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.

update-tags - Prompt - OpenSmartRoute

Name: update-tags
Author: Blacksuan19

Prompt file imported from Blacksuan19/website (.github/prompts/update-tags.prompt.md). Copyright stays with the author.

Audit and update tags across all _posts/*.md files in this Jekyll site.

Instructions

Scan all posts — read every file in _posts/ and extract the tags: list from the front matter.
Report findings:
- Full list of all unique tags and how many posts use each
- Any tags that look like duplicates or variants (e.g. ML vs machine-learning, NLP vs nlp)
- Any tags that are not kebab-case (e.g. DataScience, Web Development)
- Posts missing a tags: field entirely
Ask for confirmation before making any changes.
Apply fixes — based on user input:
- Rename tags to kebab-case consistently across all affected posts
- Merge duplicate tag variants
- Add missing tags to posts
Regenerate tag pages after all edits:
```
python scripts/update_tags.py
```
Confirm the final tag count and list.

Rules

Tag names must be kebab-case, all lowercase: data-science, not DataScience
The tags/ directory is auto-generated — never edit it directly
A tag page is only created if at least one post uses that tag
Visual rendering is handled by _includes/tag-cloud.liquid, _includes/post-tags.liquid, _includes/tag-chip.liquid, and _includes/tag-label.liquid; keep content changes in post front matter and regenerate pages rather than editing tag pages directly

Install update-tags 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.

{ "prompt": "Audit and update tags across all `_posts/*.md` files in this Jekyll site.\n\n## Instructions\n\n1. **Scan all posts** — read every file in `_posts/` and extract the `tags:`\n list from the front matter.\n\n2. **Report findings**:\n - Full list of all unique tags and how many posts use each\n - Any tags that look like duplicates or variants (e.g. `ML` vs\n `machine-learning`, `NLP` vs `nlp`)\n - Any tags that are not kebab-case (e.g. `DataScience`, `Web Development`)\n - Posts missing a `tags:` field entirely\n\n3. **Ask for confirmation** before making any changes.\n\n4. **Apply fixes** — based on user input:\n - Rename tags to kebab-case consistently across all affected posts\n - Merge duplicate tag variants\n - Add missing tags to posts\n\n5. **Regenerate tag pages** after all edits:\n\n ```bash\n python scripts/update_tags.py\n ```\n\n6. **Confirm** the final tag count and list.\n\n## Rules\n\n- Tag names must be kebab-case, all lowercase: `data-science`, not `DataScience`\n- The `tags/` directory is auto-generated — never edit it directly\n- A tag page is only created if at least one post uses that tag\n- Visual rendering is handled by `_includes/tag-cloud.liquid`,\n `_includes/post-tags.liquid`, `_includes/tag-chip.liquid`, and\n `_includes/tag-label.liquid`; keep content changes in post front matter and\n regenerate pages rather than editing tag pages directly", "variables": [], "notes": "Audit, clean up, rename, or synchronize tags across all posts on this Jekyll site. Finds inconsistencies, duplicate variants, and missing tag pages, then runs scripts/update_tags.py.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/Blacksuan19/website", "path": ".github/prompts/update-tags.prompt.md", "ref": "f98f9bd23de9744e9ae3ba7f798d50f91711bdac", "url": "https://github.com/Blacksuan19/website/blob/f98f9bd23de9744e9ae3ba7f798d50f91711bdac/.github/prompts/update-tags.prompt.md", "key": "Blacksuan19/website/.github/prompts/update-tags.prompt.md" } } }

update-tags

About

Instructions

Rules

Install update-tags 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