agentleFS
supermorkatsupermorkat/qawa-arena/skills/writing-skills/SKILL.md

writing-skills

Skill1 starsChanged 17 days agoLicence not identifiedView on GitHub

Use when creating new skills, editing existing skills, or verifying skills work before deployment

194 other projects use a version of this, 127 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

  1. 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
  2. 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
  3. 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
  4. Before writing guidance, classify the baseline failure. The form that bulletproofs one failure type measurably backfires on another.dropped by 89 of 123
  5. 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
  6. 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
  7. When: Tool is reusable code, not just narrativedropped by 11 of 123
  8. When: Reference material too large for inlinedropped by 11 of 123

Rules people add

  1. A rule we can't quote: its licence doesn't allow itadded by 114 of 123
  2. A rule we can't quote: its licence doesn't allow itadded by 113 of 123
  3. A rule we can't quote: its licence doesn't allow itadded by 113 of 123
  4. A rule we can't quote: its licence doesn't allow itadded by 113 of 123
  5. A rule we can't quote: its licence doesn't allow itadded by 113 of 123
  6. A rule we can't quote: its licence doesn't allow itadded by 113 of 123
  7. A rule we can't quote: its licence doesn't allow itadded by 112 of 123
  8. 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.

Week of Sep 20: 2 new projectsWeek of Sep 27: 2 new projectsWeek of Oct 4: 4 new projectsWeek of Oct 11: 3 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 5 new projectsWeek of Nov 1: 3 new projectsWeek of Nov 8: 3 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 9 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.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • kntismSkill

    condition-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

  • aaddrickSkill

    writing-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

  • frankxaiSkill

    defense-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

  • MicrosoftSkill

    root-cause-tracing

    Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

    Also in 4 projects that use this

  • +3 more from Leodorareluctant259

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.