error-diagnostics-error-analysis
Diagnostic tool for investigating production incidents and performing root-cause analysis across distributed systems.
Install
mkdir -p .claude/skills/error-diagnostics-error-analysis && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4450" && unzip -o skill.zip -d .claude/skills/error-diagnostics-error-analysis && rm skill.zipInstalls to .claude/skills/error-diagnostics-error-analysis
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.Key capabilities
- →Investigate production system crashes
- →Analyze distributed trace logs
- →Map recurring error patterns
- →Design observability improvement plans
How it works
Correlates error signals across system components to establish failure timelines and identify root causes.
Inputs & outputs
When to use error-diagnostics-error-analysis
- →Investigate production system crashes
- →Analyze recurring error patterns
- →Design observability and error handling improvements
- →Perform root-cause analysis
About this skill
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.
When not to use it
- →Standard feature development
- →Code that lacks error reporting or observability
Prerequisites
Limitations
- →Requires access to observability infrastructure
- →Cannot fix external service issues
How it compares
Systematically approaches incident response using structured observability data rather than anecdotal debugging.
Compared to similar skills
error-diagnostics-error-analysis side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| error-diagnostics-error-analysis (this skill) | 1 | 4mo | No flags | Advanced |
| analyzing-logs | 14 | 27d | Review | Beginner |
| sentry | 10 | 4mo | Caution | Beginner |
| obsidian-incident-runbook | 3 | 27d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by sickn33
View all by sickn33 →You might also like
analyzing-logs
jeremylongshore
Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.
sentry
openai
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
obsidian-incident-runbook
jeremylongshore
Troubleshoot Obsidian plugin failures with systematic incident response. Use when plugins crash, data is corrupted, or users report critical issues with your Obsidian plugin. Trigger with phrases like "obsidian crash", "obsidian plugin broken", "obsidian incident", "debug obsidian failure", "obsidian emergency".
obsidian-observability
jeremylongshore
Set up comprehensive logging and monitoring for Obsidian plugins. Use when implementing debug logging, tracking plugin performance, or setting up error reporting for your Obsidian plugin. Trigger with phrases like "obsidian logging", "obsidian monitoring", "obsidian debug", "track obsidian plugin".
langsmith-observability
davila7
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
network-info
UKGovernmentBEIS
Gather network configuration and connectivity information including interfaces, routes, and DNS