log-analysis · akillness — Claude Code skill: triage logs before diagnosing
A skill that reads runtime logs: it picks one evidence packet first, then isolates the earliest failure. Useful when the log is long and you need the one line that matters.
npx skills add akillness/jeo-skills --skill log-analysis -a claude-codeWhat log-analysis does
The skill acts as a packet router, not a troubleshooting encyclopedia. It first normalizes the request into a single shape: packet type, source shape, environment, failure goal, anchor. There are six packets — app-runtime, container-runtime, browser-plus-api, ci-cascade, structured-json, security-signal. Only one is chosen per run, the cheaper one that cuts uncertainty fastest.
Then it narrows the slice: by time window, by request or trace id, by job or pod name. Only after that does it look for the earliest actionable failure, and separately groups the repeated fallout into a signature and blast-radius note. The tools are plain: Bash, Read, Grep, Glob — reading and searching files, no code changes.
The boundaries are explicit. Unity and Unreal build logs go to game-build-log-triage, observability setup to monitoring-observability, hypotheses and fixes to debugging, anomaly hunting across many sources to pattern-detection. If your job is editing code or building dashboards, this skill is not it. That is worth checking before you install.
What it helps with
- find the first blocker in a noisy stack trace
- tell a real error from a cascade of secondary failures
- group repeated signatures in a log
- match a browser symptom to the server-side response
- size the blast radius after one failure
Example prompts for the agent
- check the logs, which line matters here
- here are the pod logs, find the first blocker
- this is CI output, where does the cascade start
How to install log-analysis
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill log-analysis -a claude-code2Manually: put the files in place
~/.claude/skills/log-analysis/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/log-analysis/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill log-analysis -a codex2Manually: put the files in place
.agents/skills/log-analysis/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill log-analysis -a cursor2Manually: put the files in place
.cursor/skills/log-analysis/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akillness/jeo-skills log-analysis2Manually: put the files in place
.github/skills/log-analysis/SKILL.md1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill log-analysis -a gemini-cli2Platform CLI
gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/log-analysisManually: put the files in place
.devin/skills/log-analysis/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill log-analysis -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about log-analysis
How do I install log-analysis in Claude?
Run npx skills add akillness/jeo-skills --skill log-analysis -a claude-code. The skill file then sits at ~/.claude/skills/log-analysis/SKILL.md.
What does log-analysis do?
It triages runtime logs: picks one evidence packet, narrows the slice, and isolates the earliest actionable failure. It also summarizes the repeated signature and the blast radius.
Which logs does it not handle?
Unity and Unreal build logs go to game-build-log-triage, observability design to monitoring-observability, and hypotheses or fixes to debugging.
Similar skills
All skills for DevOps and infrastructure →log-analysis by other authors comes first.
