We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈7

  Distinctive · estimate

  This author's own choices. Worth a look.

• 1

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Check that name uses lowercase letters, digits, and hyphens, matches the directory name, and stays within the standard limit.

   line 11
2. Distinctive:

   Look for overlapping triggers, duplicated skills, missing prerequisites, nonportable absolute paths, undocumented scripts, and …

   line 12
3. Distinctive:

   Check that workflows tell the agent to distinguish observed facts from assumptions and to report commands/tests actually performed.

   line 14
4. Distinctive:

   Ensure dependencies and optional resources are documented.

   line 15
5. Distinctive:

   Run repository validation and inspect a sample package listing before release.

   line 16
6. Distinctive:

   Do not modify a skill to loosen safety restrictions merely to improve its apparent capability.

   line 22
7. Distinctive:

   Do not claim compatibility has been tested on a host that was not available.

   line 23
8. Distinctive:

   Treat natural-language instructions as executable policy: inspect them with the same seriousness as code.

   line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.