Step 4 of 4

Distribution & Versioning

Share a skill without breaking the people who already use it.

Once other people rely on a skill, changes have blast radius. Treat the description and the skill's observable behavior as an interface: widening a trigger or changing outputs can surprise every user at once.

  1. Ship a short README next to SKILL.md: what it does, what it needs, how to install it.
  2. Record a version and note behavior changes so users can decide when to adopt them.
  3. Change triggering deliberately — a broadened description reroutes everyone's requests.