New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ad Drift

by CorridorTech in CorridorTech/PoseCap

Read-only drift audit — compare AGENTS.md, ARCHITECTURE.md, ADR statuses, feature specs in doc/specs/, and documentation discipline against what the code actually does.

Apache-2.0Auto-check: notesDevelopment

Install Ad Drift

skills CLI
$ npx skills add CorridorTech/PoseCap --skill ad-drift -a claude-code

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

GitHub CLI
$ gh skill install CorridorTech/PoseCap ad-drift --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/CorridorTech/PoseCap.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ad-drift .claude/skills/ad-drift && 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
ad-drift
GitHub stars
220
Token cost
~1.8k tokens
SKILL.md length
861 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Read-only drift audit — compare AGENTS.md, ARCHITECTURE.md, ADR statuses, feature specs in doc/specs/, and documentation discipline against what the code actually does.

  • Works in 3 steps: Decide what to audit → Run checks → Output
  • The user wants to audit
  • SKILL.md covers Step 1 — Decide what to audit, Step 2 — Run checks, Step 3 — Output and Output contract, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ad Drift is an agent skill from CorridorTech/PoseCap. Read-only drift audit — compare AGENTS.md, ARCHITECTURE.md, ADR statuses, feature specs in doc/specs/, and documentation discipline against what the code actually does. Outputs a drift list, never writes files. Use when the user wants to audit, review for drift, sanity-check, or report inconsistencies between the repo's docs and its code.

Its SKILL.md is about 1.8k 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 Architecture decision records, PRD writing and Agent instruction files. The licence is Apache-2.0.

When your agent uses it

  • The user wants to audit
  • Review for drift
  • Report inconsistencies between the repos docs and its code

Example prompts

  • “/ad-drift”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash

Workflow steps

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

  1. Decide what to audit
  2. Run checks
  3. Output

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Ad Drift loads about 1.8k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 861 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Bash

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 CorridorTech/PoseCap at commit 626701b, republished under its Apache-2.0 licence (© CorridorTech). 861 words, ~1,824 tokens.

Download SKILL.mdSave it as .claude/skills/ad-drift/SKILL.md (or your agent's skills folder).
name
ad-drift
description
Read-only drift audit — compare AGENTS.md, ARCHITECTURE.md, ADR statuses, feature specs in doc/specs/, and documentation discipline against what the code actually does. Outputs a drift list, never writes files. Use when the user wants to audit, review for drift, sanity-check, or report inconsistencies between the repo's docs and its code.
allowed-tools
Read, Glob, Grep, Bash
summary
Read-only drift report comparing AGENTS.md / ARCHITECTURE.md / ADRs against the code.

/ad-drift

Read-only. Produces a drift list comparing the repo's operational docs against what the code actually does. Writes nothing — the user decides whether to fix the spec or the code.

Step 1 — Decide what to audit

If the user names an artifact (AGENTS.md, ARCHITECTURE.md, ADRs, specs), audit only that. Otherwise audit all categories below.

Step 2 — Run checks

AGENTS.md drift (if present)
  • Stack — does the listed stack match package.json / pyproject.toml / Cargo.toml / go.mod / equivalent?
  • Setup/build/test commands — do they match package.json#scripts, Makefile, or pyproject.toml?
  • Quality gates — do referenced hook configs exist (.husky/, .pre-commit-config.yaml, .github/workflows/)?
  • Repository layout — do referenced directories exist?
  • Pre-approved commands — anything in the list missing from the toolchain?
ARCHITECTURE.md drift (if present)
  • Layers and boundaries — do the named directories exist? Sample 1–2 files per layer; are imports respecting the stated boundaries?
  • Patterns — sample one handler / one repository / one entry point. Do they follow the documented pattern?
  • No ## Active ADRs section — ARCHITECTURE.md must not duplicate the doc/adr/ directory index per ADR-0030 §2.
ADR drift (if doc/adr/ exists)
  • Numbering — gaps or duplicates in doc/adr/NNNN-*.md?
  • Status field — every ADR has one of proposed | accepted | deprecated | superseded by ADR-NNNN.
  • Superseded chains — every "superseded by ADR-NNNN" target exists.
Spec drift (if doc/specs/ exists)

Structural integrity only — does not deep-audit spec text against shipped code (deferred per ADR-0011 Consequences).

  • Numbering — gaps or duplicates in doc/specs/NNNN-*.md?
  • Status field — every spec has one of draft | accepted | shipped | superseded by SPEC-NNNN.
  • Superseded chains — every "superseded by SPEC-NNNN" target exists.
  • Reciprocity — every task under doc/tasks/NNNN-*.md whose Spec ref field is non-empty points to a spec that exists. And every spec with Status: accepted or shipped has at least one entry in its Related → Tasks list (an accepted spec with no implementing task is a smell).
  • No checkbox UI — per ADR-0030 §1, Spec is decision-record (not tracking). Functional Requirements / Non-functional Requirements / Success Criteria sections must use plain bullets, not - [ ] checkboxes; implementation tracking lives in per-Spec tasks.
  • Status / task aggregate alignment — when every task that references a spec is done, the spec's Status should be shipped. A spec with all tasks done but Status: accepted is drift between work-unit completion and feature-level claim.
Documentation discipline drift (WORKFLOW.md §2 / ADR-0008)

Audit narrative documents — README.md, AGENTS.md / CLAUDE.md, ARCHITECTURE.md, DESIGN.md, and prose pages under doc/ that are not lifecycle-managed artifacts under doc/product/, doc/specs/, doc/adr/, or doc/tasks/:

  • Emoji — any present? Rule 3 forbids emoji anywhere (docs, code, comments, commits, skill outputs).
  • Dates / version stamps / DRAFT markers / changelog blocks in narrative documents — Rule 2 forbids these. Lifecycle-managed artifacts under doc/product/, doc/specs/, doc/adr/, and doc/tasks/ are exempt.
  • Business context first — does the first paragraph answer why the document exists, before what and how? Rule 4.
  • Scope duplication — does the document copy material that is canonically owned by another file (AGENTS.md repeating ARCHITECTURE.md patterns; README.md re-stating ADR rationale)? Rule 5 requires linking, not copying.
  • Speculation — phrases like "we might", "in the future", "could be added", or roadmaps without an ADR / task reference. Rule 1 forbids unfounded plans.

Source code (sample, not exhaustive — flag findings, not every match):

  • Orphan TODO / FIXME — Rule 7. A reference to a GitHub Issue or a doc/tasks/NNNN-*.md task file makes it not orphan.
  • Commented-out code blocks — Rule 7. Removed code lives in git history.
Show full SKILL.md (332 more words)Show less
Single-responsibility drift (ADR-0030)

Per WORKFLOW §2 rules #9–#12, definition-layer documents do not take on tracking or duplicate other layers' indices, and WORKFLOW.md stays universal:

  • Definition-layer tracking UI (Rule #9) — grep ^- \[ \]\|^- \[x\] inside AGENTS.md, WORKFLOW.md, ARCHITECTURE.md, GUIDELINES.md, CONTEXT.md, doc/product/*.md. Findings: definition documents must not carry per-item checkbox UI. Exception: fenced code blocks showing template examples (e.g., PR-body shape) are illustrative, not pillar tracking.
  • Directory-as-index duplication (Rule #10) — flag sections that re-state another layer's index. Concrete patterns: ## Active ADRs inside ARCHITECTURE.md or AGENTS.md; multi-bullet ## Architectural Principles digests that paraphrase each ADR; PRD ## Related → ADRs bullet lists that enumerate the kit's ADR ledger.
  • Kit-state in WORKFLOW.md (Rule #12) — grep ADR-[0-9]\{4\} in WORKFLOW.md. Universal philosophy must not cite kit-specific ADR numbers (downstream installs receive WORKFLOW.md without doc/adr/). Literature citations (named books / papers) and generic doc/adr/ directory references are allowed.
  • Cross-references that are decoration (Rule #11) — sample inline ADR refs (per ADR-NNNN) in narrative documents and apply the load-bearing test: if you delete the reference and the surrounding statement still stands, the reference was decoration; flag it. Judgment-call; surface as findings, not as automated reject.

Step 3 — Output

One line per finding, formatted:

[file or section]: spec says X, code says Y. Suggested resolution: change spec / change code / discuss.

Group by artifact. If a category has no drift, print one line: AGENTS.md — no drift. etc. If an audited artifact does not exist, say so explicitly rather than reporting zero findings. The Documentation discipline drift category groups its own findings under Documentation discipline — <category>: ....

If something the user says contradicts what the code shows, surface the conflict. Don't silently trust the user; don't silently trust the code.

Output contract

A drift list, no file written. Read-only operation. Empty result is reported explicitly ("no drift found across audited artifacts"), not silently. Missing artifacts are flagged, not skipped.

Next

  • Address each finding with one of the three resolutions named in the format ("change spec / change code / discuss").
  • For findings that require implementation: /ad-task to scaffold the fix.
  • For workflow drift (where am I, what's stuck): /ad-next.
  • For kit-version drift (state file behind current kit): agentic update.

© CorridorTech, Apache-2.0. 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 .claude/skills/ad-drift of CorridorTech/PoseCap.

Open the folder on GitHubat commit 626701b

Compare with similar skills

Ad Drift 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.

Ad Drift compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ad Drift this skillCorridorTech/PoseCap220—~1.8kAutomated safety check: NotesApache-2.0
Rememberantonio-orionus/Arroxy389—~571Automated safety check: PassMIT
Documentationextra-org/extra113—~848Automated safety check: PassMIT
Expectationscitypaul/.dotfiles739—~1.2kAutomated safety check: PassCustom licence
Setuprvdbreemen/OTGW-firmware207—~964Automated safety check: PassGPL-3.0
ImportThinkfleetAI/memmesh419—~342Automated safety check: PassApache-2.0

Similar skills

  • Remember

    antonio-orionus/Arroxy

    Persists a durable Arroxy lesson — a gotcha, user preference, workflow rule, or design decision — to the right tracked file (project memory, AGENTS.md, CONTEXT.md, dev-docs, or an ADR) so any coding…

    389 GitHub stars~571 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Documentation

    extra-org/extra

    Keep the repository's documentation accurate, honest, and synchronized with the code.

    113 GitHub stars~848 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Expectations

    citypaul/.dotfiles

    Decide where a learning, gotcha, or decision should live so it is not lost, and capture it there while context is fresh.

    739 GitHub stars~1.2k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Setup

    rvdbreemen/OTGW-firmware

    One-time project setup for adr-kit. An agent skill from rvdbreemen/OTGW-firmware.

    207 GitHub stars~964 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Import

    ThinkfleetAI/memmesh

    Import memories into MemMesh from an exported file, a native MEMORY.md / CLAUDE.md, an ADR/decision log, or a mem0 export.

    419 GitHub stars~342 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Setup Matt Pocock Skills

    ywwynm/EverythingDone

    Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…

    144 GitHub starsUsed in 9 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

More from CorridorTech/PoseCap

All 15 skills in this repo

  • Ad Adr

    CorridorTech/PoseCap

    Draft a new ADR (Architecture Decision Record) at doc/adr/NNNN-<short-title.md, using Michael Nygard's Context/Decision/Consequences/Alternatives pattern.

    220 GitHub stars~1k tokensUpdated today
    Auto-check: notes

  • Ad Architecture

    CorridorTech/PoseCap

    Generate ARCHITECTURE.md at the repo root by scanning the code first, pre-filling layers/patterns/observability/deployment from observed signals, then asking only the genuine gaps.

    220 GitHub stars~1.5k tokensUpdated today
    Auto-check: notes

  • Ad Archive

    CorridorTech/PoseCap

    Hard-delete completed plan files (tasks Status:done, specs Status:shipped, PRDs Status:superseded, ADRs Status:superseded or deprecated) via git rm, leaving git history as the only ledger.

    220 GitHub stars~1.9k tokensUpdated today
    Auto-check: notes

  • Ad Hooks

    CorridorTech/PoseCap

    Scaffold deterministic quality gates per WORKFLOW.md §11 — pre-commit (lint, format, secret-scan), pre-push (build, unit, integration).

    220 GitHub stars~2.4k tokensUpdated today
    Auto-check: notes

  • Ad Next

    CorridorTech/PoseCap

    Survey the project's state across the six-layer artifact stack and recommend prioritized next actions, modeled on flutter doctor.

    220 GitHub stars~3.3k tokensUpdated today
    Auto-check: notes

  • Ad Bootstrap

    CorridorTech/PoseCap

    Generate AGENTS.md at the repo root by scanning the codebase first, pre-filling placeholders from observed signals, and asking only the genuine gaps.

    220 GitHub stars~2.4k tokensUpdated today
    Auto-check: warnings

Categories

Questions about Ad Drift

What does Ad Drift do?

Read-only drift audit — compare AGENTS.md, ARCHITECTURE.md, ADR statuses, feature specs in doc/specs/, and documentation discipline against what the code actually does. Ad Drift is an agent skill from CorridorTech/PoseCap.md, ADR statuses, feature specs in doc/specs/, and documentation discipline against what the code actually does.

When should I use Ad Drift?

Ad Drift fits situations like: the user wants to audit; review for drift; report inconsistencies between the repos docs and its code.

How do I install Ad Drift in Claude Code?

Run `npx skills add CorridorTech/PoseCap --skill ad-drift -a claude-code`. Or copy the skill folder (.claude/skills/ad-drift in CorridorTech/PoseCap) into .claude/skills/ad-drift in your project. Claude Code loads it when a task matches its description.

How do I install Ad Drift in Codex?

Run `npx skills add CorridorTech/PoseCap --skill ad-drift -a codex`. Or copy the skill folder (.claude/skills/ad-drift in CorridorTech/PoseCap) into .agents/skills/ad-drift in your project. Codex loads it when a task matches its description.

Can I use Ad Drift 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 CorridorTech/PoseCap --skill ad-drift -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ad-drift, .gemini/skills/ad-drift, .github/skills/ad-drift and .opencode/skills/ad-drift in your project.

What does Ad Drift need to run?

SKILL.md names no scripts, command-line tools or credentials: Ad Drift is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash.

Does Ad Drift access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ad Drift safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ad Drift use?

Ad Drift is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ad Drift use?

About 1.8k tokens (SKILL.md is roughly 7.3k 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 Ad Drift?

Skills that share tags, products or a category with Ad Drift: Remember (antonio-orionus/Arroxy, 389 stars), Documentation (extra-org/extra, 113 stars), Expectations (citypaul/.dotfiles, 739 stars) and Setup (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ad Drift?

CorridorTech (a GitHub organization) maintains it in CorridorTech/PoseCap, which has 220 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

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