amey-thakur/ai-skills/log-analysis
Claude Code and agent skill by amey-thakur/ai-skills
- community
Checking that the SKILL.md file is still in the repository.
Mine logs for the cause of a failure by pivoting on correlation ids, clamping the time window, and querying structured fields instead of scrolling. Use when production broke and the logs are the only record of what the system actually did.
Install
npx vskill@latest install amey-thakur/ai-skills/log-analysisSKILL.md
The same SKILL.md was published earlier as amey-thakur/ai-skills/log-analysis.
Log analysis
Logs capture everything the system did and almost none of it bears on the bug in front of you. Scrolling for red text surfaces the loudest line, which is usually a downstream victim rather than the trigger. A method narrows by identity and time until only the failing request is left on the screen.
Method
- Pivot on an identifier before a keyword. Lift the request id, trace id,
or order id from the user report or the error tracker, then query for it alone: jq 'select(.request_id=="req_8f3a")' or Loki {app="api"} | json | request_id="req_8f3a". One id collapses the haystack into a single thread.
- Clamp the window to the incident. Pass
--sinceand--untila couple
of minutes on each side of the first symptom, or drag the Grafana time picker onto the deploy. A day-wide window drowns the signal in unrelated traffic.
- Read forward from the first divergence. Sort ascending and find where
the error rate leaves baseline. The 500s at the top of the tail are the cascade; the connection reset thirty seconds earlier is the cause.
- Match fields, not substrings. On JSON logs, filter `level>="error" and
status>=500 and route="/checkout". Grepping fail misses failure and err` and matches those letters inside unrelated words.
- Merge services on the shared id. Carry the same correlation id from the
gateway through the API to the worker and interleave every line by timestamp. The gap between "received" and "handler start" is where the latency actually sat.
- Aggregate before you conclude. Run
| stats count by error_code, host.
Every error landing on one host is a sick node, not a sick code path. Cardinality tells you scope that no single line can.
Checks
- Can you name the earliest line where behavior left normal, with its exact
timestamp?
- Did the cause come from a filter on id and field, or from reading by eye?
- Does your merged timeline touch every service the request passed through?
Boundaries
Log analysis reconstructs what was written down and is blind to what was never logged. When the failing hop lives between services rather than inside one, move to distributed-tracing. Long-run trends belong on a dashboard, not in a line-by-line hunt.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/debugging/log-analysis/SKILL.md
Popularity
- Repository stars
- 10
- Repository forks
- 2
- 7-day trend score
- 17
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/amey-thakur/ai-skills/log-analysis)