writing-great-skills
Skill25 starsChanged 3 months agoMITView on GitHub
Write, revise or review an agent skill (SKILL.md package).
Files
Writing Great Skills
- Scope = user request + settled constraints + existing authorization; skill adds no authority.
- Agent prose = minimum tokens + unambiguous meaning. Use
=,→,+, terse bullets/tables where clear; delete filler + repetition. Preserve conditions, actions, exceptions and proof; cryptic abbreviations ≠ useful compression.
Routes
Load matching routes only; Core always applies.
flowchart LR
C[Core] -->|Package / metadata / invocation| P[references/package.md]
C -->|Observed skill failure| R[references/repair.md]
click P "references/package.md"
click R "references/repair.md"Core
| Check | Required outcome |
| Need | Removal loses reusable, non-default behavior; omit generic agent advice. |
| Trigger | Purpose + distinct use; relevant prompts match, unrelated prompts do not. Preserve implicit selection unless user requests explicit-only. |
| Disclosure | SKILL.md = routes + essential shared rules. Conditional workflows/examples/detail → references. Each route = load condition + direct link; load only applicable routes. Keep short universal rules inline. |
| Diagram | Flow, decision, state or dependency → Mermaid by default. Terse labels; one representation, no prose duplicate. Non-relational rule → bullet/table. |
| Split | Same actions + proof → keep together. Split for independent use or observed failure unresolved by clearer completion. |
| Resource | Script = repeated fragile logic; reference = conditional knowledge; asset = copied output. Each needs a current consumer; no mandatory file count. |
| Ownership | Rule + definition + caveat = one owner. Inspect package + relevant siblings/project instructions; consolidate duplicates + remove stale rules. |
| Steering | State target action + observable completion; likely mistake → replacement action. |
| Reader | After new or rewritten prose, a subagent that did not write it compares the old and new text. It quotes each sentence it had to reread and each sentence whose meaning changed. Fix each quoted sentence by rewording it or moving it to a reference. Do not cut more words: here clarity beats minimum tokens. The subagent reads each changed sentence with its paragraph or table row, and reads each restructured file in full. |
| Validation | Available native validator + changed links/tools/skills exist + metadata agrees. Substantial/risky change → representative trigger/non-trigger prompts + actual outcome proof. Run changed scripts; wording tests ≠ behavior proof. |
Other versions99 projects use a version of this.
Word for word · 1
- sgaabdu4/appwrite-backend★ 2100% same
Edited · 0
None found.
Wrote their own version · 98
- GreyDGL/PentestGPT★ 16ksame name
- Akylas/OSS-DocumentScanner★ 2.6ksame name
- Aniket-508/termcn★ 1.2ksame name
- stevesolun/ctx★ 583same name
- aws/graph-explorer★ 489same name
- Akylas/oss-weather★ 472same name
- sveltejs/ai-tools★ 337same name
- sveltejs/mcp★ 336same name
- ninehills/skills★ 280same name
- loulanyue/skills★ 231same name
88 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.
Used alongsideProjects with it also use decision-mapping, batch-grill-me 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.
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 7 projects that use this
boyingliu01Skillbatch-grill-me
A relentless interview that asks every frontier question at once, round by round. Thin alias of `grilling` (#540) — upstream mattpocock/skills absorbed this protocol into grilling; XP-Gate keeps this name as the sprint-flow Phase 2 entry point so orchestration docs stay stable.
Also in 7 projects that use this
simo97Skilledit-article
The user will invoke this skill to help them edit an article.
Also in 18 projects that use this
simo97Skillrequest-refactor-plan
Use this skill when user wants to create a refactor plan.
Also in 17 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 19 projects that use this
LesaniSkillwriting-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
Also in 20 projects that use this
- +3 more from simo97
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- building-flutter-appsSkill
- codebase-designSkill
- code-reviewSkill
- e2eSkill
- he-buildSkill
- he-learnSkill
- he-planSkill
- he-shipSkill
- heSkill
- marketing-videoSkill
- product-walkthrough-videoSkill
- researchSkill
- security-reviewSkill
- building-flutter-appsSkill
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.

