Log Analysis
Parsing logs, correlation analysis, reconstructing timeline of failures.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill log-analysisgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/debugging/skills/log-analysis ~/.claude/skills/log-analysisPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Log Analysis Extracting signal from system logs to understand failure sequences. ## Context You are analyzing logs to find the failure cause. Look for timeline, patterns, correlations. ## Domain Context - **Timeline**: Reconstruct what happened when; precise ordering matters - **Error Codes**: What errors occurred? In what sequence? - **Correlation**: Are errors across components? Do they align with infrastructure events? - **Search**: Use grep, jq, SQL to find relevant entries - **Context**: Include lines before/after errors; context matters ## Instructions 1. **Establish Timeline**: Extract timestamps; create chronological view 2. **Filter Noise**: Remove expected errors, noise; focus on anomalies 3. **Find Correlation**: Do errors align? Were requests affected? 4. **Look for Cascades**: One error triggers others? 5. **Check Systems**: App logs, infrastructure logs, database logs together 6. **Extract Variables**: What IDs, values were involved? 7. **Visualize**: Create timeline or flow diagram ## Anti-Patterns - Relying on log levels (ERROR) alone; logs labeled ERROR might be expected failures - Not correlating across systems; bug often spans app + infrastructure - Ignoring INFO logs; they provide context for ERROR understanding - Timestamps not synchronized; makes correlation impossible - Logs too verbose (every DB query); filter to signal ## Further Reading - Google Cloud Logging best practices - ELK Stack (Elasticsearch, Logstash, Kibana) tutorials
Details
- Skill name
log-analysis- Repository
- sethdford/claude-skills
- Path
engineer/debugging/skills/log-analysis/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Log Analysis skill do?
Parsing logs, correlation analysis, reconstructing timeline of failures.
How do I install the Log Analysis skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Log Analysis popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Market Sizing
48sethdford/claude-skills
Estimate total addressable market (TAM), serviceable market (SAM), and obtainable market (SOM).
Log Aggregation
48sethdford/claude-skills
ELK Stack, structured logging, log query patterns, and centralized log management.
Microservices Patterns
48sethdford/claude-skills
Apply proven microservices patterns including saga, circuit breaker, bulkhead, and eventual consistency. Use when designing service-to-service communication and handling distributed failures.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.