skill-creator
Skill0 starsChanged 4 months agoMITView on GitHub
Use this when creating or revising an agent skill with focused project knowledge or a repeatable workflow.
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, community-led-growth 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
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
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
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
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
- +5 more from naman10parikh
- +1 more from nicepkg
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- molt-bot/clawdbot★ 395ksame name
- steipete/warelay★ 395ksame name
- moltbot/clawdbot★ 395ksame name
- openclaw/openclaw★ 395ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- project-kickoffSkill
- repo-layoutSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 185 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create small, durable instruction packages that help an agent do a recurring kind of work correctly.
- Distinctive: line 14
Create a skill only when the guidance is reusable and specific enough to avoid repeating it in tasks or AGENTS.md.
- Distinctive: line 18
Do not create a skill for one-off task details, generic advice, or instructions that apply to the entire repository.
- Very specific: line 32
Use a short, lowercase, hyphenated directory and name.
- Very specific: line 33
Start description with exactly Use this when and state the situation that should trigger the skill.
- Distinctive: line 44
Keep a skill self-contained when practical.
- Very specific: line 57
Keep SKILL.md under 200 lines.
“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
Create small, durable instruction packages that help an agent do a recurring
kind of work correctly. A skill belongs in .agents/skills/<skill-name>/ and
its instructions belong in SKILL.md.
Start with a narrow purpose
Create a skill only when the guidance is reusable and specific enough to avoid
repeating it in tasks or AGENTS.md. Good candidates include a domain concept,
a repository subsystem, a release procedure, or a reliable debugging workflow.
Do not create a skill for one-off task details, generic advice, or instructions
that apply to the entire repository. Keep shared rules in AGENTS.md instead.
Required shape
Begin every skill with YAML frontmatter:
---
name: lowercase-hyphenated-name
description: "Use this when …"
---- Use a short, lowercase, hyphenated directory and
name. - Start
descriptionwith exactlyUse this whenand state the situation that should trigger the skill. - Make the description concrete enough for an agent to select the skill without opening every skill file.
Write useful instructions
Lead with the outcome, then give only the context and workflow needed to reach it. Prefer clear steps, commands, file locations, decision rules, and examples over background prose. Explain important constraints and verification steps.
Keep a skill self-contained when practical. Link to project files or nearby references for detailed material rather than copying large documents. Avoid tool- or agent-specific phrasing unless the workflow truly requires it.
Review before finishing
- Does the frontmatter parse as YAML and have both
nameanddescription? - Does the description start with
Use this when? - Is the trigger narrow, clear, and reusable?
- Does the body contain owned knowledge or a repeatable workflow?
- Is any guidance duplicated from
AGENTS.mdor another skill? - Can the skill be shortened without losing a decision, constraint, or action?
Keep SKILL.md under 200 lines. Split a genuinely large topic into focused
skills or place supporting detail in adjacent reference files (/ref/example.md).
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.

