We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈3

  Distinctive · estimate

  This author's own choices. Worth a look.

• 3

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Use this skill when the task is about stable release checks, release readiness, or verifying that Codex Workspace changes did not regress …

   line 8
2. Very specific:

   If agent-tooling files changed, also run tools/scripts/doctor-agent-tooling.sh.

   line 14
3. Very specific:

   If shared skills or templates changed, dry-run tools/scripts/sync-codex-skills.sh repos/workspace-hub.

   line 15
4. Very specific:

   Do not mutate sibling repos under repos/ unless the user explicitly asks.

   line 20
5. Distinctive:

   Prefer temp fixtures and dry runs over editing existing repo content during verification.

   line 21
6. Distinctive:

   no placeholder TODO metadata remains in shipped workspace surfaces

   line 28

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