We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are 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.

• 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 improving the workspace itself rather than a single child repo.

   line 8
2. Distinctive:

   Keep the workspace predictable, low-duplication, and easy for Codex or other local agents to navigate.

   line 12
3. Very specific:

   Read AGENTS.md and the relevant docs in docs/.

   line 16
4. Very specific:

   Run tools/scripts/doctor-workspace.sh before changing shared setup assumptions.

   line 17
5. Distinctive:

   Prefer workspace-native scripts and templates over ad hoc one-off layouts.

   line 18
6. Distinctive:

   Keep repo installs local to each repo.

   line 19
7. Very specific:

   When a reviewed reference appears in tools/ref/, extract the pattern into tracked workspace code, docs, templates, or skills rather than …

   line 20
8. Distinctive:

   Do not make experimental orchestration layers mandatory for the whole workspace.

   line 34
9. Distinctive:

   Do not centralize dependencies across unrelated repos.

   line 35
10. Distinctive:

    Prefer small, inspectable tracked improvements over hidden runtime magic.

    line 36

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