Automated summary
Guides a structured analysis of errors and incidents, from gathering context through root-cause identification to preventive measures.
Strengths
- A repeatable five-step workflow: context gathering, reproduction, root cause, fix, prevention
- Applies to both local errors and production incidents in distributed systems
- Includes explicit safeguards: approval and rollback plans before production changes, plus redaction of secrets and PII
- Points to a detailed playbook for cases that need deeper checklists
Limitations
- Only as effective as the error messages, logs, traces, or incident reports you can provide
- Ships no execution tooling or observability-platform integrations; the analysis stays conversational
- Findings still require environment-specific validation, testing, and expert review
Use it during a production incident, for recurring errors, or for root-cause analysis spanning multiple services.
Avoid it for pure feature development or when no logs, traces, or error reports are accessible.
Security analysis
SafeThe skill provides advisory guidance for error analysis and debugging. It declares no tools and contains no commands, destructive actions, data exfiltration, or unsafe instructions. It explicitly advises against unauthorized production changes and recommends redacting secrets and PII.
No concerns found
How this analysis is madeExamples
Analyze this stack trace from our checkout service, narrow down the failure point, and tell me the most likely root cause and the evidence supporting it: <paste stack trace>Our API returns intermittent 502s under peak load. Here are the logs and timestamps from the gateway and two backend services — help me run a root-cause analysis and propose fixes plus preventive measures.Review how our payment service logs and handles errors, then recommend structured logging, tracing, and error-handling improvements with a prioritized plan.name: error-debugging-error-analysis description: "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions." risk: safe source: community date_added: "2026-02-27"
Error Analysis and Resolution
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.
Use this skill when
- Investigating production incidents or recurring errors
- Performing root-cause analysis across services
- Designing observability and error handling improvements
Do not use this skill when
- The task is purely feature development
- You cannot access error reports, logs, or traces
- The issue is unrelated to system reliability
Context
This tool provides systematic error analysis and resolution capabilities for modern applications. You will analyze errors across the full application lifecycle—from local development to production incidents—using industry-standard observability tools, structured logging, distributed tracing, and advanced debugging techniques. Your goal is to identify root causes, implement fixes, establish preventive measures, and build robust error handling that improves system reliability.
Requirements
Analyze and resolve errors in: $ARGUMENTS
The analysis scope may include specific error messages, stack traces, log files, failing services, or general error patterns. Adapt your approach based on the provided context.
Instructions
- Gather error context, timestamps, and affected services.
- Reproduce or narrow the issue with targeted experiments.
- Identify root cause and validate with evidence.
- Propose fixes, tests, and preventive measures.
- If detailed playbooks are required, open
resources/implementation-playbook.md.
Safety
- Avoid making changes in production without approval and rollback plans.
- Redact secrets and PII from shared diagnostics.
Resources
resources/implementation-playbook.mdfor detailed analysis frameworks and checklists.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/error-analysis-and-resolution-mrwakcr4' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/error-analysis-and-resolution-mrwakcr4/download' --output '.skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md.part' && mv '.skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md.part' '.skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Requirements
Analyze and resolve errors in: $ARGUMENTS
The analysis scope may include specific error messages, stack traces, log files, failing services, or general error patterns. Adapt your approach based on the provided context.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md' && test -s '.skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/error-debugging-error-analysis' && cp -R '.skill-downloads/error-analysis-and-resolution-mrwakcr4' '.claude/skills/error-debugging-error-analysis'Cursor
test -f '.skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md' && test -s '.skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/error-debugging-error-analysis' && cp -R '.skill-downloads/error-analysis-and-resolution-mrwakcr4' '.cursor/skills/error-debugging-error-analysis'Codex
test -f '.skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md' && test -s '.skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/error-debugging-error-analysis' && cp -R '.skill-downloads/error-analysis-and-resolution-mrwakcr4' '.agents/skills/error-debugging-error-analysis'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/error-analysis-and-resolution-mrwakcr4'openskills read 'error-analysis-and-resolution-mrwakcr4'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/error-analysis-and-resolution-mrwakcr4/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.