change-control
Skill1 starsChanged 4 months agoNo licenceView on GitHub
The change policy for this repo (nic095layson/claude, the claude-council skill library). Load BEFORE editing any tracked file when you need to answer "am I allowed to change this, and what gate must the change pass?" — e.g. before rewording SKILL.md prose, touching a skill's frontmatter description, rebuilding files.zip or a .skill artifact, editing the README, or adding a new skill directory. Also load when asked "what are the non-negotiables here" or "in what order does the edit→eval→release pipeline run". Do NOT load for how to run evals (validation-and-evals), how to rebuild artifacts step by step or the release process mechanics (release-and-packaging), or how to turn a wording hunch into evidence (research-methodology) — this skill only tells you which gate applies and in what order the pipeline runs.
In this repository14 other files it gives its agents.
- architecture-contractSkill
- build-and-envSkill
- claude-councilSkill
- debugging-playbookSkill
- diagnostics-and-toolingSkill
- docs-and-writingSkill
- domain-referenceSkill
- eval-harness-campaignSkill
- failure-archaeologySkill
- logic-treeSkill
- release-and-packagingSkill
- research-methodologySkill
- skill-authoringSkill
- validation-and-evalsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.

