We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈6

  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:

   Create or update an Obsidian release note when a project is deployed, published, or finished.

   line 8
2. Distinctive:

   Use vault-relative paths only.

   line 24
3. Very specific:

   Use list_notes or get_note to check whether a release note already exists.

   line 44
4. Very specific:

   Create the folder Release Notes if missing.

   line 45
5. Distinctive:

   Create or update the release note.

   line 46
6. Distinctive:

   Keep wording useful for both public release history and private project memory.

   line 47
7. Distinctive:

   Prefer bullets for shipped changes and verification.

   line 53
8. Distinctive:

   Avoid hype. State what shipped and why it matters.

   line 55
9. Very specific:

   Use templates/release-note.md as the base structure when creating a new note.

   line 60

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