skills
CLAUDE.md1 starsChanged 2 months agoMITView on GitHub
This repository contains Claude Code plugin skills. Before finishing, verify:
In this repository15 other files it gives its agents.
- codebase-inventorySkill
- code-commentsSkill
- codex-goal-writerSkill
- generate-specSkill
- git-commitSkill
- glab-mr-reviewSkill
- glab-mrSkill
- handoff-auditSkill
- jira-apiSkill
- linear-task-lifecycleSkill
- reject-and-redoSkill
- setup-serenaSkill
- setup-skill-syncSkill
- subagent-goSkill
- wtSkill
The file
We split this CLAUDE.md into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Every skill must have a SKILL.md.
- Very specific: line 27
Every SKILL.md must start with YAML frontmatter.
- Distinctive: line 32
Keep skill-level README.md human-facing.
- Distinctive: line 33
Keep localized README files separate from the default English README.
- Very specific: line 34
Use relative links from SKILL.md.
- Very specific: line 41
Every skill has a SKILL.md.
- Very specific: line 42
Every SKILL.md has valid frontmatter.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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
CLAUDE.md
Repository Purpose
This repository contains Claude Code plugin skills.
Structure Rules
- Plugin metadata lives in
.claude-plugin/plugin.json. - Codex plugin metadata lives in
.codex-plugin/plugin.json. .claude-plugin/should only containplugin.json..codex-plugin/should only containplugin.json.- Skills live in
skills/<skill-name>/SKILL.md. - Optional human-facing skill usage docs may live in
skills/<skill-name>/README.md. - English is the default skill README language. Localized skill docs may use
README.<locale>.md, for exampleREADME.zh-TW.md. - Skill UI metadata may live in
skills/<skill-name>/agents/openai.yaml. - Skill names use kebab-case.
- Shared references live in
references/. - Skill-specific references live in
skills/<skill-name>/references/. - Shared scripts live in
scripts/. - Skill-specific scripts live in
skills/<skill-name>/scripts/. - Templates live in
skills/<skill-name>/templates/when they are skill-specific.
Skill Authoring Rules
- Every skill must have a
SKILL.md. - Every
SKILL.mdmust start with YAML frontmatter. - Frontmatter must include
nameanddescription. descriptionmust describe when to use the skill.- Keep
SKILL.mdconcise. - Move long examples, templates, and detailed references into separate files.
- Keep skill-level
README.mdhuman-facing; do not rely on it for agent trigger behavior. - Keep localized README files separate from the default English README.
- Use relative links from
SKILL.md.
Review Checklist
Before finishing, verify:
- Directory structure is valid.
- Every skill has a
SKILL.md. - Every
SKILL.mdhas valid frontmatter. - Skill names match their folder names.
- References are placed at the correct level.
- Scripts are documented.
- README lists all skills.
- Plugin metadata directories contain only
plugin.json.
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.

