analyze-logs
Skill1 starsChanged 3 days agoMITView on GitHub
Analyze application logs from the .evlog/logs/ directory. Use when debugging errors, investigating slow requests, understanding request patterns, or answering questions about application behavior. Reads structured NDJSON wide events written by evlog's file system drain.
4 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- h-wata/claude-skillstheir own version, first seen Oct 13, 2026
- tangem/tangem-app-androidtheir own version, first seen Oct 8, 2026
- HugoRCD/evlogedited, first seen Oct 8, 2026
- activepieces/activepiecesedited, first seen Jun 17, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- activepieces/activepieces★ 26k91% same
- HugoRCD/evlog★ 1.9k75% same
Wrote their own version · 2
- tangem/tangem-app-android★ 64same name
- h-wata/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- architectSkill
- build-audit-logsSkill
- cloudflareSkill
- code-reviewSkill
- design-engineeringSkill
- diagnosing-bugsSkill
- full-sendSkill
- full-stopSkill
- ghSkill
- grillingSkill
- impeccableSkill
- improve-animationsSkill
- interrogateSkill
- no-use-effectSkill
- prSkill
- retroSkill
- t3-toolsSkill
- triageSkill
- unslopSkill
- vitestSkill
- wait-whatSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
12 rules. 3 are common, 2 are distinctive, and 7 are very specific to this project.
3
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read and analyze structured wide-event logs from the local .evlog/logs/ directory to debug errors, investigate performance issues, and …
- Very specific: line 30
Always check the first few bytes of the file to detect the format: if the second character is a newline or ", it's NDJSON.
- Distinctive: line 32
Search order: Check these locations relative to the project root:
- Common: line 37
Use glob to find log files:
- Very specific: line 53
Before wiring a new drain, you can try npx @evlog/cli doctor --json, which checks whether evlog is installed and whether a local …
- Distinctive: line 62
Ask before running it. On other frameworks (or if the user declines), guide the manual setup:
- Common: line 85
After setup, the user needs to trigger some requests to generate logs, then re-analyze.
- Very specific: line 109
All other fields are application-specific context added via log.set() (e.g.
- Very specific: line 115
Read the latest .jsonl file.
- Very specific: line 121
Errors: look for "level":"error" or status >= 400
- Very specific: line 134
How to fix: check error.data.fix for suggested remediation
- Common: line 136
Patterns: look for recurring errors, degrading performance, or correlated failures
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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
Logs are written by evlog's file system drain as .jsonl files, organized by date.
Format detection: The drain supports two modes:
- NDJSON (default,
pretty: false): One compact JSON object per line. Parse line-by-line. - Pretty (
pretty: true): Multi-line indented JSON per event. Parse by reading the entire file and splitting on top-level objects (e.g.JSON.parse('[' + content.replace(/\}\n\{/g, '},{') + ']')) or use a streaming JSON parser.
Always check the first few bytes of the file to detect the format: if the second character is a newline or ", it's NDJSON; if it's a space or newline followed by spaces, it's pretty-printed.
Search order. Check these locations relative to the project root:
.evlog/logs/(default)- Any
.evlog/logs/inside app directories (monorepos:apps/*/.evlog/logs/)
Use glob to find log files:
.evlog/logs/*.jsonl
*/.evlog/logs/*.jsonl
apps/*/.evlog/logs/*.jsonlFiles are named by date: 2026-03-14.jsonl. Start with the most recent file.
Programmatic reading: instead of hand-parsing, a small script can use the readers shipped with evlog: readFsLogs() and tailFsLogs() from evlog/fs are async generators that handle both formats, date ordering, and filtering. Prefer them when the project already has evlog installed and the analysis needs more than a quick grep.
Memory drain alternative: some apps use the Memory adapter (evlog/memory) instead of (or alongside) the FS drain, exposing recent events through a dev-only HTTP endpoint via readMemoryLogs(). If .evlog/logs/ is empty but the app wires createMemoryDrain(), query that endpoint instead.
If no logs are found
Before wiring a new drain, you can try npx @evlog/cli doctor --json, which checks whether evlog is installed and whether a local .evlog/logs drain already exists (read-only). Optional; skip if the CLI is unavailable.
The file system drain may not be enabled. On Nuxt, Nitro, Next.js, TanStack Start, or Hono, the fastest path is the CLI, which detects the framework and wires the fs drain (its default dev drain) in one pass:
npx @evlog/cli init --dry-run --yes # preview first
npx @evlog/cli init --yes --drain fs # applyAsk before running it. On other frameworks (or if the user declines), guide the manual setup:
import { createFsDrain } from 'evlog/fs'
// Nuxt / Nitro: server/plugins/evlog-drain.ts
export default defineNitroPlugin((nitroApp) => {
nitroApp.hooks.hook('evlog:drain', createFsDrain())
})
// Hono / Express / Elysia: pass in middleware options
app.use(evlog({ drain: createFsDrain() }))
// Fastify: pass in plugin options
await app.register(evlog, { drain: createFsDrain() })
// NestJS: pass in module options
EvlogModule.forRoot({ drain: createFsDrain() })
// Standalone: pass to initLogger
initLogger({ drain: createFsDrain() })After setup, the user needs to trigger some requests to generate logs, then re-analyze.
Log format
Each line is a self-contained JSON object (wide event). Key fields:
| Field | Type | Description |
timestamp | string | ISO 8601 timestamp |
level | string | info, warn, error, debug |
service | string | Service name |
environment | string | development, production, etc. |
method | string | HTTP method (GET, POST, etc.) |
path | string | Request path (/api/checkout) |
status | number | HTTP response status code |
duration | string | Request duration, human-formatted ("234ms") |
durationMs | number | Request duration in milliseconds. Filter and sort on this one |
requestId | string | Unique request identifier |
error | object | Error details: name, message, stack, statusCode, data |
error.data.why | string | Human-readable explanation of what went wrong |
error.data.fix | string | Suggested fix for the error |
source | string | client for browser logs, absent for server logs |
userAgent | object | Parsed browser/OS/device info |
All other fields are application-specific context added via log.set() (e.g. user, cart, payment).
How to analyze
Step 1: Read the most recent log file
Read the latest .jsonl file. Each line is one JSON event. Parse each line independently.
Step 2: Identify the relevant events
Filter based on the user's question:
- Errors: look for
"level":"error"orstatus >= 400 - Specific endpoint: match on
path - Slow requests: filter on
durationMs(e.g.durationMs > 500) - Specific user/action: match on application-specific fields
- Client-side issues: filter by
"source":"client" - Time range: compare
timestampvalues
Step 3: Analyze and explain
For each relevant event:
- What happened: summarize the
path,method,status,level - Why it failed (errors): read
error.message,error.data.why, and the stack trace - How to fix: check
error.data.fixfor suggested remediation - Context: examine application-specific fields for business context (user info, payment details, etc.)
- Patterns: look for recurring errors, degrading performance, or correlated failures
Analysis patterns
Find all errors
Filter: level === "error"
Group by: error.message or path
Look for: recurring patterns, common failure modesFind slow requests
Filter: durationMs > 1000
Sort by: durationMs descending
Look for: specific endpoints, time-of-day patternsTrace a specific request
Filter: requestId === "the-request-id"
Result: single wide event with all context for that requestError rate by endpoint
Group events by: path
Count: total events vs error events per path
Look for: endpoints with high error ratiosClient vs server errors
Split by: source === "client" vs no source field
Compare: error patterns between client and server
Look for: client errors that don't have corresponding server errors (network issues)Important notes
- Each line is a complete, self-contained event. Unlike traditional logs, you don't need to correlate multiple lines. One line has all the context for one request.
- The
error.data.whyanderror.data.fixfields are evlog-specific structured error fields. When present, they provide the most actionable information. durationis human-formatted with units (e.g."706ms").durationMsis the same duration in milliseconds; filter and sort ondurationMs.- Events with
"source":"client"originated from browser-side logging and were sent to the server via the HTTP drain endpoint. - Log files are
.gitignore'd automatically. They exist only on the local machine or server where the app runs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

