Getting Started

Agent Skills

AI-assisted code review and evlog adoption using Agent Skills. Let AI review your logging patterns and guide migration to wide events.

evlog includes agent skills that help AI assistants review your logging patterns and guide evlog adoption.

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

Skill	Description
`skills/review-logging-patterns`	Review code for logging patterns, suggest evlog adoption, guide wide event design
`skills/build-audit-logs`	Design, wire, and review tamper-aware audit trails: policy, `auditEnricher`, `auditOnly`, `signed`, denials, redaction, tests
`skills/analyze-logs`	Analyze application logs from `.evlog/logs/` to debug errors, investigate performance, and understand behavior

Installing the Skill

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

To manually install with the skills CLI:

Terminal

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

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

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:

Review my code for logging anti-patterns

Convert console.log calls to a wide event

Suggest context to add to my wide event

Design or review an audit trail with evlog

Structure this error with evlog

Debug a failing endpoint from logs

Find the slowest requests from today

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

Edit this pageorReport an issue

Quick Start

Get up and running with evlog in minutes. Learn the log API, createLogger for wide events, useLogger for requests, and structured errors.

vs Other Loggers

Side-by-side comparison of evlog with pino, winston, and consola. Feature parity matrix, honest gaps, and migration snippets so you can switch with no surprises.