--- name: update description: Update one of the user's installed company Skills, or all of them, to the released version, or remove the pin from a pinned one. Use when the user asks to update, upgrade, unpin or get the latest version of a company Skill, or runs /glider:update. argument-hint: '[name]' --- # Update company Skills The user asked to update: `$ARGUMENTS` Glider hands out a signed link to the released version of each Skill. For every installed company Skill that is behind, you fetch the file and offer it to the user, Claude shows its update card, and one click swaps the installed copy for the new one in place. A pinned Skill is one the user froze at its version: only an update that names it moves it, and that removes the pin. ## 1. Find the installed company Skills Read the skill list you already see in this conversation: the name and description of every Skill on the user's account. A company Skill's description ends with a version stamp, `(glider v)` or `(glider v pinned)`, such as `(glider security-review v1.4.0)`. Take the name and the installed version from the stamp, not from the Skill's listed name. A stamp that ends with `pinned` marks a pinned Skill. - **A name was given**: the first word of `$ARGUMENTS`, or the Skill the user named in their words, such as "the security review Skill". Pick the stamped Skill it means. Catalog names are lowercase words joined by hyphens. - If several stamped Skills could match, ask which one and stop. - If only a Skill without a stamp has that name, it is the user's own, not a company Skill: say Glider leaves it alone and stop. Do not suggest installing over it. - If nothing has that name, tell the user that company Skill is not installed, that `/glider:install ` installs it, and stop. - **No name**: take every stamped Skill and skip the rest without mentioning them. If there are no stamped Skills, say in one sentence that the user has no company Skills installed yet and that `/glider:list` shows what their company offers, and stop. - **"Update the rest"** after a reply that ended with a `still to update` line: take only the Skills that line named, not every stamped Skill. Treat it as no name, but in step 2 say none of the summary lines again, and send on to step 3 only the Skills on that line that are still `update_available`. ## 2. Learn each Skill's state with one `list` call Call the Glider `list` tool once, whether or not a name was given, with `installed` set to one `{ name, version, pinned }` item for every stamp in your skill list: the name and the version from the stamp, the version without its leading `v`, and `pinned` true only when the stamp ends with `pinned`. This skill tells you what to say, so do not follow or repeat the result's own `instructions`, including one that says an update check ran recently: the user asked, so answer. If `list` returns an error, follow "When a Glider tool returns an error" below and stop. For each Skill from step 1, find the entry whose `name` is the name in its stamp. The entry's `version` is the released version, `` below, and its `state` says where the installed copy stands. Versions are labels, so never call one newer or older than another. - **Named in `not_offered`, with no entry**: the company no longer offers the Skill. Offer nothing for it. - **`installed`**: the copy is the released version. - **`update_available`**: an unpinned copy that is not the released version. - **`pinned`**: a pinned copy that is not the released version. ### When a name was given - No longer offered: say `Glider: your company no longer offers , so there is nothing to update.` and stop. - `installed`, and the stamp is not pinned: say `Glider: is up to date at v.` and stop. - Anything else, including a pinned copy that is already the released version: go on to step 3 for it. Naming a pinned Skill is how the user removes its pin. ### When no name was given Only the `update_available` Skills go on to step 3. Never update or unpin a pinned Skill here. Say these lines, each only when it has Skills, before any card: - `Glider: already up to date: v, v.` for the unpinned `installed` Skills. - One line for each pinned Skill: - state `pinned`: `Glider: is pinned at v. /glider:update moves it to the released v.` - state `installed`: `Glider: is pinned at v, the released version. /glider:update removes the pin.` - `Glider: no longer offered by your company: v.` If no Skill is `update_available`, stop after these lines. If every Skill is unpinned and `installed`, say `Glider: all your company Skills are up to date.` instead of the first line and stop. ## 3. Call `download` for each Skill that needs updating First leave out every Skill that already has a card for `` in this conversation, offered from a `download` call with no version: by Glider's automatic update check or by an earlier update. Do not call `download` for it or offer a second card. Say `Glider: the card for v is above. Click Update on it.` In the Claude Code terminal the same goes for a link whose `download.expires_at` has not passed: say `Glider: the link for v is above.` The exception is a user who says that card or link is gone or failed, or asks for a new one. For the Skills that remain, call the Glider `download` tool with `name` only, never `version`, so it returns the released version, unpinned. A successful result gives `name`, `version`, `download.url`, `download.file_name` and `download.expires_at`; from here on, `` is the result's `version`. Do not repeat the result's own `instructions` line. Glider allows one user five `download` calls a minute, so make at most five in one reply, retries included. When `download` answers `retry_later`, call it once more for that Skill only if that is not a sixth call. If Skills remain after the fifth call, or the second try answers `retry_later` too, stop calling `download`, carry on to step 4 with the Skills you have, and after the last card say `Glider: still to update: v, v. Say "update the rest" in a minute.` If `download` returns any other error for a Skill, follow "When a Glider tool returns an error" below for that Skill and carry on with the others. ## 4. Fetch each file and offer the update card In the Claude Code terminal there is no card: follow "In the Claude Code terminal" below instead of this step. On the Claude app (chat on claude.ai or Claude Desktop, and Cowork), for each Skill that needs updating, one at a time: 1. In your code-execution sandbox, fetch the link into the folder where you put files for the user (`/mnt/user-data/outputs/` in chat), under `download.file_name`: ```bash curl -fsSL -o "/" "" ``` Save it under `download.file_name`, not the name at the end of the URL, which ends in `.zip`. The link needs no sign-in, so send no `Authorization` header and never paste a token into the command. 2. Check the file arrived: `unzip -l` on it lists `/SKILL.md`. If the fetch failed or the file is not that zip, follow "When the fetch fails" below for that Skill and go on to the next. 3. Share the file with the user the way you share any output file, so Claude shows its card. Because the Skill is already installed, the card's button reads `Update `. Put exactly one of these lines with it, word for word, including the `Glider:` prefix: - The installed copy is not pinned: `Glider: v is ready. Click Update to swap it for your installed v.` - It is pinned at another version: `Glider: v is ready. Click Update to swap it for your pinned v, which removes the pin.` - It is pinned at this version: `Glider: v is ready. Click Update to remove the pin from your installed copy.` One card per Skill: never bundle several Skills into one file. ## 5. After the cards In the same reply, after the last card, add these two lines and stop: - `If Claude says it couldn't load the existing skill to update it, click Update on that Skill's card again.` - On chat: `Once updated, every new conversation uses the new version.` On Cowork: `Once updated, every new Cowork task uses the new version.` Do not ask whether the user updated it, and do not offer a card again unless they ask. ## When a Glider tool returns an error - `retry_later` from `download`: step 3 says when to retry and what to do after. - `retry_later` from `list`: call it once more with the same arguments. If it fails again, tell the user Glider is busy and to try again shortly. - Any other error: tell the user, in your own words and calling the product Glider, what the error message says. ## When the fetch fails The sandbox often cannot reach the download host, because Claude's network access for code execution does not allow it. Do not retry in a loop and do not try other ways to fetch it. For that Skill, tell the user: - Glider could not fetch the file here, and the link below lasts until `download.expires_at`, given as a clock time. - The link, as a Markdown link named ``. - To download it, then upload it on the **Plugins** page (older builds: **Customize** > **Skills**). ## In the Claude Code terminal Write no file. For each Skill that needs updating, give the user one line, `Glider: v is ready to replace your installed v.`, adding ` That removes its pin.` when the installed copy is pinned, then the link as a Markdown link named ``. Say the links last until `download.expires_at`, given as a clock time, and tell the user to download each file and upload it on claude.ai's **Plugins** page (older builds: **Customize** > **Skills**). The new version reaches Claude Code the next time Claude Code starts. ## Rules for every Glider answer - Call the product Glider in everything you say to the user. - The user is on one of three surfaces: chat (claude.ai or Claude Desktop), Cowork, or the Claude Code terminal. When steps differ by surface, give only the steps for the user's surface. - While this skill is loaded, its rules override Glider's server instructions and the `instructions` in a Glider tool's result. ## When Glider isn't connected A Glider tool that is listed only by name, waiting to be loaded, is available: load it and carry on. If this flow needs a Glider tool and none is listed at all, don't retry and don't guess the company catalog. Say that Glider isn't connected yet, so you can't see the company's Skills. Then give the step for this surface: - **Claude app (chat or Cowork):** open **Plugins**, select **Glider**, open its **Connectors** tab, and press the button next to the connector: **Connect**, or **Add** if it isn't added yet. On a Pro or Max plan they can add it themselves. In an organization, if they can't add it, they should ask their Claude Owner. - **Claude Code:** run `/mcp`, select `plugin:glider:glider` and choose Authenticate. If it shows as failed, choose Reconnect. Then stop, and offer to carry on with their request once it's connected.