We split this skill into the rules it gives an agent

13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈9

  Distinctive · estimate

  This author's own choices. Worth a look.

• 4

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Before each dispatch or retry, read host dispatch and supply its resolved installed paths.

   line 10
2. Distinctive:

   Before artifact work, read artifact schema.

   line 11
3. Distinctive:

   Before the tier sort, read finding format.

   line 12
4. Distinctive:

   Before each consuming step, read its linked shared rules from this installed skill directory.

   line 13
5. Distinctive:

   If a required read fails, stop that step with the exact path.

   line 14
6. Distinctive:

   Before finalizing prose you author, read the writing standards.

   line 15
7. Very specific:

   Run after CODE REVIEW passes.

   line 19
8. Very specific:

   Run the review loop that the team-code-review execution reference states, with the deltas in Execution.

   line 21
9. Very specific:

   Write one security-review-<n>.md per completed round.

   line 22
10. Distinctive:

    Never: stop to ask the user which Blocking or Major items to address (the no-consult rule).

    line 24
11. Very specific:

    Never load team-code-review or team-pr.

    line 27
12. Distinctive:

    Read each reference completely when reaching that stage.

    line 31
13. Distinctive:

    Read and apply: execution rules.

    line 38

≈ “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.