FREE
Debugging
error-detective
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes.
Try it — you'd type
“Help me with error-detective.”
And you'd get back
Search logs and codebases for error patterns, stack traces, and anomalies.
Correlates errors across systems and identifies root causes.
Adding it takes about 30 seconds
1
Click Get this skill. Grab the .md file, one click, no account needed.
2
Add it to Claude. Drop it into ~/.claude/skills/. Claude picks it up the next time you open a session.
3
Ask normally. Type your question. The skill triggers on the right keywords — you don't have to remember anything.
You might also like
Error Analyzer
Analyze error messages and suggest fixes
Stack Trace Decoder
Decode and explain stack traces
Memory Leak Finder
Find and fix memory leaks
Performance Profiler
Profile code and identify bottlenecks
Log Analyzer
Analyze log files and identify patterns
Network Debugger
Debug network/HTTP request issues
SKILL FILEWhat Claude actually reads
- 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 1. Start with error symptoms, work backward to cause 2. Look for patterns across time windows 3. Correlate errors with deployments/changes 4. Check for cascading failures 5. 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.