--- name: status description: Show which of their company's Skills the user has installed, at which versions, and whether each is current, has an update available, is pinned or is no longer offered. Use when the user asks which company Skills they have, what version of a Skill they are on, whether their company Skills are up to date, or runs /glider:status. --- # Installed company Skills The versions and pins come from the skill list you already see in this conversation: the name and description of every Skill installed on the user's account. One call to the Glider `list` tool adds each Skill's state. This skill only reports: call no other tool, read no file, and never offer a Save or Update card from it. ## 1. Find the company Skills 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. - Skip every Skill whose description has no stamp. It is the user's own, not one of their company's Skills, so leave it out without mentioning it. When you found none, call no tool. Answer with one sentence and stop: the user has none of their company's Skills installed yet, and `/glider:list` shows what their company offers. ## 2. Learn each Skill's state with one `list` call Call the Glider `list` tool once, with `installed` set to one `{ name, version, pinned }` item for every stamp you found: the name and the version from the stamp, the version without its leading `v`, and `pinned` true only when the stamp ends with `pinned`. Pass every stamp even when the user asked about one Skill. 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. Call `download` for nothing. Read each installed Skill's state from the result: - Its name is in `not_offered`: the company no longer offers it. - Otherwise find the entry whose `name` is the name in its stamp. The entry's `version` is the released version, and its `state` is `installed` (the installed copy is the released version), `update_available` (an unpinned copy that is not the released version) or `pinned` (a pinned copy that is not the released version). Versions are labels compared for equality only: never call one newer or older than another. If you cannot get a result, follow "When Glider cannot check" below. ## 3. Answer List every company Skill you found, one per line, sorted by name. Use the line for its state, word for word, where `` is the installed version from the stamp and `` is the entry's `version`: - `installed`, stamp not pinned: `- v: current` - `installed`, stamp pinned: `- v, pinned: current` - `update_available`: `- v: update available, v is the released version. /glider:update gets it.` - `pinned`: `- v, pinned: v is the released version. /glider:update moves you to it.` - In `not_offered`, adding `, pinned` after the version when the stamp is pinned: `- v: no longer offered by your company. To remove it, open its row on Claude's Plugins page and select Remove; /glider:remove gives the full steps.` Say nothing else about each Skill, and remove nothing yourself. When the user asked about one Skill, answer with that Skill's line only, worded as above. If it has no stamp, say it is not installed as one of their company's Skills; when an entry in the result has that name, add that their company offers it at v`` and `/glider:install ` installs it. ## When Glider cannot check The user still gets their versions and pins. This applies when: - `list` returns `retry_later`: call it once more with the same arguments first, and come here only if it fails again. - `list` returns any other error, or the call itself fails. - No Glider tool is listed at all. List every company Skill from the stamps alone, one per line, sorted by name, or only the Skill the user asked about: ``` - v - v, pinned ``` Then add this line, word for word: `Glider could not check for updates just now, so these are the versions you have installed.` When the user asked about one Skill and it has no stamp, give no version line. Say it is not installed as one of their company's Skills, and that Glider could not check just now whether their company offers it. When no Glider tool is listed at all, do not stop before answering: give the lines above first, then the step for the user's surface from "When Glider isn't connected" below. ## 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.