update-toolkit
Skill1 starsChanged 27 days agoMITView on GitHub
Conductor-only meta skill. How to add, modify or retire a role, skill, slash command, or behavioral rule as the project grows. Use when the workflow needs a new procedure, entry point, or specialist role, or when one drifts or goes unused.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- thensls/nsls-builder-toolkittheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- thensls/nsls-builder-toolkit★ 0same name
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 repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adversarial-reviewSkill
- clean-architectureSkill
- decision-recordingSkill
- design-system-checkSkill
- dispatch-handoffSkill
- feature-branchingSkill
- finding-dispositionSkill
- git-recoverySkill
- gotcha-recordingSkill
- human-checkpointSkill
- plan-reviewSkill
- plan-writingSkill
- pr-createSkill
- simplicity-ladderSkill
- spec-writingSkill
- subagent-contractSkill
- subagent-dispatchSkill
- tdd-loopSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 2 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Read 2–3 existing files of the target kind first to match tone and structure.
- Very specific: line 22
Create .claude/skills/<name>/SKILL.md (directory per skill.
- Very specific: line 29
Modify: Update description if triggers change.
- Very specific: line 32
Always re-read frontmatter after editing and quote values containing : or # or starting with [, {, or quotes.
- Very specific: line 37
Create .claude/commands/project/<name>.md (served as /project:<name>).
- Very specific: line 41
Add to .claude/rules/workflow.md § Commands, update docs/wiki/commands.md if applicable, and commit feat: add /project:<name> — <reason>.
- Very specific: line 43
Modify: Keep argument-hint, Argument:, and consuming steps in sync.
- Very specific: line 58
Add to .claude/rules/workflow.md § Roles, wire into the dispatching command, and restart Claude Code to load.
- Very specific: line 60
Modify: Follow subagent-dispatch § Changing a role's model or effort for model/effort changes.
- Distinctive: line 65
What-is textbook prose: instead of project procedure.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Updating the Toolkit
Decide which artifact first
- Skill — a procedure loaded by task content ("when X, do these steps"). Default choice for domain knowledge.
- Command — a human-invoked
/project:*entry point orchestrating branches, dispatches, and wiki updates. Keep thin; put procedures in skills. - Role — a subagent with a distinct context scope or conflicting invariants ("never write code" vs "always write code"). Default to no; never create domain roles ("backend agent").
- Rule — a universal session invariant added as the next number in
.claude/rules/behavioral.md(never renumber). Project-specific traps go indocs/wiki/gotchas.md. - Wiki page — facts about the system (
docs/wiki/concepts/).
Read 2–3 existing files of the target kind first to match tone and structure. Keep bodies concise: every line is paid for on load. Commit each add/modify/retire with a chore log entry per log-and-commit.md (rule 19) and push.
Skills
Add:
- Create
.claude/skills/<name>/SKILL.md(directory per skill; supporting templates sit besideSKILL.md). - Frontmatter:
name(kebab-case), a specificdescriptionstarting withConductor-only.orSubagent-side, preloaded into <role>.(orSubagent-side, loaded on demand by <role>.) followed by what it does and trigger phrases, anduser-invocable: false. Never setdisable-model-invocation: trueon a preloaded skill. - Body = procedure (rule 14): when it fires → Read first → numbered Steps → wiki updates → project-specific Anti-patterns. Omit textbook explanations and historical rationale.
- Scope discipline: A skill preloaded into or invoked by a subagent must obey that role's constraints (no git commits, no direct edits to
todos.md/wiki-todos.md/log.md→ useFollow-ups:). Split procedures with both subagent and conductor steps into two skills (e.g.adversarial-review/finding-disposition). - Attach to a role: Preload in
skills:only if needed on almost every dispatch of that role; if needed only occasionally bydeveloper, leave it offskills:sodeveloperloads it on demand via theSkilltool. Two roles never share a procedure skill (onlysubagent-contractis shared). - List in
.claude/rules/workflow.md § Skillsand commitfeat: add <name> skill — <reason>.
Modify: Update description if triggers change; verify cited wiki pages exist. Commit refactor: <name> skill — <reason>.
Retire: Grep .claude/ and docs/wiki/ (including role skills: lists), delete the directory, commit chore: retire <name> skill.
Always re-read frontmatter after editing and quote values containing : or # or starting with [, {, or quotes.
Commands
Add:
- Create
.claude/commands/project/<name>.md(served as/project:<name>). - Frontmatter: one-line
description, quotedargument-hint('[scope — e.g. "the auth module"]'), anddisable-model-invocation: true. - Under H1, write
**Argument:** \$ARGUMENTS`and specify what it overrides, its shapes, what empty means, and what it cannot bypass (preconditions, Red, human checkpoints). Wire$ARGUMENTS` into the consuming step. - Body: Preconditions → numbered Steps → Failure modes → wiki updates → human checkpoints. Keep
!backtick`` live-state injections fast and read-only. - Add to
.claude/rules/workflow.md § Commands, updatedocs/wiki/commands.mdif applicable, and commitfeat: add /project:<name> — <reason>.
Modify: Keep argument-hint, **Argument:**, and consuming steps in sync. Commit refactor: /project:<name> — <reason>.
Retire: Grep .claude/, delete file, remove from workflow.md, commit chore: retire /project:<name>.
Roles
Add:
- Create
.claude/agents/<name>.md. - Frontmatter:
nameanddescriptionnaming the command step that dispatches it.model(opusfor high-leverage reasoning;sonnetfor per-cycle execution) andeffort(medium,high, orxhigh).tools: explicit list (read-only roles getRead, Grep, Glob, Bash, PowerShell; never grantAgent).permissionMode:dontAskfor read-only roles or roles bounded by.claude/settings.jsonpath allowlists (Edit(/docs/wiki/**),Edit(/docs/raw/research/**));acceptEditsfor source writers.skills:subagent-contractfirst, then role-specific preloads.maxTurnsand a uniquecolor. Omitmemoryandisolation: worktree.
- Body: role statement → Entry checklist → procedure → Report format → What you do NOT do.
- Add to
.claude/rules/workflow.md § Roles, wire into the dispatching command, and restart Claude Code to load. Commitfeat: add <name> role.
Modify: Follow subagent-dispatch § Changing a role's model or effort for model/effort changes. Commit refactor: <name> role — <reason>.
Retire: Confirm no command dispatches it, delete file, remove from workflow.md, commit chore: retire <name> role.
Anti-patterns
- What-is textbook prose instead of project procedure.
- Generic descriptions that route on unrelated tasks.
- Duplicate procedures across skills or roles.
- Granting Edit tools to read-only roles.
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.

