Create Evlog Adapter

You're adding a new observability adapter to the evlog package. This walks you through all eight mandatory touchpoints: writing the adapter source with proper error handling and timeout support, updating build config and package exports, adding tests, writing framework-specific docs for Nuxt, Hono, Express, and others, and updating the overview and skill registry. The architecture is standardized around config interfaces, factory functions, and send methods built on the same toolkit primitives that community adapters use. What I like here is the enforced completeness. It won't let you skip the documentation page or forget to renumber files, which means the adapter you ship actually matches the quality bar of built-in ones. If you're contributing upstream or maintaining a fork, this keeps the codebase consistent.

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

View on GitHub

Install

$ npx -y skills add hugorcd/evlog --skill create-evlog-adapter --agent claude-code

Installs into .claude/skills of the current project.

Files

Create evlog Adapter

Add a new built-in adapter to evlog. Every adapter follows the same architecture and is built on the public toolkit primitives in evlog/toolkit, so a community adapter has the same shape as a built-in one.

PR Title

feat({name}): add the {Name} drain adapter

Recent examples: feat(loki): add the Grafana Loki drain adapter, feat(clickhouse): add the ClickHouse drain adapter. Use the adapter name as the conventional-commit scope, and register that scope (see touchpoint 11).

Scope timing caveat: the semantic PR check reads its scope list from the base branch, so a brand-new scope can't validate the very PR that introduces it. Either register the scope in a small preceding PR (the Loki/ClickHouse pattern), or use an unscoped title (feat: add the {Name} drain adapter) on the introducing PR.