We split this skill into the rules it gives an agent

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

• 0

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Use this entrypoint only when an existing portfolio/static-site repository and an authorized GitHub Pages change are in scope.

   line 9
2. Distinctive:

   Before editing or media replacement: references/inspect-media.md

   line 11
3. Distinctive:

   Before publishing: references/publish.md

   line 12
4. Distinctive:

   After a layout/media change: references/validate.md

   line 13
5. Distinctive:

   Verify authorship/labels and never invent clients, metrics, or project claims.

   line 18
6. Distinctive:

   Keep source media, repository state, and deployed Pages state separately verifiable.

   line 19
7. Distinctive:

   Use dry-run before any push.

   line 20
8. Distinctive:

   Before, a portfolio update is one command away from an accident:

   line 24
9. Distinctive:

   After, the change is inspected before anything leaves the machine:

   line 31

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