We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈8

  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:

   Use this skill when monitoring Squad issues, pull requests, CI, review feedback, or a labeled work queue.

   line 11
2. Distinctive:

   Start with a named repository, explicit workstream, label set, and state filter.

   line 16
3. Distinctive:

   Do not turn monitoring into product implementation or broad cleanup.

   line 18
4. Distinctive:

   After every mutation, refetch the exact item and verify the requested transition and fields.

   line 27
5. Distinctive:

   Stop immediately on a verification mismatch.

   line 28
6. Distinctive:

   Use the focused two-pass scan for broad retrieval, then inspect only actionable candidates.

   line 29
7. Distinctive:

   Stop before mutation when the workstream, labels, repository, or state filter is ambiguous.

   line 33
8. Distinctive:

   Stop when candidates cannot be hydrated or post-mutation state cannot be verified.

   line 34
9. Distinctive:

   Stop when an action would exceed the explicitly scoped queue or become product work.

   line 35

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