skill-creator
Skill7 starsChanged 5 months agoMITView on GitHub
Design a new Claude Code skill from a concrete use case and produce a repo-ready skill package. Use when the user asks to create a new skill, define a skill's responsibility, draft SKILL.md, choose frontmatter, design supporting files, or prepare eval criteria for a new skill. Also trigger on "スキルを作りたい", "スキルを作って", "スキルを追加して", "新しいスキル", "SKILL.md生成".
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 repository140 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- static/llms.txtllms.txt
- ask-codexSkill
- river-review-disciplineSkill
- skill-ops-plannerSkill
- skill-optimizerSkill
- commandsSkill
- adversarial-reviewSkill
- review-teamSkill
- river-review-architectureSkill
- river-review-codeSkill
- river-review-docsSkill
- river-review-frontendSkill
- river-review-performanceSkill
- river-review-security-auditSkill
- river-review-securitySkill
- river-reviewSkill
- river-review-testingSkill
- unknown-coverage-reviewSkill
- Coverage and Failure Path GapsSkill
- Flaky Test Risk CheckSkill
- GitHub Actions Workflow Security ReviewSkill
- Standard Review Policy for DownstreamSkill
- Test Assertion Effectiveness 常に PASS するテストの検出Skill
- Test Presence for Changed CodeSkill
- Test Naming and StructureSkill
- テスト観点レビュー(差分ドリブン)Skill
- a11y Accessible Name BasicsSkill
- Agent Skill Bridge ReviewSkill
- Altitude Generalization GuardSkill
- API Compatibility and Test Gap ReviewSkill
- Assumption Resolution Trace Plan の前提解消トレーサビリティSkill
- Async Correctness 非同期処理の正しさ検証Skill
- Behavior-Structure Separation 振る舞い変更と構造変更の分離・外部挙動維持Skill
- Closure Scope Retention GuardSkill
- Component Variants / States Documentation コンポーネント状態の文書化Skill
- Configuration File ReviewSkill
- Cross-File Leakage リファクタ後の caller 側残骸検出Skill
- Design Source-of-Truth Conformance デザイン定義準拠Skill
- Design System Component Reuse GuardSkill
- Design Token EnforcementSkill
- Detector Detection Power 検査器の検出力の検証Skill
- Documentation Hygiene ドキュメント衛生Skill
- End-to-End Wiring 末端到達・貫通の検証Skill
- Existing-Pattern Conformance 既存パターン準拠の確認Skill
- Firebase Security Rules ReviewSkill
- Fix Scope Integrity 指摘対応ループのスコープ逸脱・前提破壊検出Skill
- GitHubレビューコメント対応(修正案つき)Skill
- Hallucinated Reference 幻覚的参照の実在確認Skill
- Hello Skill (Always-On Sample)Skill
- i18n Unused Key ReviewSkill
- Impact Evidence Coverage 影響・失敗系・外部依存の証拠充足Skill
- Independent Review SynthesisSkill
- Invisible Unicode Injection Scan 不可視 Unicode コード注入検出Skill
- Knowledge-to-Code Alignment 新知識のコード反映・設計知識の保全Skill
- Laravel Eloquent N+1 and Query Efficiency ReviewSkill
- Laravel Mass Assignment and Authorization ReviewSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 0 are common, 17 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 185 edited versions we read keep these.
17
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Create a new skill only after the use case is concrete enough.
- Very specific: line 29
Write output files only to .claude/skills/ unless the user explicitly specifies a different path.
- Distinctive: line 30
Do not modify existing skills without user confirmation.
- Distinctive: line 36
Do not create a broad or fuzzy skill.
- Distinctive: line 44
If the requested scope is too broad, split it into multiple skills.
- Distinctive: line 59
If any item is unclear:
- Distinctive: line 61
ask the minimum focused questions, or
- Distinctive: line 64
Do not draft the full skill until the gate passes.
- Distinctive: line 82
add secondary patterns only when one pattern is insufficient
- Distinctive: line 85
Do not continue until the pattern choice is explicit.
- Very specific: line 131
Keep the main file compact.
- Very specific: line 135
Use ${CLAUDE_SKILL_ROOT}/assets/basic-skill-template.md as the starting skeleton.
- Distinctive: line 141
Create an initial eval plan with:
- Very specific: line 155
Use ${CLAUDE_SKILL_ROOT}/assets/eval-rubric-template.md as the rubric structure.
- Distinctive: line 159
Check the draft against:
- Distinctive: line 168
After the skill files are written:
- Very specific: line 170
verify the directory name matches the name field in frontmatter
- Very specific: line 171
verify description is under 1024 characters and includes trigger keywords
- Very specific: line 174
verify all ${CLAUDE_SKILL_ROOT}/ references point to existing files
- Distinctive: line 175
check the repository CLAUDE.md or AGENTS.md for additional registration steps
- Distinctive: line 176
if the repository uses a skills index or registry, update it
- Distinctive: line 200
create a "do everything" skill
- Distinctive: line 202
write a vague description
- Distinctive: line 211
If the request is too broad:
“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
Pattern declaration
Primary pattern: Pipeline Secondary patterns: Inversion Why: skill creation requires strict phase order (requirements → pattern selection → structure → review) with an upfront question-gathering gate.
Purpose
Create a new skill only after the use case is concrete enough.
Your job is to:
- identify the smallest useful responsibility
- select the right design pattern
- define when the skill should trigger
- choose safe frontmatter defaults
- draft a minimal but strong
SKILL.md - propose supporting files only when they add clear value
- define an initial eval set
Safety constraints
Write output files only to .claude/skills/ unless the user explicitly specifies a different path.
Do not modify existing skills without user confirmation.
Note: this skill does not set disable-model-invocation: true because file creation is its primary purpose, not an incidental side effect. The settings.json deny list and user confirmation prompts provide sufficient guardrails.
Core rule
Do not create a broad or fuzzy skill.
Prefer:
- one responsibility
- one primary workflow
- one clear success condition
If the requested scope is too broad, split it into multiple skills.
Phase 0: Gate
Before drafting, confirm:
- target outcome
- primary user intent
- trigger phrases
- audience
- allowed tools needed
- whether the skill should be auto-invoked or manual-only
- source material available
- definition of done
If any item is unclear:
- ask the minimum focused questions, or
- inspect available files first if the answer can be found without asking
Do not draft the full skill until the gate passes.
Phase 0.5: Pattern selection
Choose the primary design pattern before drafting the skill.
Available patterns:
- Tool Wrapper — the skill mainly injects domain, library, or framework knowledge on demand
- Generator — the skill mainly produces structured output from a reusable template
- Reviewer — the skill mainly evaluates output against a checklist or rubric
- Inversion — the skill must gather missing information before acting
- Pipeline — the skill must enforce a strict multi-step workflow with checkpoints
Selection rules:
- identify the primary value source or failure mode the skill addresses
- map it to one primary pattern
- add secondary patterns only when one pattern is insufficient
- each secondary pattern must appear in a named phase with a measurable role
Do not continue until the pattern choice is explicit.
Phase 1: Skill boundary design
Produce a short working summary with:
- skill name candidate
- single responsibility
- in-scope tasks
- out-of-scope tasks
- likely trigger language
- risk level
Reject designs that combine unrelated workflows.
Phase 2: Frontmatter design
Choose frontmatter intentionally.
Defaults:
- include
name - include
description - omit extra fields unless clearly needed
Use:
disable-model-invocation: truefor side-effecting, sensitive, or timing-dependent workflowsallowed-toolsonly when safe pre-approval is clearly usefulmodelonly when there is a concrete reason to override the default
For every chosen field, state why it is needed.
Phase 3: Structure design
Draft the skill with this order:
- pattern declaration
- purpose
- gate
- workflow phases
- output contract
- review step
- failure handling
- additional resources
Keep the main file compact.
Move heavy references, examples, and templates into separate files.
For River Review Agent Skills, keep activation, responsibility, routing, hard guards, and the output contract in SKILL.md; move optional examples, troubleshooting, rationale, and provider-specific detail to references/. Treat the repository's 12 KiB / 250-line context-health threshold as an advisory review signal, never as a reason to remove safety or verification.
Use ${CLAUDE_SKILL_ROOT}/assets/basic-skill-template.md as the starting skeleton.
The generated SKILL.md must include a Pattern declaration section at the top with primary pattern, secondary patterns, and Why fields matching the choice from Phase 0.5.
Phase 4: Eval design
Create an initial eval plan with:
- 10 to 20 realistic test prompts
- 3 to 6 pass/fail criteria
- likely failure modes
- what should be checked by code vs by reviewer
Include at least:
- one trigger test
- one under-specified request
- one boundary case
- one anti-pattern case
Use ${CLAUDE_SKILL_ROOT}/assets/eval-rubric-template.md as the rubric structure.
Phase 5: Review
Check the draft against:
${CLAUDE_SKILL_ROOT}/references/review-default.md${CLAUDE_SKILL_ROOT}/references/design-principles.md
Fix any issue before finalizing.
Phase 6: Registration
After the skill files are written:
- verify the directory name matches the
namefield in frontmatter - verify
descriptionis under 1024 characters and includes trigger keywords - measure the
SKILL.mdentrypoint size and review whether optional knowledge should move to supporting files - for River Review Agent Skills, run
npm run agent-skills:validateand inspect any context-health advisory; exceeding 12 KiB / 250 lines is warning-only and requires judgment, not blind trimming - verify all
${CLAUDE_SKILL_ROOT}/references point to existing files - check the repository CLAUDE.md or AGENTS.md for additional registration steps
- if the repository uses a skills index or registry, update it
Output format
Return exactly these sections:
Skill summary
Pattern selection
Recommended directory structure
SKILL.md draft
Supporting files to add
Eval plan
Known risks
Anti-patterns
Do not:
- create a "do everything" skill
- invent company-specific rules
- write a vague description
- skip the gate
- skip pattern selection
- omit eval planning
- hide trade-offs
- stack multiple patterns without justifying each one
Failure handling
If the request is too broad:
- propose 2 to 4 smaller skills
- explain the split by responsibility
- recommend which one to build first
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.

