writing-skills
Skill0 starsChanged 21 days agoLicence not identifiedView on GitHub
Use when creating new skills, editing existing skills, or verifying skills work before deployment
195 other projects use a version of this, 126 of them edited; 123 of 127 edited versions we compared changed its rules; 12 new projects in the last 4 weeks, against 11 the 4 before.
How people change it
123 of 127 edited versions changed its rules, and some changes recur.
Of the 127 edited versions we compared: 4 keep every rule, 123 made changes of their own.
Rules people drop
- When you write or change a skill's frontmatter, name or description, or need to cut its size, read [references/discovery.md](references/discovery.md): the SKILL.md template, description and keyword guidance, naming, token budgets, and cross-referencing other …dropped by 122 of 123
- When you add or change a flowchart in a skill, read [references/flowcharts.md](references/flowcharts.md) first: when a flowchart earns its place, the graphviz conventions, and how to render one.dropped by 122 of 123
- When the baseline failure is a discipline failure, read [references/bulletproofing.md](references/bulletproofing.md) before you write the guidance: closing loopholes, the spirit-vs-letter line, the rationalization table, and the red-flags list.dropped by 122 of 123
- Before writing guidance, classify the baseline failure. The form that bulletproofs one failure type measurably backfires on another.dropped by 89 of 123
- Always include a no-guidance control. If the control doesn't exhibit the failure, there is nothing to fix — stop, don't author the guidance.dropped by 89 of 123
- Variance is a metric. When guidance lands, reps converge on the same shape. Five different interpretations across five reps means the wording isn't binding — tighten the form before adding words.dropped by 89 of 123
- When: Tool is reusable code, not just narrativedropped by 11 of 123
- When: Reference material too large for inlinedropped by 11 of 123
Rules people add
- A rule we can't quote: its licence doesn't allow itadded by 114 of 123
- A rule we can't quote: its licence doesn't allow itadded by 113 of 123
- A rule we can't quote: its licence doesn't allow itadded by 113 of 123
- A rule we can't quote: its licence doesn't allow itadded by 113 of 123
- A rule we can't quote: its licence doesn't allow itadded by 113 of 123
- A rule we can't quote: its licence doesn't allow itadded by 113 of 123
- A rule we can't quote: its licence doesn't allow itadded by 112 of 123
- A rule we can't quote: its licence doesn't allow itadded by 112 of 123
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Steady: 12 new projects took it in the last 4 weeks, 1.1× the 4 weeks before.
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- Floppa2003/skillsedited, first seen Nov 16, 2026
- dragoshont/architraveword for word, 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/tandemedited, 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 versions195 projects use a version of this.
Word for word · 13
- obra/superpowers★ 314k100% same
- lingyired/status-trio★ 1.8k100% same
- The-AIOS/aios★ 113100% same
- codeAnqiang-ma/dsh-superpowers★ 12100% same
- ddtcorex/maestro-skills★ 5100% same
- bepaldes/heimdall-agent★ 2100% same
- dragoshont/architrave★ 2100% same
- DJtx001/ai-coding-playbook★ 1100% same
- Just-Silver/just-silver-skills★ 1100% same
- supermorkat/qawa-arena★ 1100% same
3 more not listed
Edited · 126
- openai/plugins★ 7.8k49% same
- farm-fe/farm★ 5.6k45% same
- pcvelz/superpowers★ 1.3k98% same
- DemonDamon/AgenticX★ 1k45% same
- mdiri-ai/SoduWork★ 93048% same
- coco-research/coco★ 79743% same
- Innei/ryugi★ 50253% same
- Trevoke/org-gtd.el★ 48545% same
- koaning/wigglystuff★ 45547% same
- derHaken/SuperAntigravity★ 43945% same
116 more not listed
Wrote their own version · 56
- PostHog/posthog★ 41ksame name
- jnMetaCode/superpowers-zh★ 8.5ksame name
- compozy/compozy★ 2.9ksame name
- crbnos/carbon★ 2.8ksame name
- GanyuanRan/Aegis★ 1.4ksame name
- software-mansion/react-native-audio-api★ 862same name
- PostHog/posthog-foss★ 731same name
- pedronauck/skills★ 655same name
- speakeasy-api/gram★ 278same name
- NoobyGains/godmode★ 120same name
46 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 repository171 other files it gives its agents.
- skills/05-ereuna/humanizer/AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- algorithmoi-polyplokotitaSkill
- anagnosi-paperSkill
- arxitektoniki-ypologistonSkill
- diktya-ypologistonSkill
- elegxos-vivliografiasSkill
- ellinika-texnika-keimenaSkill
- enswmatomena-systimataSkill
- ergasia-panepistimiouSkill
- fysiki-grafiSkill
- kathigitis-kodikaSkill
- latex-ellinikaSkill
- leitourgika-systimataSkill
- metaglottistesSkill
- omadiki-ergasia-gitSkill
- proetoimasia-exetaseonSkill
- ptyxiaki-diplomatikiSkill
- theoria-ypologismouSkill
- vaseis-dedomenonSkill
- discernment-nudgeSkill
- karpathy-guidelinesSkill
- mcp-builderSkill
- skill-creatorSkill
- using-superpowersSkill
- brainstormingSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- verification-before-completionSkill
- writing-plansSkill
- bash-defensive-patternsSkill
- cpp-proSkill
- c-reviewSkill
- debugging-strategiesSkill
- devcontainer-setupSkill
- frontend-designSkill
- gh-cliSkill
- go-concurrency-patternsSkill
- golang-proSkill
- java-architectSkill
- javascript-proSkill
- modern-cppSkill
- modern-pythonSkill
- mutation-testingSkill
- property-based-testingSkill
- python-proSkill
- rust-async-patternsSkill
- rust-engineerSkill
- rust-reviewSkill
- shellcheck-configurationSkill
- typescript-proSkill
- webapp-testingSkill
- web-artifacts-builderSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. 11 are common, 11 are distinctive, and 1 is very specific to this project.
11
Common
Most of the 172 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 172 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.
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.

