We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

• 0

  Common

  Most of the 162 edited versions we read keep these.

• 8

  Distinctive

  This author's own choices. Worth a look.

• 0

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   Use this skill when the user wants confidence that a feature, fix, or refactor actually works.

   line 8
2. Distinctive:

   Prefer existing tests first.

   line 15
3. Distinctive:

   If coverage is missing, run the narrowest direct verification commands available.

   line 16
4. Distinctive:

   If direct automation is not enough, describe the manual validation steps and gather concrete observable evidence.

   line 17
5. Distinctive:

   Do not say a change is complete without evidence.

   line 27
6. Distinctive:

   If a check fails, include the failure clearly.

   line 28
7. Distinctive:

   If no realistic verification path exists, say that explicitly instead of bluffing.

   line 29
8. Distinctive:

   Prefer concise evidence summaries over noisy logs.

   line 30

“Common” is measured: kept by at least 6 in 10 of the 162 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.

• Other versions187 projects use a version of this.

  Word for word · 2

  1. Yeachan-Heo/oh-my-claudecode★ 40k100% same
  2. Yeachan-Heo/oh-my-claude-sisyphus★ 40k100% same

  Edited · 1

  1. zereight/gitlab-mcp★ 2.1k66% same

  Wrote their own version · 184

  1. facebook/react★ 252ksame name
  2. react/react★ 251ksame name
  3. oven-sh/bun★ 96ksame name
  4. anthropics/financial-services★ 41ksame name
  5. anthropics/financial-services-plugins★ 39ksame name
  6. anthropics/claude-quickstarts★ 19ksame name
  7. NVIDIA-NeMo/Speech★ 19ksame name
  8. NVIDIA-NeMo/NeMo★ 19ksame name
  9. sumatrapdfreader/sumatrapdf★ 18ksame name
  10. udecode/plate★ 17ksame name

  174 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 build-fix, instinct-export and 5 more.

  Other files people use alongside this one.

  How we pick theseFiles 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.

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 6 projects that use this

  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • AviadPSkill

    risk-assess

    Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

    Also in 3 projects that use this

  • AaravChadhaSkill

    secure

    Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high/medium/low confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization/crypto/transport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.

    Also in 3 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 10 projects that use this

• In this repository29 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • skills/AGENTS.mdAGENTS.md
  • .github/copilot-instructions.mdCopilot instructions
  • ai-slop-cleanerSkill
  • autopilotSkill
  • cancelSkill
  • configure-notificationsSkill
  • debugSkill
  • deep-diveSkill
  • deepinitSkill
  • deep-interviewSkill
  • external-contextSkill
  • mcp-setupSkill
  • omni-doctorSkill
  • omni-referenceSkill
  • omni-setupSkill
  • omni-planSkill
  • ralphSkill
  • ralplanSkill
  • releaseSkill
  • rememberSkill
  • setupSkill
  • skillifySkill
  • skillSkill
  • teamSkill
  • traceSkill
  • ultraqaSkill
  • ultraworkSkill
  • wikiSkill