--- name: pin description: Pin one of the user's installed company Skills at the version they have, so Glider stops offering updates for it. Use when the user asks to pin, freeze, lock or keep a company Skill at its version, such as "pin the security review Skill", or runs /glider:pin. argument-hint: --- # Pin a company Skill The user asked to pin: `$ARGUMENTS` A pinned Skill stays at its version: Glider mentions a different released version but never offers it until the user asks to update that Skill by name. The pin lives in the installed copy's stamp, so pinning means handing the user the same version again, stamped `pinned`, on a card they save over the copy they have. ## 1. Find the Skill Read the skill list you already see in this conversation. A company Skill's description ends with a version stamp, `(glider v)` or `(glider v pinned)`. Take the name and the installed version, `` below, from the stamp, not from the Skill's listed name. The name is the first word of `$ARGUMENTS`, or the Skill the user named in their words, such as "the security review Skill". Catalog names are lowercase words joined by hyphens. - No Skill named: ask which one and stop. - Several stamped Skills could match: ask which one and stop. - Only a Skill without a stamp has that name: it is the user's own, not a company Skill. Say Glider can only pin company Skills and stop. - Its stamp ends with `pinned`: follow "Already pinned" below. - No Skill has that name: follow "Not installed" below. - Otherwise go on to step 2. Pin one Skill per request. If the user asks to pin all their Skills, ask which one to start with. ## 2. Call `download` with the installed version Call the Glider `download` tool with `name` and `version` set to `` without its leading `v`. Naming the version is what makes Glider stamp the copy `pinned`. A successful result gives `name`, `version`, `download.url`, `download.file_name` and `download.expires_at`. Do not repeat the result's own `instructions` line. If `download` returns an error, follow "When a Glider tool returns an error" below and stop. ## 3. Fetch the file and offer the 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): 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 and stop. 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 this one line with it, word for word, including the `Glider:` prefix: `Glider: this copy of is pinned at v. Click Update to pin your installed copy.` In the same reply, after the card, add these two lines and stop: - `Once saved, Glider leaves at v until you run /glider:update .` - `If Claude says it couldn't load the existing skill to update it, click Update again.` Saving is the user's choice. Do not ask whether they saved it, and do not offer the card again unless they ask. ## Already pinned Offer no card and do not call `download`. Call the Glider `list` tool once, with no arguments, and find the entry whose `name` is the name in the stamp. Versions are labels, so never call one newer or older than another. Answer with one line and stop: - The entry's `version` equals ``, or `list` returned an error: `Glider: is already pinned at v.` - It differs: `Glider: is already pinned at v. The released version is v, and /glider:update moves you to it.` - No entry: `Glider: is already pinned at v. Your company no longer offers it.` ## Not installed Call the Glider `list` tool once, with no arguments, and find the entry the user means by its name or description. - No entry matches: say `Glider: you don't have a company Skill called , and your company doesn't offer one.` and stop. - Several could match: ask which one and stop. - One matches: say `Glider: isn't installed, so there is nothing to pin yet. Say yes to install the released v, pinned.` and stop. If the user says yes, call `download` once with `name` and `version` set to ``, then carry on from step 3. The Skill is new on their account, so the card's button reads `Save`: the card line is `Glider: v is ready, pinned at that version. Click Save to add it to your Claude account.` and the last line after the card is left out. ## When a Glider tool returns an error - `retry_later`: call the tool once more with the same arguments. If it fails again, tell the user Glider is busy and to try again in a minute. - `unknown_version`: - The Skill is installed: say `Glider: your company no longer keeps v of , so Glider can't pin it. /glider:update moves you to the released version.` - You came from "Not installed": say `Glider: your company just changed , so v is no longer there to install. Ask to pin again to get the version it releases now.` - `not_offered`: - The Skill is installed: say `Glider: your company no longer offers , so Glider can't pin it. Your installed copy keeps working.` - You came from "Not installed": say `Glider: your company no longer offers , so there is nothing to install or pin.` - 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. Delete whatever the failed fetch left in the outputs folder, do not retry and do not try other ways to fetch it. Tell the user: - Glider could not fetch the pinned copy 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**), which pins `` at v``. ## In the Claude Code terminal Write no file. Give the user one line, `Glider: this copy of is pinned at v.`, then the link as a Markdown link named ``. Say it lasts until `download.expires_at`, given as a clock time, and tell them to download it and upload it on claude.ai's **Plugins** page (older builds: **Customize** > **Skills**). The pin 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.