customize
Skill0 starsChanged 15 days agoMITView on GitHub
Change a playbook default for this project only, with a copy in .playbook/local/. Run only when the user asks.
43 other projects use a version of this.
Adopted by
Most recently taken up by
- bouob/claude-statuslinetheir own version, first seen Nov 15, 2026
- shivasaini04/nanocrewtheir own version, first seen Nov 15, 2026
- nanocoai/nanoclawtheir own version, first seen Nov 15, 2026
- HughYau/AcademicForgetheir own version, first seen Nov 8, 2026
- microsoft/frontier-ai-governance-rvastheir own version, first seen Oct 25, 2026
- JonathanChan-geek/claude-science-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use add-discord, add-slack and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilladd-discord
Add Discord bot channel integration via Chat SDK.
Also in 11 projects that use this
MicrosoftSkilladd-slack
Add Slack channel integration via Chat SDK.
Also in 11 projects that use this
- +10 more from microsoft
Other versions43 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 43
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- anthropics/claude-for-legal★ 9.5ksame name
- anthropics/defending-code-reference-harness★ 7.5ksame name
- microsoft/skills★ 3.2ksame name
- microsoft/agent-skills★ 3.2ksame name
- HughYau/AcademicForge★ 2.6ksame name
- microsoft/azure-skills★ 1.6ksame name
- xuzhougeng/wisp-science★ 1.1ksame name
33 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- architecture-reviewSkill
- bootstrap-projectSkill
- capture-screenshotsSkill
- deliver-featureSkill
- design-reviewSkill
- docs-upkeepSkill
- fix-bugSkill
- handoffSkill
- implementSkill
- leadSkill
- log-decisionSkill
- refine-requirementsSkill
- release-readinessSkill
- reproduce-in-worktreeSkill
- security-auditSkill
- ship-prSkill
- start-taskSkill
- sync-branchSkill
- threat-modelSkill
- verify-featureSkill
- vet-dependencySkill
- write-adrSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Check the readers: Search the skills and agents for the path, and confirm that each still makes sense with the change: a renamed section, …
“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Customise the playbook for this project
Request: $ARGUMENTS
The playbook's files stay general. A project changes one by keeping its own copy at the same path under .playbook/local/, which wins over the default everywhere. The session-start hook lists the overrides for plugin users, and the core rules in AGENTS.md say to check there first.
- Find the file. Match the request to a path under
${CLAUDE_PLUGIN_ROOT}/(principles/,templates/,stacks/,trackers/). If several fit, list them and ask. Rules that only apply here, and need no playbook file, belong inAGENTS.md→ "This project" instead: say so, and stop. - Copy it, unless the project already overrides it: from
${CLAUDE_PLUGIN_ROOT}/<path>to.playbook/local/<path>, creating folders as needed. Where the copy names other playbook files by a full path, write them as playbook-relative paths instead ("the playbook'stemplates/adr.md"): the copy is shared, and the playbook's location differs per person and per install. - Make the change the user asked for, and only that, keeping the file's structure so the skills that read it still find their sections. Add a one-line HTML comment at the top: what was changed, why, and the date.
- Check the readers. Search the skills and agents for the path, and confirm that each still makes sense with the change: a renamed section, or a removed step a skill relies on, needs the skill's input adjusted. Tell the user about anything that conflicts.
- Record it. Log the decision with
log-decision("Project override of<path>:<why>"). Remind the user to commit.playbook/local/; it's shared with everyone on the project.
To drop an override, delete the file from .playbook/local/; the default applies again at the next session.
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
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.

