{"id":9059,"plugin_id":"plugin_asdk_app_6a605b4283948191831f5f8c9b59fbd9","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T22:54:06.495Z","digest":"fe0bf60191459248e4e137998c833ac849fcce70bd4eef0f7d5fd488d269021c","against":null,"payload":{"name":"whats-new","description":"Explain what changed in Operator Powers, which version is installed, whether a newer release exists, and how to update.","included_files":[],"skill_md_contents":"---\nname: whats-new\ndescription: Explain what changed in Operator Powers, which version is installed, whether a newer release exists, and how to update.\n---\n\n# What's New\n\n## The Job\n\nTell the user what their installed version contains, what changed recently, and whether something newer exists.\n\n## How to Run It\n\n1. Read the installed release metadata at `${CLAUDE_PLUGIN_ROOT}/catalog/release.json` (fall back to `catalog/release.json` two directories above this skill file). That file states the installed version and its changelog entries.\n2. 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.\n3. If the `operator_powers` MCP server is connected, you may call `get_whats_new` with 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.\"\n4. If the service is unreachable, show the installed changelog and say plainly that live release information was unavailable, without guessing whether an update exists.\n\n## Boundaries\n\n- Never claim a newer skill is already installed; live catalogue data describes what an update would bring.\n- Never promise instant updates; the user's client controls when updates apply.\n- The only data sent to the service is the installed version number, and only when live information is wanted.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}