How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

golang-tui:update-examples - Prompt

Name: golang-tui:update-examples
Author: lrstanley

Prompt file imported from lrstanley/skills (.cursor/commands/golang-tui:update-examples.md). Copyright stays with the author.

/golang-tui:update-examples

Goal: Align skills/golang-tui/references/libraries/examples.md with the current Bubble Tea examples README.

Source of truth: The README at main on GitHub -- not a local clone unless you are validating links.

Steps

Fetch the canonical README (raw):

https://raw.githubusercontent.com/charmbracelet/bubbletea/main/examples/README.md
Parse structure: Treat each ### -level heading as one documented example. The following paragraph usually contains `dirname` naming the directory under examples/. Build an ordered list of (heading title, directory name, descriptive sentence from the README).
Compare to skills/golang-tui/references/libraries/examples.md:
- New README section / example → add a matching ### block in the same order as upstream. Each block must include:
  - Tree: link: https://github.com/charmbracelet/bubbletea/tree/main/examples/<dirname>
  - Short bullets naming features and components (Bubble Tea messages, tea.Cmd patterns, Bubbles packages, Lip Gloss, external libs like Glamour) -- no full code blocks; this file stays a map, not a tutorial.
- Removed from README → remove the corresponding ### section from the reference (unless the project explicitly keeps historical entries -- default is delete to stay aligned).
- Renamed directory or heavily rewritten blurb → update the tree URL and bullets so they match the new README. If only wording changes slightly, adjust bullets minimally.
Preserve file-level framing: Keep the intro paragraph, the link to the GitHub README as the authoritative index, the pointer to this command path, and the Scope note at the bottom (refresh the "not every folder" wording if the README policy changes).
Validate links: Spot-check that each examples/<dirname> path exists on main (e.g. GitHub tree URL or API). If the README references a directory that does not exist yet, keep the README as source of truth and note the mismatch in your summary to the user.

Output

Brief summary of what changed (added / removed / updated sections).
If nothing changed, say so explicitly.

Install golang-tui:update-examples and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# /golang-tui:update-examples **Goal:** Align `skills/golang-tui/references/libraries/examples.md` with the current [Bubble Tea examples README](https://github.com/charmbracelet/bubbletea/blob/main/examples/README.md). **Source of truth:** The README at `main` on GitHub -- not a local clone unless you are validating links. ## Steps 1. **Fetch the canonical README** (raw): `https://raw.githubusercontent.com/charmbracelet/bubbletea/main/examples/README.md` 2. **Parse structure:** Treat each `### `-level heading as one documented example. The following paragraph usually contains `` `dirname` `` naming the directory under `examples/`. Build an ordered list of `(heading title, directory name, descriptive sentence from the README)`. 3. **Compare to** `skills/golang-tui/references/libraries/examples.md`: - **New** README section / example → add a matching `###` block in the same order as upstream. Each block must include: - **`Tree:`** link: `https://github.com/charmbracelet/bubbletea/tree/main/examples/<dirname>` - Short bullets naming **features and components** (Bubble Tea messages, `tea.Cmd` patterns, Bubbles packages, Lip Gloss, external libs like Glamour) -- **no full code blocks**; this file stays a map, not a tutorial. - **Removed** from README → remove the corresponding `###` section from the reference (unless the project explicitly keeps historical entries -- default is **delete** to stay aligned). - **Renamed directory or heavily rewritten blurb** → update the tree URL and bullets so they match the new README. If only wording changes slightly, adjust bullets minimally. 4. **Preserve file-level framing:** Keep the intro paragraph, the link to the GitHub README as the authoritative index, the pointer to this command path, and the **Scope note** at the bottom (refresh the "not every folder" wording if the README policy changes). 5. **Validate links:** Spot-check that each `examples/<dirname>` path exists on `main` (e.g. GitHub tree URL or API). If the README references a directory that does not exist yet, keep the README as source of truth and note the mismatch in your summary to the user. ## Output - Brief summary of what changed (added / removed / updated sections). - If nothing changed, say so explicitly.

{ "prompt": "# /golang-tui:update-examples\n\n**Goal:** Align `skills/golang-tui/references/libraries/examples.md` with the current [Bubble Tea examples README](https://github.com/charmbracelet/bubbletea/blob/main/examples/README.md).\n\n**Source of truth:** The README at `main` on GitHub -- not a local clone unless you are validating links.\n\n## Steps\n\n1. **Fetch the canonical README** (raw):\n\n `https://raw.githubusercontent.com/charmbracelet/bubbletea/main/examples/README.md`\n\n2. **Parse structure:** Treat each `### `-level heading as one documented example. The following paragraph usually contains `` `dirname` `` naming the directory under `examples/`. Build an ordered list of `(heading title, directory name, descriptive sentence from the README)`.\n\n3. **Compare to** `skills/golang-tui/references/libraries/examples.md`:\n\n - **New** README section / example → add a matching `###` block in the same order as upstream. Each block must include:\n - **`Tree:`** link: `https://github.com/charmbracelet/bubbletea/tree/main/examples/<dirname>`\n - Short bullets naming **features and components** (Bubble Tea messages, `tea.Cmd` patterns, Bubbles packages, Lip Gloss, external libs like Glamour) -- **no full code blocks**; this file stays a map, not a tutorial.\n\n - **Removed** from README → remove the corresponding `###` section from the reference (unless the project explicitly keeps historical entries -- default is **delete** to stay aligned).\n\n - **Renamed directory or heavily rewritten blurb** → update the tree URL and bullets so they match the new README. If only wording changes slightly, adjust bullets minimally.\n\n4. **Preserve file-level framing:** Keep the intro paragraph, the link to the GitHub README as the authoritative index, the pointer to this command path, and the **Scope note** at the bottom (refresh the \"not every folder\" wording if the README policy changes).\n\n5. **Validate links:** Spot-check that each `examples/<dirname>` path exists on `main` (e.g. GitHub tree URL or API). If the README references a directory that does not exist yet, keep the README as source of truth and note the mismatch in your summary to the user.\n\n## Output\n\n- Brief summary of what changed (added / removed / updated sections).\n- If nothing changed, say so explicitly.", "variables": [], "notes": "Re-sync golang-tui Bubble Tea official examples reference from charmbracelet/bubbletea examples README", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/lrstanley/skills", "path": ".cursor/commands/golang-tui:update-examples.md", "ref": "4353f0a4352cc513377a85402fe5f39c9abe4248", "url": "https://github.com/lrstanley/skills/blob/4353f0a4352cc513377a85402fe5f39c9abe4248/.cursor/commands/golang-tui:update-examples.md", "key": "lrstanley/skills/.cursor/commands/golang-tui:update-examples.md" } } }

golang-tui:update-examples

About

/golang-tui:update-examples

Steps

Output

Install golang-tui:update-examples and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews