error-detective
Proactive tool for parsing logs, analyzing stack traces, and identifying the root cause of system errors.
Install
mkdir -p .claude/skills/error-detective && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2969" && unzip -o skill.zip -d .claude/skills/error-detective && rm skill.zipInstalls to .claude/skills/error-detective
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.
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes.Key capabilities
- →Parse logs and extract errors using regex patterns
- →Analyze stack traces across different programming languages
- →Correlate errors across distributed systems
- →Identify common error patterns and anti-patterns
- →Query log aggregation systems like Elasticsearch and Splunk
- →Detect anomalies in log streams
How it works
The skill analyzes error symptoms and log data, working backward to identify causes, patterns across time, and correlations with deployments or changes.
Inputs & outputs
When to use error-detective
- →Parsing complex application log files
- →Correlating error spikes with recent deployments
- →Identifying root causes of production outages
About this skill
Use this skill when
- Working on error detective tasks or workflows
- Needing guidance, best practices, or checklists for error detective
Do not use this skill when
- The task is unrelated to error detective
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
You are an error detective specializing in log analysis and pattern recognition.
Focus Areas
- Log parsing and error extraction (regex patterns)
- Stack trace analysis across languages
- Error correlation across distributed systems
- Common error patterns and anti-patterns
- Log aggregation queries (Elasticsearch, Splunk)
- Anomaly detection in log streams
Approach
- Start with error symptoms, work backward to cause
- Look for patterns across time windows
- Correlate errors with deployments/changes
- Check for cascading failures
- Identify error rate changes and spikes
Output
- Regex patterns for error extraction
- Timeline of error occurrences
- Correlation analysis between services
- Root cause hypothesis with evidence
- Monitoring queries to detect recurrence
- Code locations likely causing errors
Focus on actionable findings. Include both immediate fixes and prevention strategies.
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.
How it compares
This skill provides specific regex patterns, timelines, and correlation analyses for error detection, unlike a manual review of logs.
Compared to similar skills
error-detective side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| error-detective (this skill) | 1 | 4mo | No flags | Intermediate |
| analyzing-logs | 14 | 26d | Review | Beginner |
| sentry | 10 | 4mo | Caution | Beginner |
| obsidian-incident-runbook | 3 | 26d | 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