Analyze Logs

This is for debugging with evlog's structured logging system. It reads NDJSON files from `.evlog/logs/` where each line is a complete wide event with all request context in one place. No correlating multiple log lines to understand what happened. When errors occur, you get `error.data.why` and `error.data.fix` fields that actually explain the problem and suggest remediation. The skill knows to check for both compact and pretty-printed formats, hunt through monorepo structures, and walk you through setup if the file system drain isn't configured yet. Most useful when you're staring at a 500 error or mysterious slowdown and need to see exactly what the application saw, including business context like user data or payment details that got logged alongside the technical failure.

skills.sh installs: 227
GitHub stars: 1.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add hugorcd/evlog --skill analyze-logs --agent claude-code

Installs into .claude/skills of the current project.

Files

Analyze application logs

Read and analyze structured wide-event logs from the local .evlog/logs/ directory to debug errors, investigate performance issues, and understand application behavior.

When to Use

User asks to debug an error, investigate a bug, or understand why something failed
User asks about request patterns, slow endpoints, or error rates
User asks "what happened" or "what's going on" with their application
User asks to analyze logs, check recent errors, or review application behavior
User mentions a specific error message or status code they're seeing

Finding the logs

Try the CLI first; it reads both file layouts, every dated file, and knows where the project's drain writes. Prefer the copy the project installed (pnpm evlog, or the equivalent for its package manager). The wrappers that fetch on demand (npx, bunx, npm exec) install @evlog/cli when the project has none, which runs a release the lockfile never pinned. Ask before that happens.

SKILL.md on GitHub