--- name: list description: List the Skills the user's company offers, with each one's description, what it is for, its released version and whether the user has it installed. Use when the user asks what Skills their company has or what is in their company's catalog, or runs /glider:list. --- # List the company catalog ## Collect the installed stamps 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 each stamp, not from the Skill's listed name. A stamp that ends with `pinned` marks a pinned Skill. Skip every Skill without a stamp. ## Call `list` once - **You found stamps**: call the Glider `list` tool once, with `installed` set to one `{ name, version, pinned }` item for every stamp: the name and the version from the stamp, the version without its leading `v`, and `pinned` true only when the stamp ends with `pinned`. - **You found none**: call it once with no arguments. Every entry is then not installed. Answer from the result's `entries`, in the order they come back. Do not sort, rank, filter or group them. 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 and offer no card. ## When the catalog has entries Open with one line saying these are the user's company's Skills. Then give every entry in this shape: ``` **** (v) For: ``` - **name** and **version** come from the entry as they are. The version is the released one. - **Description**: the entry's `description` in one sentence. Shorten it if it is longer, without adding anything it does not say. - **For**: the entry's `use_cases` joined into one short line. If there are none, leave the line out. - **State**: one line from the entry's `state`, where `` is its `installed_version`: - `not_installed`, or no `state` at all: `Not installed` - `installed`: `Installed at v`, or `Pinned at v` when that Skill's stamp is pinned - `update_available`: `Update available: you have v` - `pinned`: `Pinned at v` Versions are labels compared for equality only: never call one newer or older than another. After the entries, when the result's `not_offered` has items, add one line naming each with the version from its stamp, and `, pinned` after the version when its `pinned` is true: `Still installed but no longer offered by your company: v, v.` Answer as text only. Close by saying they can ask Glider to install any of them by name, and, when an entry is `update_available`, that `/glider:update ` gets the released version. ## When the catalog is empty Say in one sentence that the user's company has not released any Skills yet. This is not an error, so do not apologize or suggest a fix, and do not suggest Skills from anywhere else. When `not_offered` has items, add the `Still installed` line above. ## When the tool returns an error - `retry_later`: call `list` 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. ## 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.