skill-creator
Skill44 starsChanged 6 months agoMITView on GitHub
Guide for creating or updating a ReviewFlow skill. Use when the user wants to create a new skill, update an existing skill, or asks how to add a slash command that extends Claude's capabilities in this project.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- maotoumao/Cebiantheir own version, first seen Nov 9, 2026
- SebastienDegodez/copilot-instructionstheir own version, first seen Nov 8, 2026
- idavidov13/agentic-playwrighttheir own version, first seen Nov 8, 2026
- HughYau/AcademicForgetheir own version, first seen Nov 8, 2026
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
Used with
Projects with it also use taskflow-inbox-triage, mermaid-diagram-generator and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
shalombSkillmermaid-diagram-generator
Guide on creating and editing Mermaid charts safely. Use when asked to draw a diagram, flowchart, or architecture chart. Triggers on: 'mermaid', 'diagram', 'flowchart', 'visualize'.
Also in 5 projects that use this
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
Liang-MHSkillstock_analysis
获取 A 股、基金和港股的实时行情和技术分析数据
Also in 5 projects that use this
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
- +6 more from naman10parikh
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- openclaw/openclaw★ 395ksame name
- moltbot/clawdbot★ 394ksame name
- steipete/warelay★ 394ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- molt-bot/clawdbot★ 391ksame name
- anthropics/skills★ 195ksame name
- openai/codex★ 135ksame name
- google-gemini/gemini-cli★ 109ksame name
179 more not listed
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 repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-creatorSkill
- anti-overengineeringSkill
- audit-docsSkill
- auto-reviewSkill
- architectureSkill
- clean-codeSkill
- commitSkill
- create-docSkill
- dddSkill
- discoverySkill
- docs-indexSkill
- e2eSkill
- event-stormingSkill
- implement-featureSkill
- product-managerSkill
- refactor-featureSkill
- refactoring-mikado-stranglerSkill
- review-backSkill
- review-docSkill
- review-followupSkill
- review-frontSkill
- review-fullstackSkill
- securitySkill
- shipSkill
- solidSkill
- dashboard-stylingSkill
- tddSkill
- update-docsSkill
- worktreeSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 185 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Write the body — imperative instructions, low prose
- Very specific: line 48
Test it: invoke /skill-name and verify Claude follows the workflow
- Distinctive: line 70
Write in English — no exceptions (code, body, comments)
- Distinctive: line 71
Use imperative form: "Run", "Read", "Stop", never "You should run"
- Distinctive: line 73
Keep the body under 400 lines
- Distinctive: line 75
Prefer tables and bullet lists over prose paragraphs
- Distinctive: line 99
After creating a skill, add it to the skills table in CLAUDE.md:
“Common” is measured: kept by at least 6 in 10 of the 185 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Creator
Guide for creating effective skills in the ReviewFlow project.
About Skills
Skills are modular, self-contained packages that extend Claude's capabilities with specialized workflows, domain knowledge, and tool integrations. They transform Claude from a general-purpose agent into a project-specialized one.
What Skills Provide
- Specialized workflows — Multi-step procedures (e.g.
/ship,/tdd,/implement-feature) - Domain expertise — ReviewFlow-specific knowledge, architecture patterns, business rules
- Bundled resources — References and assets loaded on demand
Core Principles
Concise is Key
The context window is a shared resource. Only add context Claude does not already have. Challenge each paragraph: "Does Claude really need this?" If not, remove it.
Set Appropriate Degrees of Freedom
- High freedom (text instructions): multiple approaches valid, context-dependent
- Medium freedom (pseudocode/templates): preferred pattern exists, variation acceptable
- Low freedom (shell scripts): operations are fragile, consistency critical
Anatomy of a ReviewFlow Skill
.claude/skills/<skill-name>/
├── SKILL.md (required)
│ ├── YAML frontmatter (required: name + description)
│ └── Markdown instructions
└── references/ (optional — bundled docs loaded by reference)Skill Creation Process
- Understand the skill with 2-3 concrete usage examples
- Draft the frontmatter (
name,description,user-invocable) - Write the body — imperative instructions, low prose
- Test it: invoke
/skill-nameand verify Claude follows the workflow - Register in
CLAUDE.mdskills table
Frontmatter Reference
---
name: skill-name # kebab-case, matches folder name
description: > # PRIMARY TRIGGER — LLM reads only this initially.
One or two sentences. # Include natural-language trigger phrases.
"Use when the user says X, Y, Z."
user-invocable: true # true = can be invoked with /skill-name
allowed-tools: Bash, Read # optional — restrict available tools
---Official fields: name, description, user-invocable, allowed-tools, disable-model-invocation, context.
triggers: []is NOT an official field — it is silently ignored. Thedescriptionis the only trigger mechanism.
Writing Guidelines
- Write in English — no exceptions (code, body, comments)
- Use imperative form: "Run", "Read", "Stop", never "You should run"
descriptionis the primary trigger — include natural trigger phrases in it- Keep the body under 400 lines
- Include only what Claude does not already know
- Prefer tables and bullet lists over prose paragraphs
- Match ReviewFlow conventions (see
CLAUDE.mdand.claude/rules/coding-standards.md)
What NOT to Include
- Generic programming knowledge Claude already has
- README-style context that belongs in docs
- Comments explaining what the skill is (the frontmatter does that)
- Skills are for AI agents, not humans — do not write tutorials
ReviewFlow-Specific Conventions
| Convention | Detail |
| Package manager | yarn — never pnpm or npm |
| Main branch | master — never main |
| Quality gate | yarn verify (typecheck + lint + test:ci) |
| Commit format | Conventional Commits via commitlint |
| Language | English everywhere (code, tests, commits, logs) |
| Imports | @/ alias + .js extension mandatory |
| No barrel exports | Direct imports only, no index.ts re-exports |
Skill Registration
After creating a skill, add it to the skills table in CLAUDE.md:
| `/skill-name` | When to use this skill |Quick Template
---
name: my-skill
description: Brief description. Use when the user says "X", "Y", or wants to Z.
user-invocable: true
---
# My Skill — Short Title
## Activation
This skill activates with `/my-skill`.
## Workflow
### Step 1: <Action>
<Instructions>
### Step 2: <Action>
<Instructions>
## Rules
- NEVER do X
- ALWAYS do YDoes 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.

