docs-and-writing
Skill1 starsChanged 4 months agoNo licenceView on GitHub
How to maintain the documents of record in this repo (nic095layson/claude, the claude-council skill library) — which doc owns which truth, the house style, and copy-paste templates for new-skill README sections, eval cases, incident entries, and Provenance sections. Load when editing README.md, writing prose in any library SKILL.md (house style and templates), documenting a new skill, or when asked "where does this get written down?", "is the README up to date?", "what's the doc style here?". Do NOT load for the skill-body authoring checklist (skill-authoring), for recording an incident's facts (failure-archaeology owns the log), for change gating (change-control), or for shipping docs inside release artifacts (release-and-packaging).
In this repository14 other files it gives its agents.
- architecture-contractSkill
- build-and-envSkill
- change-controlSkill
- claude-councilSkill
- debugging-playbookSkill
- diagnostics-and-toolingSkill
- 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
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
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.

