Agent Skills

evlog includes agent skills that help AI assistants review your logging patterns and guide evlog adoption. Pair them with @evlog/cli when you want a scoreable coverage map — the skills teach the patterns; evlog map points at the dark entry points.

What are Agent Skills?

Agent Skills is an open specification for packaging AI assistant capabilities. Skills provide:

• Domain knowledge: Best practices for wide events and structured errors
• Code review: Identify logging anti-patterns in your codebase
• Guided adoption: Step-by-step help migrating to evlog

Available Skills

Installing the Skill

Compatible agents (Cursor, Claude Code, etc.) can discover and use skills automatically.

To install with the skills CLI:

npx skills add https://www.evlog.dev

evlog agents runs that same command for you, and additionally writes a short block of evlog conventions into your project's AGENTS.md — the rules an agent should follow on every logging change, which the skills then back with the detail:

npx @evlog/cli agents

What the Skill Does

Code Review

The skill analyzes your codebase for:

• Scattered logging: Multiple console.log or logger.info calls in request handlers
• Missing context: Logs without user, request, or business context
• Unhelpful errors: throw new Error() without structured fields
• Correlation gaps: Missing request IDs or trace IDs

On Nuxt, Nitro, Next.js, and TanStack Start, ask the assistant to try evlog map first (npx @evlog/cli map --no-write) — it scores every entry point and lists FIX FIRST. Agents that prefer structured output can use npx @evlog/cli map --json --no-write. The skill still works without the CLI; map is a separate early package that makes the review faster when available.

Adoption Guidance

The skill helps you:

• Convert traditional logging to wide events
• Design effective wide event schemas
• Implement structured errors with why, fix, and link
• Set up evlog in Nuxt, Nitro, or standalone TypeScript

Log Analysis

The analyze-logs skill teaches your AI assistant to read structured logs from .evlog/logs/:

• Error debugging: Find and explain errors, stack traces, and failure patterns
• Performance investigation: Identify slow requests by duration
• Request tracing: Follow a request across its lifecycle using requestId
• Pattern detection: Spot recurring issues or anomalies

Example Prompts

Ask your AI assistant:

Skill Structure

skills/
├── review-logging-patterns/
│   ├── SKILL.md              # Main skill instructions
│   └── references/
│       ├── wide-events.md    # Wide event patterns
│       ├── structured-errors.md # Error handling guide
│       └── code-review.md    # Review checklist
├── build-audit-logs/
│   ├── SKILL.md              # Audit policy, wiring, review checklist
│   └── references/
│       └── framework-wiring.md
└── analyze-logs/
    └── SKILL.md              # Log analysis from .evlog/logs/

Reference Documents

The skill includes reference documents that provide:

wide-events.md

• Wide event anatomy and best practices
• Context grouping patterns
• Output format examples

structured-errors.md

• Error field definitions
• Status code guidelines
• Frontend integration patterns

code-review.md

• Checklist for logging code review
• Common anti-patterns to identify
• Migration suggestions

Next Steps

• Quick Start - Get started with evlog
• Wide Events - Learn wide event design
• Structured Errors - Error handling patterns