agentleFS
seancabalseseancabalse/agentic-playbook/skills/customize/SKILL.md

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

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.
  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • +10 more from microsoft

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
  1. Distinctive:

    Check the readers: Search the skills and agents for the path, and confirm that each still makes sense with the change: a renamed section, …

    line 17

“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.

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

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.

  1. 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 in AGENTS.md → "This project" instead: say so, and stop.
  2. 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's templates/adr.md"): the copy is shared, and the playbook's location differs per person and per install.
  3. 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.
  4. 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.
  5. 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.

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.