Annotate a version with a note

A diff shows what changed; a note says why. You can annotate any version with a short note — "tightened the intake questions", "raised the liability floor to 2×" — and it shows right on the version's row in history.

Add a note

1. Open the skill and click Version History.
2. Find the version you're working on and choose Add note (or edit an existing one).
3. Write up to 500 characters and save.

Write the note while the version is still a draft — publishing freezes the version, note included, so the record travels with it permanently.

Notes you get for free

When you restore an earlier version, the new version is automatically annotated "Restored from vN" — rollbacks document themselves.

What makes a good note

• Say what changed in the team's language: "added the renewal-clause checklist", not "updates".
• Flag anything a teammate should re-check: "pricing thresholds changed — confirm with finance".
• Keep it to one line; the diff carries the detail.

A skill whose history is annotated is a skill people update confidently — nobody's afraid to improve it when every change is explained and any version can be restored.

Availability

All plans. Adding or editing notes requires edit access to the skill; everyone with read access sees them in history.