Updates and Versions
How a new kit version reaches you, the kit's own version line and changelog, the catalogue stamp, what it means that the kit follows code, and the eval suite as the proof of a release.
The kit has its own version line, separate from Subscriby's, and a new version ships with each Subscriby deploy that changes a contract the kit describes: a tool, an endpoint, a webhook event, an ability, an error code, an SDK port or a creator feature. Between those deploys the installed copy stays exactly as it was, which is what makes a session reproducible.
See what you have
/plugin lists the two plugins with their version (the guard carries the kit's), and the kit's catalogue/stamp.json names the Subscriby catalogue the release was generated from (its version, the date and the counts per family).
Refresh the marketplace
/plugin marketplace update envigoClaude Code fetches the marketplace's current listing. A plugin whose manifest carries a version is pinned to that version until the manifest changes, so a cached copy stays in place until the kit's version is bumped; that is deliberate, so a release is a single, named change rather than whatever the repository held that morning.
Install the new version
Run /plugin install subscriby@envigo and /plugin install subscriby-guard@envigo again, or turn on auto-update for the marketplace under its settings in /plugin, and every later version arrives on its own. The changelog says what changed in each.
The kit follows code
Nothing in the kit is typed from memory. Every tool name, event, endpoint, ability, error code, team permission and count is generated from the catalogues Subscriby publishes at api.subscriby.net, the same files this site's references are built from; the guard's list of destructive tools and the agents' allowlists are generated from the tool annotations; and a check fails the kit's own build when a catalogue carries an item that no skill owns, so a new tool is placed in a skill by hand before a release can be cut. The skills' prose is written by people and reviewed against the documentation page each rests on.
| When Subscriby changes… | The kit… |
|---|---|
| A tool, an endpoint, a webhook event, an ability or an error code | Regenerates its references and the guard's hook, places the new item in a skill, and ships a new version of both plugins with the deploy. |
| A creator feature with a new page here | Updates the skill whose domain changed and links the page. |
| An SDK port or a manifest block | Updates the connector skills. |
| Nothing that an integration can see | Does not move; your installed copy stays as it was. |
One version per deploy
The kit is bumped once per Subscriby deploy that changes a contract, never for a tool that has not shipped. A version named in the changelog always describes a catalogue that is live.
The eval suite as the proof
Each release runs the kit's eval suite: cases phrased as a user would type them (a sign-in check, a launch checklist, a broadcast that must be previewed and confirmed, a cancellation that must be confirmed, the week's figures, a webhook verifier, the events a CRM subscribes to, a connector's data rules, a request that must not trigger the plugin), graded on the answer and on the steps Claude took, against mocked tools that carry the real schemas, and compared with a run without the plugin. A case that regresses blocks the release. The suite lives in the repository beside the skills, so anyone can run it against a checkout with npm run eval.
Versions
The kit uses semantic versions and keeps a changelog in its repository. A patch is a correction to prose or a reference regenerated from an unchanged catalogue; a minor adds or changes skills, commands or agents for a new or changed Subscriby contract; a major changes how the kit is installed or renames a skill or a command. The Subscriby catalogue version a release was generated from is recorded with it.
How is this guide?
Last updated on
Permissions and Safety
The guard plugin whose hook makes every destructive tool ask, what destructive means on the Subscriby server, least-privilege tokens, the audit trail, members' data, and the settings a team admin uses.
Troubleshooting
What to do when the marketplace cannot be added, the sign-in never appears, tools are missing or duplicated, a call answers TOKEN_MISSING_ABILITY, a destructive tool ran without a prompt, a skill does not fire, or the eval suite will not run.