Atdd Mutate
swingerman/engineer
A skill your agent uses to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs.
A skill your agent uses when implementing, reviewing, or debugging a Gherkin acceptance-test pipeline with mutation testing.
Install Acceptance Pipeline Catalog
$ npx skills add pproenca/dot-skills --skill acceptance-pipeline-catalog -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pproenca/dot-skills acceptance-pipeline-catalog --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/acceptance-pipeline-catalog .claude/skills/acceptance-pipeline-catalog && rm -rf skills-srcUse ~/.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/
Install the "acceptance-pipeline-catalog" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/acceptance-pipeline-catalog into .claude/skills/acceptance-pipeline-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-pipeline-catalog", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/acceptance-pipeline-catalogType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pproenca/dot-skills --skill acceptance-pipeline-catalog -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pproenca/dot-skills acceptance-pipeline-catalog --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/acceptance-pipeline-catalog .agents/skills/acceptance-pipeline-catalog && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "acceptance-pipeline-catalog" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/acceptance-pipeline-catalog into .agents/skills/acceptance-pipeline-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-pipeline-catalog", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill acceptance-pipeline-catalog -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pproenca/dot-skills acceptance-pipeline-catalog --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/acceptance-pipeline-catalog .cursor/skills/acceptance-pipeline-catalog && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "acceptance-pipeline-catalog" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/acceptance-pipeline-catalog into .cursor/skills/acceptance-pipeline-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-pipeline-catalog", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/acceptance-pipeline-catalog--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pproenca/dot-skills --skill acceptance-pipeline-catalog -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pproenca/dot-skills acceptance-pipeline-catalog --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/acceptance-pipeline-catalog .gemini/skills/acceptance-pipeline-catalog && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "acceptance-pipeline-catalog" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/acceptance-pipeline-catalog into .gemini/skills/acceptance-pipeline-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-pipeline-catalog", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pproenca/dot-skills acceptance-pipeline-catalogInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pproenca/dot-skills --skill acceptance-pipeline-catalog -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/acceptance-pipeline-catalog .github/skills/acceptance-pipeline-catalog && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "acceptance-pipeline-catalog" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/acceptance-pipeline-catalog into .github/skills/acceptance-pipeline-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-pipeline-catalog", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill acceptance-pipeline-catalog -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pproenca/dot-skills acceptance-pipeline-catalog --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/acceptance-pipeline-catalog .opencode/skills/acceptance-pipeline-catalog && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "acceptance-pipeline-catalog" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/acceptance-pipeline-catalog into .opencode/skills/acceptance-pipeline-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-pipeline-catalog", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
acceptance-pipeline-catalog- GitHub stars
- 215
- Token cost
- ~2.2k tokens
- SKILL.md length
- 665 words
- Files
- 56 (incl. references)
- Skills in repo
- 41
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when implementing, reviewing, or debugging a Gherkin acceptance-test pipeline with mutation testing.
- Works in 12 steps: Parser (CRITICAL) → JSON IR (CRITICAL) → Generator (CRITICAL) → …
- Debugging a Gherkin acceptance-test pipeline with mutation testing
- SKILL.md covers When to Apply, Pipeline Overview, Rule Categories by Priority and Quick Reference, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Acceptance Pipeline Catalog is an agent skill from pproenca/dot-skills. Use when implementing, reviewing, or debugging a Gherkin acceptance-test pipeline with mutation testing. Covers parser, JSON IR, generator, runtime, step handlers, test runner, mutator, value mutation rules, execution, result classification, reporting, project layout, conformance, and agent setup. Based on Uncle Bob's Acceptance Pipeline Specification. Trigger even when the user mentions Gherkin parsing, acceptance test generation, mutation testing for acceptance tests, or building a portable test pipeline.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 56 other files, including reference files (for example `gotchas.md`, `metadata.json` and `references/_sections.md`).
It sits in Testing & QA, covering End-to-end testing and Test coverage. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.
When your agent uses it
- Debugging a Gherkin acceptance-test pipeline with mutation testing
- Even when the user mentions Gherkin parsing
- Acceptance test generation
- Mutation testing for acceptance tests
Example prompts
- “/acceptance-pipeline-catalog”
Workflow steps
12 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cf93c57. 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
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
Acceptance Pipeline Catalog loads about 2.2k tokens when it runs, and up to ~38k if it reads all its reference files. Until then it costs about 135 tokens; SKILL.md has 665 words of instructions outside code blocks.
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 pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 665 words, ~2,229 tokens.
Download SKILL.mdSave it as
.claude/skills/acceptance-pipeline-catalog/SKILL.md (or your agent's skills folder). This skill also uses 55 other files; get the full folder from GitHub.- name
- acceptance-pipeline-catalog
- description
- Use when implementing, reviewing, or debugging a Gherkin acceptance-test pipeline with mutation testing. Covers parser, JSON IR, generator, runtime, step handlers, test runner, mutator, value mutation rules, execution, result classification, reporting, project layout, conformance, and agent setup. Based on Uncle Bob's Acceptance Pipeline Specification. Trigger even when the user mentions Gherkin parsing, acceptance test generation, mutation testing for acceptance tests, or building a portable test pipeline.
Robert C. Martin Acceptance Pipeline Best Practices
Language-neutral specification for a portable acceptance-test pipeline: Gherkin feature files to JSON IR to generated acceptance tests to mutation testing. Based on Robert C. Martin's Acceptance Pipeline Specification. Contains ~50 rules across 14 categories, prioritized by impact.
When to Apply
Reference these rules when:
- Building a Gherkin parser that outputs JSON IR
- Implementing an acceptance test generator from JSON IR
- Writing an acceptance runtime that expands scenarios and dispatches steps
- Implementing mutation testing for acceptance test example values
- Setting up the full pipeline (parser, generator, runner, mutator) in a new project
- Debugging pipeline failures (parse errors, generation issues, mutation classification)
Pipeline Overview
The pipeline has two modes:
Normal acceptance run:
feature file -> gherkin parser -> JSON IR -> acceptance generator -> generated tests -> test runnerMutation run:
feature file -> gherkin parser -> base JSON IR -> mutator (one changed IR per mutation)
-> generator (tests per mutation) -> test runner (evaluate each) -> mutation reportThe normal run proves the project satisfies the feature. The mutation run probes whether tests are strong enough to fail when example data changes.
Rule Categories by Priority
| Priority | Category | Impact | Prefix | Rules |
|---|---|---|---|---|
| 1 | Parser | CRITICAL | parser- | 9 |
| 2 | JSON IR | CRITICAL | ir- | 4 |
| 3 | Generator | CRITICAL | gen- | 2 |
| 4 | Runtime | HIGH | rt- | 3 |
| 5 | Step Handlers | HIGH | handler- | 4 |
| 6 | Test Runner | HIGH | runner- | 2 |
| 7 | Mutator Core | HIGH | mut- | 4 |
| 8 | Value Mutation Rules | HIGH | val- | 10 |
| 9 | Result Classification | HIGH | result- | 2 |
| 10 | Conformance | HIGH | conform- | 1 |
| 11 | Agent Setup | HIGH | setup- | 1 |
| 12 | Mutation Execution | MEDIUM | exec- | 4 |
| 13 | Reports | MEDIUM | report- | 3 |
| 14 | Project Layout | MEDIUM | layout- | 3 |
Quick Reference
1. Parser (CRITICAL)
parser-command-interface- Two positional args, exit codes 0/1/2parser-feature-declaration- Feature: keyword required, trimmed nameparser-background- Optional Background: section with Given/And stepsparser-scenarios- Scenario: and Scenario Outline: both supportedparser-steps- Given/When/Then/And keywords, keyword stored separatelyparser-parameters- Angle-bracket placeholders, not expanded by parserparser-examples-tables- Pipe-delimited tables, header row firstparser-general-rules- Blank lines, comments, whitespace, orderingparser-unsupported-syntax- Tags, rules, localized keywords, doc strings
2. JSON IR (CRITICAL)
ir-feature-object- name, scenarios, optional backgroundir-scenario-object- name, steps, examples arraysir-step-object- keyword, text, optional parametersir-example-object- String-keyed, string-valued maps
3. Generator (CRITICAL)
gen-command-interface- Two positional args, exit codes 0/1/2gen-requirements- Embed IR, no Gherkin parsing, deterministic output
4. Runtime (HIGH)
rt-responsibilities- Load IR, expand, dispatch, reportrt-scenario-expansion- One execution per example row, background prependedrt-execution-naming- Scenario name / example index naming convention
5. Step Handlers (HIGH)
handler-matching- Match by exact text value, not keywordhandler-world-state- Fresh world/state per scenario executionhandler-value-handling- Fetch, parse, fail on missing/malformedhandler-unsupported- Unsupported step text must fail the test
Show full SKILL.md (272 more words)Show less
6. Test Runner (HIGH)
runner-interface- Input/output contract for the test runner adapterrunner-classification- Three-way: failure, success, infrastructure error
7. Mutator Core (HIGH)
mut-command-interface- CLI options, exit codes 0/1/2mut-scope- Only example cell values mutatedmut-identity- Stable deterministic IDs, paths, descriptionsmut-deep-copy- Original IR never modified in place
8. Value Mutation Rules (HIGH)
val-rule-order- 8 rules applied in priority orderval-comma-list- Comma-delimited list mutationval-boolean- true/false toggleval-null- null/nil/none to dithered stringval-integer- Integer plus pseudo-random deltaval-float- Float plus pseudo-random deltaval-datetime- ISO-8601 date/time shiftval-duration- Duration shift preserving syntaxval-string-dither- Character-level string editsval-determinism- Pseudo-random, deterministic for fixed input
9. Result Classification (HIGH)
result-statuses- killed, survived, errorresult-classification-rules- Mapping from test outcomes to statuses
10. Conformance (HIGH)
conform-checklist- All 21 validation items
11. Agent Setup (HIGH)
setup-checklist- 15-step installation guide
12. Mutation Execution (MEDIUM)
exec-work-directory- Per-mutation directory structureexec-workflow- Write IR, generate, run, classifyexec-parallelism- Concurrent workers, isolated directoriesexec-timeout- Full-run timeout, unfinished = error
13. Reports (MEDIUM)
report-text-format- Summary line + per-result linesreport-json-format- JSON object with summary and results arrayreport-field-requirements- Required fields for summary and results
14. Project Layout (MEDIUM)
layout-required-paths- features/, build/, acceptance/ directorieslayout-commands- gherkin-parser, acceptance-generator, gherkin-mutatorlayout-scripts- Normal acceptance and mutation scripts
How to Use
Read individual reference files for detailed spec requirements and rationale:
- Start with the category relevant to the component you are building
- Each rule file is self-contained with WHY explanations, spec requirements, and examples
- For a new project setup, read
setup-checklistfirst - For validation, use
conform-checklist - Check gotchas.md for known failure points
Reference Files
| File | Description |
|---|---|
| metadata.json | Version and reference information |
| gotchas.md | Known failure points (append-only) |
| references/ | All rule files organized by prefix |
© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 55 other files (references) in skills/.experimental/acceptance-pipeline-catalog of pproenca/dot-skills.
- SKILL.md
- gotchas.md
- metadata.json
- references/_sections.md
- references/conform-checklist.md
- references/exec-parallelism.md
- references/exec-timeout.md
- references/exec-work-directory.md
- references/exec-workflow.md
- references/gen-command-interface.md
- references/gen-requirements.md
- references/handler-matching.md
- references/handler-unsupported.md
- references/handler-value-handling.md
- references/handler-world-state.md
- references/ir-example-object.md
- references/ir-feature-object.md
- references/ir-scenario-object.md
- references/ir-step-object.md
- references/layout-commands.md
- … and 36 more
Open the folder on GitHubat commit cf93c57
Compare with similar skills
Acceptance Pipeline Catalog 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Acceptance Pipeline Catalog this skillpproenca/dot-skills | 215 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Atdd Mutateswingerman/engineer | 154 | — | ~2.7k | Automated safety check: Pass | MIT | |
| E2E Test ThinkerUniClipboard/UniClipboard | 1.9k | — | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Check Test Coverageopenshift/oc-mirror | 124 | — | ~853 | Automated safety check: Pass | Apache-2.0 | |
| E2E Test Creatorletehaha/moneymatter | 160 | — | ~2.4k | Automated safety check: Warn | AGPL-3.0 | |
| Platform Dsar Policy Manageforcedotcom/sf-skills | 1.1k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
E2E Test Thinker
UniClipboard/UniClipboard
Analyze the current branch's diff against main and determine which changes are testable via CLI-based end-to-end tests.
Check Test Coverage
openshift/oc-mirror
Analyze oc-mirror CLI feature coverage across integration and e2e tests, identifying untested features and gaps
E2E Test Creator
letehaha/moneymatter
Creates backend e2e tests for new or existing endpoints. An agent skill from letehaha/moneymatter.
Platform Dsar Policy Manage
forcedotcom/sf-skills
Configure, run, and audit DsarPolicy Right-to-Portability exports end to end: author the data map over a subject's related records, resolve a request's subject (email/name/id) to a root-entity…
Post Dev Test
sd0xdev/sd0x-harness
Post-development test completion. An agent skill from sd0xdev/sd0x-harness.
More from pproenca/dot-skills
All 41 skills in this repoAudio Voice Recovery
pproenca/dot-skills
Audio forensics and voice recovery guidelines for CSI-level audio analysis.
Codemod React Pipeline
pproenca/dot-skills
Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
Language Spec Author
pproenca/dot-skills
Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…
Python Pep Author
pproenca/dot-skills
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…
Related
Categories
Questions about Acceptance Pipeline Catalog
What does Acceptance Pipeline Catalog do?
A skill your agent uses when implementing, reviewing, or debugging a Gherkin acceptance-test pipeline with mutation testing. Acceptance Pipeline Catalog is an agent skill from pproenca/dot-skills. Use when implementing, reviewing, or debugging a Gherkin acceptance-test pipeline with mutation testing.
When should I use Acceptance Pipeline Catalog?
Acceptance Pipeline Catalog fits situations like: debugging a Gherkin acceptance-test pipeline with mutation testing; even when the user mentions Gherkin parsing; acceptance test generation; mutation testing for acceptance tests.
How do I install Acceptance Pipeline Catalog in Claude Code?
Run `npx skills add pproenca/dot-skills --skill acceptance-pipeline-catalog -a claude-code`. Or copy the skill folder (skills/.experimental/acceptance-pipeline-catalog in pproenca/dot-skills) into .claude/skills/acceptance-pipeline-catalog in your project. Claude Code loads it when a task matches its description.
How do I install Acceptance Pipeline Catalog in Codex?
Run `npx skills add pproenca/dot-skills --skill acceptance-pipeline-catalog -a codex`. Or copy the skill folder (skills/.experimental/acceptance-pipeline-catalog in pproenca/dot-skills) into .agents/skills/acceptance-pipeline-catalog in your project. Codex loads it when a task matches its description.
Can I use Acceptance Pipeline Catalog 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 pproenca/dot-skills --skill acceptance-pipeline-catalog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/acceptance-pipeline-catalog, .gemini/skills/acceptance-pipeline-catalog, .github/skills/acceptance-pipeline-catalog and .opencode/skills/acceptance-pipeline-catalog in your project.
What does Acceptance Pipeline Catalog need to run?
SKILL.md names no scripts, command-line tools or credentials: Acceptance Pipeline Catalog is instructions for the agent only.
Does Acceptance Pipeline Catalog 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 Acceptance Pipeline Catalog 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 Acceptance Pipeline Catalog use?
Acceptance Pipeline Catalog 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 Acceptance Pipeline Catalog use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 36k tokens, read only when the agent opens those files.
What are the alternatives to Acceptance Pipeline Catalog?
Skills that share tags, products or a category with Acceptance Pipeline Catalog: Atdd Mutate (swingerman/engineer, 154 stars), E2E Test Thinker (UniClipboard/UniClipboard, 1.9k stars), Check Test Coverage (openshift/oc-mirror, 124 stars) and E2E Test Creator (letehaha/moneymatter, 160 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Acceptance Pipeline Catalog?
pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 215 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on August 15, 2026.
Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.