create-evlog-adapter

Add a built-in evlog drain adapter across source, build, exports, tests, and docs.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/suiramdev/terryscord-new --skill create-evlog-adapter-suiramdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-evlog-adapter
Source: https://github.com/suiramdev/terryscord-new/tree/main/.agents/skills/create-evlog-adapter
Command: npx skills add https://github.com/suiramdev/terryscord-new --skill create-evlog-adapter-suiramdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a new built-in evlog adapter requires coordinating source code, build configuration, package exports, tests, and documentation across multiple repo areas. This skill ensures a consistent, end-to-end workflow for integrating a new drain adapter that can feed external observability platforms.

Core Features & Use Cases

  • Walks through all 8 touchpoints to add a new adapter: implement the adapter at packages/evlog/src/adapters/{name}.ts, add a tsdown.config entry, update package exports, create tests at packages/evlog/test/adapters/{name}.test.ts, add an API docs page at apps/docs/content/3.adapters/{n}.{name}.md, update the adapters overview and AGENTS.md, and renumber custom.md to keep it last.
  • Ensures rigorous build, test coverage, and documentation wiring for maintainability and consistency across adapters.
  • Supports a scalable approach to adding multiple adapters for different observability backends.

Quick Start

Create a new evlog adapter by following the 8 touchpoints outlined above to implement the adapter, tests, docs, and integration.

Frequently Asked Questions about create-evlog-adapter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new evlog adapter for sending wide events to an external observability platform?

To add a new evlog adapter, implement the adapter source file, update build configuration, modify package exports, write tests, and wire up API documentation across the repository.

What steps are required to integrate a drain adapter for observability platforms like Datadog or Sentry?

Integrating a drain adapter requires completing 8 touchpoints: implementing source code, updating tsdown.config, modifying package exports, adding tests, creating an API docs page, and updating repository documentation.

Does the evlog adapter workflow enforce specific file paths for source code and tests?

Yes, the workflow enforces strict file paths for adapter implementation and testing, placing source files in packages/evlog/src/adapters/ and test files in packages/evlog/test/adapters/.

Can I use this workflow to scale observability integrations for multiple backends like Loki or Elasticsearch?

Yes, the workflow supports a scalable approach to adding multiple adapters, ensuring consistent build configuration, test coverage, and documentation wiring across different observability backends.

Why does adding an adapter require updating AGENTS.md and renumbering custom.md?

Updating AGENTS.md and renumbering custom.md maintains repository documentation accuracy, ensuring custom adapters remain listed last and internal guidelines reflect the new built-in integration.

What is the best way to ensure test coverage and documentation wiring when extending the evlog package?

The best way to ensure coverage is following the guided workflow that mandates test creation, API docs generation, and overview updates, enforcing rigorous build and documentation standards end-to-end.