We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈4

  Distinctive · estimate

  This author's own choices. Worth a look.

• 2

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Treat the window as the lookback range for other team members' activity unless the user explicitly includes themselves.

   line 20
2. Very specific:

   Follow the installed team-collab-protocol skill and its references/team-progress.md flow.

   line 21
3. Distinctive:

   If the protocol skill is not available in the current session, read it from:

   line 22
4. Distinctive:

   If that file is missing, stop and tell the user to run:

   line 28
5. Distinctive:

   Keep the final report concise and sectioned.

   line 34
6. Very specific:

   If a future Codex version supports custom slash commands and /team-progress reaches the model as plain user text, handle it exactly the …

   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.