create-evlog-enricher

Implement a six-touchpoint evlog enricher blueprint with source, tests, and documentation.

9|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/PhantomKnight287/saturn --skill create-evlog-enricher-phantomknight287
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-evlog-enricher
Source: https://github.com/PhantomKnight287/saturn/tree/main/.agents/skills/create-evlog-enricher
Command: npx skills add https://github.com/PhantomKnight287/saturn --skill create-evlog-enricher-phantomknight287

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a repeatable blueprint for adding a new built-in evlog enricher that derives context for wide events, ensuring consistency across source, tests, and documentation.

Core Features & Use Cases

  • Enricher architecture implements the standard Info interface, factory function, and safe merge with existing event data.
  • Full touchpoint coverage requires six mandatory touchpoints (source, tests, documentation, overview, AGENTS.md, and READMEs) to ensure completeness.
  • Common use cases include enriching deployments, tenant context, feature flags, and other metadata to enhance observability.

Quick Start

Create a new enricher by following the six touchpoints to implement end-to-end integration with the evlog package.

Frequently Asked Questions about create-evlog-enricher

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

FAQPage Schema
How do I add a new event enricher to derive context for wide events?

To add a new event enricher, implement the standard Info interface and factory function, then follow a six-touchpoint workflow covering source code, tests, and documentation to ensure uniform behavior across the evlog package.

What is the standard architecture for an evlog enricher?

An evlog enricher architecture implements a standard Info interface, a factory function, and a safe merge with existing event data using helpers like getHeader and mergeEventField to consolidate context into a single ctx.event field.

How do I safely merge new event context without causing side effects?

You safely merge event context by using existing helpers like mergeEventField to consolidate data into a single ctx.event field with overwrite control, guaranteeing no side effects or logging during the enrichment process.

What does the six-touchpoint workflow require when building an enricher?

The six-touchpoint workflow requires updating source code, tests, documentation, overview, AGENTS.md, and READMEs to ensure complete end-to-end integration and consistent behavior when adding built-in enrichers to the evlog package.

Does the evlog enricher blueprint support enriching tenant context and feature flags?

Yes, the enricher blueprint supports enriching deployments, tenant context, feature flags, and other metadata to enhance observability, using a factory function and safe merge to integrate the derived context into wide events.