Agent skill

Adapter Alignment

by evloghq in evloghq/evlog

Twice-monthly check that evlog's drain adapters still send what each provider's own client sends.

MITAuto-check passedDevelopment

Install Adapter Alignment

skills CLI
$ npx skills add evloghq/evlog --skill adapter-alignment -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install evloghq/evlog adapter-alignment --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/evloghq/evlog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/evi/agent/skills/adapter-alignment .claude/skills/adapter-alignment && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
adapter-alignment
GitHub stars
1.9k
Token cost
~1.3k tokens
SKILL.md length
719 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Twice-monthly check that evlog's drain adapters still send what each provider's own client sends.

  • Works in 4 steps: Pick the two adapters → Read both sides → Compare → …
  • Tasks that involve Static sites and blogs
  • SKILL.md covers 1. Pick the two adapters, 2. Read both sides, 3. Compare and 4. Deliver, plus 1 more section
  • Calls pnpm and npm

What it does

Adapter Alignment is an agent skill from evloghq/evlog. Twice-monthly check that evlog's drain adapters still send what each provider's own client sends. Rotates two adapters per run through the pins in .agents/skills/create-adapter/references/upstream-alignment.md, diffs endpoint, auth, payload shape, level mapping, batch limits, and retry behavior against the official client at its current version, opens ready pull requests for mechanical mismatches, files philosophy mismatches in Linear, and moves the pin forward. Load this when the adapter-alignment schedule…

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Static sites and blogs, Data warehousing and Pull requests. It works with ClickHouse, OpenTelemetry, Datadog and PostHog. The repository describes itself as: Digging through logs is not observability. It's hope — wide events, structured errors, TypeScript-first, every runtime. The licence is MIT.

When your agent uses it

  • Tasks that involve Static sites and blogs
  • Tasks that involve Data warehousing
  • Tasks that involve Pull requests

Example prompts

  • “s drain adapters still send what each provider”
  • “/adapter-alignment”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Pick the two adapters
  2. Read both sides
  3. Compare
  4. Deliver

What it can do on your machine

Read from SKILL.md and the folder at commit 59a105f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Adapter Alignment loads about 1.3k tokens when it runs. Until then it costs about 170 tokens; SKILL.md has 719 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~170
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from evloghq/evlog at commit 59a105f, republished under its MIT licence (© evloghq). 719 words, ~1,285 tokens.

Download SKILL.mdSave it as .claude/skills/adapter-alignment/SKILL.md (or your agent's skills folder).
name
adapter-alignment
description
Twice-monthly check that evlog's drain adapters still send what each provider's own client sends. Rotates two adapters per run through the pins in .agents/skills/create-adapter/references/upstream-alignment.md, diffs endpoint, auth, payload shape, level mapping, batch limits, and retry behavior against the official client at its current version, opens ready pull requests for mechanical mismatches, files philosophy mismatches in Linear, and moves the pin forward. Load this when the adapter-alignment schedule fires, or when Hugo asks whether an adapter is still aligned with Sentry, Datadog, Axiom, PostHog, Loki, ClickHouse, Better Stack, HyperDX, or OTLP.

Adapter alignment

evlog ships adapters for providers whose APIs and clients move on their own. The e2e suite proves a destination still accepts our payload; nothing proves the payload is what the provider's own client would have sent. This run closes that gap for two adapters at a time, so every third-party adapter is compared about every two months.

The question is always the same: given one wide event, would the official client and evlog produce the same request? Where they differ, is the difference a choice evlog made on purpose, or drift?

1. Pick the two adapters

Read .agents/skills/create-adapter/references/upstream-alignment.md in /workspace/repo. Take the two rows with the oldest Aligned to, treating unset as oldest. Break a tie by table order. Skip a row only when a run in the last two weeks already covered it and record why.

2. Read both sides

For each adapter:

  • Ours: packages/evlog/src/adapters/<name>.ts, its unit test under packages/evlog/test/adapters/, its e2e under packages/evlog/test/e2e/ when one exists, and its docs page under apps/docs/content/4.integrate/adapters/.
  • Theirs: the ingest documentation URL and the Start here files in the official client at its latest published version. Read the version with npm view <package> version from the sandbox. Read source with github__getFileContent at the matching tag; a Start here path that no longer exists is a limitation to record, and the run locates the replacement with github__searchCode before continuing. Do not reason from memory of the client; read the lines.

Record the client version and the files read. They are the evidence for everything below.

3. Compare

Walk the list under "What a comparison covers" in the reference file. For each property, write one line: ours, theirs, same or different. A difference becomes one of:

  • Mismatch: the provider stores or indexes the event differently because of it (wrong default site, a renamed field, a level the provider does not recognise, a limit we exceed, an endpoint the provider deprecated). Evidence is the upstream line and ours.
  • Choice: evlog differs on purpose and the adapter or docs say so (we batch where they stream, we flatten where they nest). Record it; do not file it. If nothing says so, it is a question, not a choice.
  • Note: evlog is stricter than the client with no effect on what the provider stores.

The e2e test is part of the comparison. An adapter with no e2e file (Datadog and HyperDX today) gets that gap recorded as a proposal unless one already exists in Linear.

Show full SKILL.md (310 more words)Show less

4. Deliver

Mechanical mismatch → ready PR. A wrong default, a missing or renamed field, a stale endpoint, a limit to lower. Follow contributing: branch off main in /workspace/repo, write the failing regression test first, fix, run pnpm run lint, pnpm run typecheck, and pnpm --filter evlog exec vitest run test/adapters/<name>.test.ts, then the full suite. Add a changeset; an adapter change is user-facing. Update the adapter docs page when it states the old value. The PR body shows the upstream line and ours side by side, names the client version, and states what the provider will store differently after the change. Read CI, fix what fails, request hugorcd as reviewer. One mismatch per PR unless several are the same kind on one adapter; then one PR for that adapter. At most two PRs per run.

Philosophy mismatch or question → Linear issue via linear__save_issue on the evlog team. State what the client does, what evlog does, the upstream evidence, who would notice, and the decision to make. Search linear__list_issues first; a recurring mismatch updates its issue.

Move the pin. In a real run, once every mismatch on an adapter is either in a PR, in an issue, or recorded as a choice, update that row's Aligned to to <package> <version> @ <short SHA of main> in the same PR as the fixes, or in its own docs: PR when nothing needed fixing. A pin never moves past a mismatch that has no destination.

Then post one line per adapter to the thread: aligned, or the PR and issue links inline.

When nothing is warranted

Both adapters match their client: move the two pins in one docs: PR and say so in one line. Never invent a mismatch, never file an issue to record that an adapter is aligned, and never open a PR that only touches the pin table alongside a code change.

© evloghq, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in apps/evi/agent/skills/adapter-alignment of evloghq/evlog.

Open the folder on GitHubat commit 59a105f

Compare with similar skills

Adapter Alignment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Adapter Alignment compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Adapter Alignment this skillevloghq/evlog1.9k—~1.3kAutomated safety check: PassMIT
Code ReviewClickHouse/clickhouse-java1.6k—~290Automated safety check: PassApache-2.0
Continue PRClickHouse/ClickHouse50k—~5.5kAutomated safety check: NotesApache-2.0
Fix SyncClickHouse/ClickHouse50k—~2.8kAutomated safety check: PassApache-2.0
Clickhouse PR DescriptionClickHouse/ClickHouse50k—~1.9kAutomated safety check: PassApache-2.0
Create PRUniClipboard/UniClipboard1.9k—~4.6kAutomated safety check: PassAGPL-3.0

Similar skills

  • Code Review

    ClickHouse/clickhouse-java

    Review changes in clickhouse-java for correctness, compatibility, API stability, and missing tests.

    1.6k GitHub stars~290 tokensUpdated today
    DevelopmentAuto-check passed
  • Continue PR

    ClickHouse/ClickHouse

    Continue work on an existing PR - resolve conflicts, fix CI failures, address reviewer feedback, and push updates.

    50k GitHub stars~5.5k tokensUpdated today
    DevelopmentAuto-check: notes
  • Fix Sync

    ClickHouse/ClickHouse

    Fix the "CH Inc sync" job in a pull request. An agent skill from ClickHouse/ClickHouse.

    50k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Clickhouse PR Description

    ClickHouse/ClickHouse

    Generate PR descriptions for ClickHouse/ClickHouse that match maintainer expectations.

    50k GitHub stars~1.9k tokensUpdated today
    DatabasesAuto-check passed
  • Create PR

    UniClipboard/UniClipboard

    Push the current branch and open a GitHub pull request against main.

    1.9k GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Review

    ClickHouse/ClickHouse

    Review a ClickHouse Pull Request for correctness, safety, performance, and compliance.

    50k GitHub stars~8k tokensUpdated today
    DatabasesAuto-check: notes

More from evloghq/evlog

All 20 skills in this repo
  • Walks through adding a new built-in evlog drain adapter for an observability platform: source, build config, exports, tests, docs and PR scope.

    1.9k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Guides adding a new built-in enricher to the evlog package, covering the source, tests, docs, README, a related skill and a changeset.

    1.9k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Walks a contributor through adding a new HTTP framework integration to the evlog logging package: middleware source, build entry, exports, tests, example app and docs.

    1.9k GitHub stars~5k tokensUpdated yesterday
    Auto-check: notes
  • Walks through adding a new rule or framework adapter to `evlog map` in @evlog/cli, from the rule source and registry to types, tests, docs and the published skill.

    1.9k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Rules for writing and reviewing evlog docs, blog posts, READMEs, skills and AGENTS.md files, with separate review and rewrite roles, a house voice and a catalog of AI-sounding tells.

    1.9k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Before After

    evloghq/evlog

    Produce a before/after visual comparison of an evlog surface (landing, docs, telemetry, playgrounds) and share it as public Blob URLs.

    1.9k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

Questions about Adapter Alignment

What does Adapter Alignment do?

Twice-monthly check that evlog's drain adapters still send what each provider's own client sends. Adapter Alignment is an agent skill from evloghq/evlog. Twice-monthly check that evlog's drain adapters still send what each provider's own client sends.

When should I use Adapter Alignment?

Adapter Alignment fits situations like: tasks that involve Static sites and blogs; tasks that involve Data warehousing; tasks that involve Pull requests.

How do I install Adapter Alignment in Claude Code?

Run `npx skills add evloghq/evlog --skill adapter-alignment -a claude-code`. Or copy the skill folder (apps/evi/agent/skills/adapter-alignment in evloghq/evlog) into .claude/skills/adapter-alignment in your project. Claude Code loads it when a task matches its description.

How do I install Adapter Alignment in Codex?

Run `npx skills add evloghq/evlog --skill adapter-alignment -a codex`. Or copy the skill folder (apps/evi/agent/skills/adapter-alignment in evloghq/evlog) into .agents/skills/adapter-alignment in your project. Codex loads it when a task matches its description.

Can I use Adapter Alignment in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add evloghq/evlog --skill adapter-alignment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adapter-alignment, .gemini/skills/adapter-alignment, .github/skills/adapter-alignment and .opencode/skills/adapter-alignment in your project.

What does Adapter Alignment need to run?

Going by SKILL.md and its folder, Adapter Alignment needs the command-line tools its instructions call (pnpm and npm).

Does Adapter Alignment access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Adapter Alignment safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Adapter Alignment use?

Adapter Alignment is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Adapter Alignment use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Adapter Alignment?

Skills that share tags, products or a category with Adapter Alignment: Code Review (ClickHouse/clickhouse-java, 1.6k stars), Continue PR (ClickHouse/ClickHouse, 50k stars), Fix Sync (ClickHouse/ClickHouse, 50k stars) and Clickhouse PR Description (ClickHouse/ClickHouse, 50k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Adapter Alignment?

evloghq (a GitHub organization) maintains it in evloghq/evlog, which has 1,887 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 7, 2026.

Source: evloghq/evlog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.