agentleFS
clnnnclnnn/playbook/.agents/skills/setup-playbook/SKILL.md

setup-playbook

Skill0 starsChanged 5 days agoMITView on GitHub

Configure this repo for the playbook: run setup-matt-pocock-skills, then wire in the playbook's extensions to those skills. Run once, and again after installing a new extension.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the Skill tool refuses the call, stop and tell the user to run /setup-matt-pocock-skills, then /setup-playbook again.

    line 15
  2. Distinctive:

    Check which extensions are installed: a skill folder alongside this one, or the name in your available skills.

    line 23
  3. Very specific:

    When Verification is wired in and no verify-* skill exists: if the app runs, tell the user to run /create-verification-skill in a new …

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup Playbook

The playbook extends the vendored engineering skills without editing them: each extension is a skill of its own, and a pointer in AGENTS.md tells the agent when to load it. This skill writes those pointers.

1. Base setup

Call the Skill tool with "setup-matt-pocock-skills" and follow it through its "Done" step; when it asks which instructions file to create, recommend AGENTS.md. Done when its ## Agent skills block and docs/agents/*.md are written. When ## Agent skills already exists, ask whether to re-run it (recommended: no) and skip to step 2 on no.

If the Skill tool refuses the call, stop and tell the user to run /setup-matt-pocock-skills, then /setup-playbook again.

2. Instructions file

The playbook keeps one instructions file: AGENTS.md, which the playbook's other skills also write to. Claude Code reads it natively when no CLAUDE.md exists. When CLAUDE.md also exists, Claude Code reads only CLAUDE.md: tell the user, and offer to add an @AGENTS.md line to it.

3. Extensions

Check which extensions are installed: a skill folder alongside this one, or the name in your available skills.

ExtensionSub-blockDoc fileSeed
property-testing### Testingdocs/agents/testing.mdtesting.md
create-verification-skill### Verificationdocs/agents/verification.mdverification.md

Draft the ## Playbook extensions block for AGENTS.md, including a sub-block only for an installed extension:

## Playbook extensions

### Testing

Property-based testing extends `tdd` and `diagnosing-bugs`. See `docs/agents/testing.md`.

### Verification

The `verify-<app>` skill proves changes in the running app for `implement`, `implement-spec`, `pr`, `triage`, `diagnosing-bugs` and `retro`. See `docs/agents/verification.md`.

Draft each installed extension's doc file from its seed. Show the drafts and let the user edit before writing. Then write: update the ## Playbook extensions block and each sub-block in place when they exist, create them otherwise, and leave ## Agent skills and every other section as they are. Done when every installed extension has its sub-block and doc file. When none is installed, skip this step and say so in step 4.

4. Done

Name each extension wired in, the skill it extends, and the doc file holding its rules. Those files can be edited directly later; re-run this skill after installing a new extension.

When Verification is wired in and no verify-* skill exists: if the app runs, tell the user to run /create-verification-skill in a new session; otherwise, tell them it comes once the walking skeleton runs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.