agent-skills
CLAUDE.md31 starsChanged 6 months agoMITView on GitHub
Do NOT add a name field to skill frontmatter. The name field overrides the skill's display prefix, causing it to show an incorrect or generic name instead of the proper namespaced prefix (e.g. codagent:handoff). Every PR must include a release. Run the release skill (.claude/skills/release) before creating or pushing a PR so the branch carries the version bump and changelog entry. Do not open a PR without it.
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Do NOT add a name field to skill frontmatter.
- Very specific: line 9
Every PR must include a release.
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md 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
Agent Skills — Development Notes
Skill frontmatter
Do NOT add a name field to skill frontmatter. The name field overrides the skill's display prefix, causing it to show an incorrect or generic name instead of the proper namespaced prefix (e.g. codagent:handoff).
Releases
Every PR must include a release. Run the release skill (.claude/skills/release) before creating or pushing a PR so the branch carries the version bump and changelog entry. Do not open a PR without it.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- releaseSkill
- releaseSkill
- ask-questionsSkill
- call-agentSkill
- designSkill
- finalize-prSkill
- fix-prSkill
- handoffSkill
- implement-changeSkill
- initSkill
- orchestrate-changeSkill
- plan-tasksSkill
- prepare-acceptanceSkill
- proposal-reviewSkill
- proposeSkill
- push-prSkill
- review-approachSkill
- review-assumptionsSkill
- review-specSkill
- review-tasksSkill
- session-reportSkill
- simple-planSkill
- specSkill
- task-complianceSkill
- test-flowsSkill
- test-planSkill
- verify-behaviorSkill
- wait-ciSkill
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.

