nahiddotai What's New
The Job
Tell the user what their installed version contains, what changed recently, and whether something newer exists.
How to Run It
- Read the installed release metadata at
${CLAUDE_PLUGIN_ROOT}/catalog/release.json(fall back tocatalog/release.jsontwo directories above this skill file). That file states the installed version and its changelog entries. - Present the installed version and its changes in plain language, newest first: new powers as jobs ("you can now turn a meeting into a deliverable"), then improvements, then fixes. Skip internal or build-only changes. When a release entry credits user input (feedback or requests), lead with that: this collection is self-improving, and "this exists because users asked for it" is the most important line in any release.
- If the
operator_powersMCP server is connected, you may callget_whats_newwith the installed version to learn about releases newer than the installed one. If something newer exists, say what it adds and how updating works: "updates arrive through your marketplace; refresh it and update the plugin, then start a new session." - If the service is unreachable, show the installed changelog and say plainly that live release information was unavailable, without guessing whether an update exists.
Boundaries
- Never claim a newer skill is already installed; live catalogue data describes what an update would bring.
- Never promise instant updates; the user's client controls when updates apply.
- The only data sent to the service is the installed version number, and only when live information is wanted.