write-skill
Skill7 starsChanged 6 months agoMITView on GitHub
Meta-skill that creates new Claude Code skills. Describe what you want the skill to do and this generates a complete SKILL.md with proper frontmatter, shell injection, structured instructions, and output format.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- serionist/claude-session-restoretheir own version, first seen Nov 8, 2026
- protokol11/skillstheir own version, first seen Nov 8, 2026
- AlomoesDataScience/claude-skillstheir own version, first seen Nov 8, 2026
- maideps/ai-harness-frameworktheir own version, first seen Nov 8, 2026
- devjiwonchoi/skillstheir own version, first seen Nov 8, 2026
- LindseyB/skillstheir own version, first seen Nov 4, 2026
Used with
Projects with it also use grill, write-docs and 6 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.
renatorozasSkillgrill
Adversarial code review. Don't let me ship until the changes pass your scrutiny.
Also in 5 projects that use this
SentrySkillwrite-docs
Create or update documentation pages for the Abacus docs site. Use when adding new documentation, updating existing pages, or ensuring docs stay in sync with code changes. Ensures pages follow Starlight patterns and build correctly.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 4 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 4 projects that use this
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 3 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- garrytan/gstack★ 141ksame name
- primer/react★ 3.9ksame name
- iliaal/whetstone★ 36same name
- evist0/okf-matt-skills★ 13same name
- day-ai/gtm-brain★ 9same name
- agentpatterns-ai/skills★ 7same name
- hassan-mohiddin/freeflow★ 5same name
- umararshad4/honey-stack★ 5same name
- dzianisv/skills★ 4same name
- ssakhavi/writing-good-skills-course★ 3same name
15 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 repository45 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- api-designSkill
- architecture-reviewSkill
- business-blueprintSkill
- business-logic-auditSkill
- changelogSkill
- ci-pipelineSkill
- code-coverageSkill
- competitive-analysisSkill
- convert-codeSkill
- create-componentSkill
- db-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- design-flowSkill
- docker-setupSkill
- env-setupSkill
- error-monitorSkill
- estimateSkill
- explain-codeSkill
- fix-issueSkill
- generate-docsSkill
- git-cleanupSkill
- grill-meSkill
- handoffSkill
- legal-pagesSkill
- memory-importSkill
- memorySkill
- microcopySkill
- migrate-frameworkSkill
- onboardSkill
- optimizeSkill
- pr-summarySkill
- refactorSkill
- reference-appSkill
- review-prSkill
- security-scanSkill
- seo-scaffoldSkill
- tddSkill
- web-launch-checkSkill
- wireframeSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
4
Distinctive
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
- Distinctive: line 22
Trigger: When should someone use it?
- Distinctive: line 29
Create the file following this template:
- Very specific: line 66
Check the generated SKILL.md against these requirements:
- Distinctive: line 95
Follow existing skill patterns in this project
- Very specific: line 96
Keep SKILL.md under 200 lines
- Distinctive: line 97
Use shell injection for context detection, not hardcoded assumptions
“Common” is measured: kept by at least 6 in 10 of the 23 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
Existing Skills (for pattern reference)
!ls .claude/skills/ 2>/dev/null
Process
Step 1: Gather Requirements
From the user's description, determine:
- Name: lowercase-with-hyphens, becomes the
/slash-command - Purpose: What does this skill do?
- Trigger: When should someone use it?
- Input: What arguments does it need?
- Output: What should it produce?
- Tools needed: Which Claude Code tools does it require?
Step 2: Generate SKILL.md
Create the file following this template:
---
name: skill-name
description: "One sentence: what it does + when to use it. Be specific enough for auto-invocation."
argument-hint: "[argument description]"
allowed-tools: Read, Grep, Glob
---
# Skill Title
## Context Detection
!`relevant shell command for auto-detecting project context`
---
## Instructions
### Step 1: [First action]
Detailed instructions for what Claude should do.
### Step 2: [Second action]
...
### Step N: [Final action]
...
## Output Format
Describe the expected structure of the output.
## Rules
- Rule 1
- Rule 2Step 3: Validate the Skill
Check the generated SKILL.md against these requirements:
- Frontmatter has
nameanddescription(required) - Description is under 150 characters and specific
allowed-toolslists only what's needed (principle of least privilege)- Shell injection uses
!command`` syntax correctly - Instructions are numbered steps, not vague paragraphs
- Output format is defined
- Rules section exists with boundaries
Step 4: Save and Test
- Create directory:
.claude/skills/<skill-name>/ - Save
SKILL.mdto that directory - Instruct user to test: open Claude Code, type
/<skill-name>
Frontmatter Reference
| Field | Required | Description |
name | Yes | Slash command name (lowercase, hyphens) |
description | Yes | When to use (specific, <150 chars) |
argument-hint | No | Autocomplete hint, e.g. [filename] |
allowed-tools | No | Tools allowed without asking |
disable-model-invocation | No | true = manual only |
user-invocable | No | false = hidden from menu |
model | No | Override model |
effort | No | low, medium, high, max |
context | No | fork for subagent isolation |
Rules
- Follow existing skill patterns in this project
- Keep SKILL.md under 200 lines
- Use shell injection for context detection, not hardcoded assumptions
- Description must be specific enough for Claude to auto-invoke correctly
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.

