writing-skills
Skill4 starsChanged 3 months agoMITView on GitHub
Use when creating, editing, or improving a SKILL.md for AI agents. Triggers: "write a skill", "skill template", "skill structure", "skill description", "skill discovery", "SDO", "skill quality", or fixing a skill that agents ignore or mis-trigger.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- Floppa2003/skillstheir own version, first seen Nov 16, 2026
- dragoshont/architravetheir own version, first seen Nov 16, 2026
- rundesk-ai/skillstheir own version, first seen Nov 15, 2026
- draekien/skillstheir own version, first seen Nov 15, 2026
- mintunitish/tandemtheir own version, first seen Nov 15, 2026
Used with
Projects with it also use chinese-code-review, chinese-commit-conventions 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.
Leodorareluctant259Skillchinese-code-review
中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈
Also in 8 projects that use this
Leodorareluctant259Skillchinese-commit-conventions
中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化
Also in 8 projects that use this
obraSkilldiagnosing-superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Also in 20 projects that use this
kntismSkillcondition-based-waiting
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
Also in 3 projects that use this
aaddrickSkillwriting-agents
Use when creating new agents, editing existing agents, or defining specialized subagent roles for the Task tool
Also in 3 projects that use this
frankxaiSkilldefense-in-depth
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
Also in 3 projects that use this
- +3 more from Leodorareluctant259
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- obra/superpowers★ 314ksame name
- PostHog/posthog★ 41ksame name
- jnMetaCode/superpowers-zh★ 8.5ksame name
- openai/plugins★ 7.8ksame name
- farm-fe/farm★ 5.6ksame name
- compozy/compozy★ 2.9ksame name
- crbnos/carbon★ 2.8ksame name
- lingyired/status-trio★ 1.8ksame name
- GanyuanRan/Aegis★ 1.4ksame name
- pcvelz/superpowers★ 1.3ksame name
181 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstorm-featureSkill
- context-handoffSkill
- document-wikiSkill
- estimate-featureSkill
- implement-taskSkill
- lean-auditSkill
- plan-featureSkill
- read-codebase-contextSkill
- review-and-verifySkill
- setup-codebaseSkill
- setup-openezSkill
- systematic-debuggingSkill
- using-devkitSkill
The file
We split this skill into the rules it gives an agent
9 rules. 1 is common, 5 are distinctive, and 3 are very specific to this project.
1
Common
Most of the 181 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 75
Start with "Use when..."; put the triggering conditions first
- Distinctive: line 77
Add at most one purpose clause that names the outcome, never the steps
- Common: line 83
Use words an agent would search for:
- Distinctive: line 97
Before writing guidance, classify the baseline failure:
- Very specific: line 115
Control: Run the scenario three times without the new wording (baseline or current skill), each in a fresh session on a disposable …
- Very specific: line 119
Treatment: Run it three times with the new wording.
- Distinctive: line 121
Keep new wording only when the control fails at least one run and the treatment passes every run.
- Very specific: line 171
Don't explain what's obvious from the command (--help exists)
- Distinctive: line 175
Before deploying a skill:
“Common” is measured: kept by at least 6 in 10 of the 181 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
Writing Skills
A skill is a reusable playbook that teaches an agent how to execute a repeatable process. Skills are not narratives or one-off solutions. A skill succeeds only when the right agent picks it up for the right situation and follows it faithfully under pressure.
When to create a skill
Create when:
- The technique was not intuitively obvious
- It applies across projects, not just one repo
- Others (or future agent sessions) would benefit
Don't create for:
- One-off solutions
- Standard practices well-documented elsewhere
- Project-specific conventions (put in
AGENTS.md) - Mechanical constraints enforceable by tooling
SKILL.md structure
---
name: skill-name-with-hyphens
description: Use when [specific triggering conditions and symptoms]
---
# Skill Name
## Overview
Core principle in 1-2 sentences.
## When to use
Bullet list of symptoms and situations.
When NOT to use.
## Process / Pattern
Step-by-step instructions or before/after comparison.
## Quick reference
Table or bullets for scanning.
## Common mistakes
What goes wrong + fixes.
## Red flags (if discipline skill)
Table of rationalizations and reality. Keep this section last.Skill Discovery Optimization (SDO)
Description = trigger first, then at most one purpose clause
The description states when to use the skill, then at most one clause naming the outcome. Never list the skill's steps: agents follow the description instead of reading the full skill. This matches Anthropic's "Skill authoring best practices" (state what the skill does and when to use it; at most 1,024 characters).
# BAD: summarizes the workflow — agents follow this shortcut
description: Use when executing plans - dispatches subagent per task with review between tasks
# GOOD: trigger first, one purpose clause, no steps
description: Use when executing an implementation plan with independent tasks, to deliver each task reviewed and verifiedRules:
- Start with "Use when..."; put the triggering conditions first
- Include specific symptoms, situations, contexts
- Add at most one purpose clause that names the outcome, never the steps
- Third person
- 100–400 characters (never over 1,024)
Keyword coverage
Use words an agent would search for:
- Error messages: "Hook timed out", "ENOTEMPTY"
- Symptoms: "flaky", "hanging", "stale"
- Synonyms: "timeout/hang/freeze", "cleanup/teardown"
- Tool names: actual commands, library names
Descriptive naming
- Verb-first, active voice:
writing-skillsnotskill-creation - Gerunds work for processes:
creating-skills,debugging-with-logs - Name by what you DO or core insight:
root-cause-tracingnotdebugging-techniques
Match the form to the failure
Before writing guidance, classify the baseline failure:
| Baseline failure | Right form | Wrong form |
| Skips rule under pressure | Prohibition + rationalization table + red flags | Soft guidance ("prefer...") |
| Output has wrong shape | Positive recipe: state what output IS | Prohibition list ("don't X") |
| Omits required element | Structural: REQUIRED field in template | Prose reminders |
| Conditional behavior | Conditional on observable predicate | Unconditional rule + exemptions |
No nuance clauses. "Don't X unless it matters" reopens negotiation. Express a real exception as its own conditional on an observable predicate.
Test wording before keeping it
Judge every added or cut sentence by a measured run, not by how it reads.
- Scenario first. Name the scenario in
EVALS.mdthat exercises the wording and its written pass condition. Write one if none exists. - Control. Run the scenario three times without the new wording (baseline
or current skill), each in a fresh session on a disposable repository. Record
Control: x/3. Harness, grading, and flags are inEVALS.md, "Running a scenario". - Treatment. Run it three times with the new wording. Record
Runs: y/3. - Keep or cut.
- Keep new wording only when the control fails at least one run and the treatment passes every run. Wording that the control already passes in 3/3 adds context cost with no measured effect: do not add it.
- A cut is safe when every scenario that exercises it keeps a pass count not lower than the baseline's. Otherwise restore the wording.
- Record the host and version, run counts, and input and output tokens
when the host reports them. An unavailable host is
cannot verify, never a manual pass.
Bulletproofing discipline skills
Skills that enforce discipline need to resist rationalization. Agents find loopholes under pressure.
- Close every loophole explicitly — don't just state the rule, forbid specific workarounds.
- Address spirit vs letter — add: "Violating the letter of the rules is violating the spirit of the rules."
- Build rationalization table — every excuse agents make goes in:
| Excuse | Reality | - Create red flags list — self-check signals: "If you catch yourself thinking X, stop."
Anti-patterns
| Anti-pattern | Why bad |
| Narrative ("In session 2025-10-03, we found...") | Too specific, not reusable |
| Multi-language dilution (example.js + .py + .go) | Mediocre quality, maintenance burden |
| Code in flowcharts | Can't copy-paste, hard to read |
| Generic labels (helper1, step3) | No semantic meaning |
| Summarizing workflow in description | Agents follow shortcut, skip full skill |
Token efficiency
Skills load into agent context. Every token counts. Limits follow Anthropic's "Skill authoring best practices" (body under 500 lines; description at most 1,024 characters; references one level deep):
| Item | Limit |
SKILL.md lines | at most 500 (tested) |
SKILL.md characters | the skill's cap in tests/plugin-smoke.mjs (tested); a skill missing from its table fails |
description | starts "Use when"; trigger first, at most one purpose clause, no steps; 100–400 characters (tested) |
| Reference files | linked from SKILL.md as "Read references/x.md when <condition>"; a table of contents when over 100 lines; one level deep |
- Each shared rule has one owner; every other skill points to it in one line
- Move conditional procedures to
references/; keep prohibitions, red flags, approval gates, and stop conditions inline - Compress examples to minimal viable illustration
- Don't explain what's obvious from the command (
--helpexists)
Quality checklist
Before deploying a skill:
- Name uses only letters, numbers, hyphens
- Description starts with "Use when...", puts triggers first, has at most one purpose clause, no steps, 100–400 characters
- Keywords throughout for search (errors, symptoms, tools)
- Clear overview with core principle
- One excellent example (not multi-language)
- Quick reference table for scanning
- Common mistakes section
- Red flags table (if discipline skill)
- No narrative storytelling
- Supporting files only for heavy reference or reusable tools
- At most 500 lines and within its character cap; conditional procedures moved to
references/
Common mistakes
| Mistake | Fix |
| No keywords an agent would search | Add error strings, symptoms, synonyms, and tool names throughout. |
| Prohibition list for a shape problem | State what the output IS (positive recipe), not just what to avoid. |
Red flags
| Thought | Reality |
| "The description should explain what the skill does" | State the triggers first and at most one purpose clause naming the outcome. Listing the steps makes agents follow the shortcut and skip the skill body. |
| "A longer skill is more helpful" | Skills load into context. Bloat pushes out the user's code. Trim to the minimum that survives pressure. |
"I'll add a unless it makes sense exemption" | Nuance clauses reopen negotiation under pressure. Express the real exception as a conditional on an observable predicate. |
| "One example per language is clearer" | Multi-language dilution lowers every example's quality. Pick one excellent example. |
| "This is obvious, agents will just know" | If it were obvious, the skill wouldn't exist. Make the rule explicit and forbid the workaround. |
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.

