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.

optimize - Prompt - OpenSmartRoute

Name: optimize
Author: lenneTech

Prompt file imported from lenneTech/claude-code (.claude/commands/optimize.md). Copyright stays with the author.

Optimize Marketplace

Invoke the marketplace-optimizer skill with the arguments below and follow its execution protocol. The skill holds the procedure; .claude/skills/marketplace-optimizer/house-rules.md holds the decisions earlier runs settled.

What a Run Does

Cache, delta, coverage — records the cached Claude Code version, refreshes .claude/docs-cache/, triages failed sources (pages split upstream are added as sources, then accepted with --accept-shrink), lists documentation pages the cache lacks, and cuts the changelog to the entries since the last run.
Default model check — reads which model the opus/default aliases resolve to; a changed default adds a model-specific prompt audit against that model's prompting guide.
Secondary sources — optional URLs or files, from the arguments or one prompt.
Parallel analysis — five element agents (skills, commands, agents, hooks, mcp) analyse without editing, starting from the documentation diff, with live session signals relayed to them (failed MCP servers, hooks firing on the wrong turn); then the marketplace agent checks structure, dependencies, cross-references and features.
Verification — the high-impact claims are re-checked against the cached pages before anything is shown.
Findings and selection — the numbered findings are printed first, then selected via grouped multi-select.
Execution — approved changes are applied by agents on disjoint file partitions; the coordinator handles everything outside them. Nothing is staged or committed.
Final checks — plugin validation, cross-references, cache integrity, hook and node tests, a verification pass over the diff, and updates to CLAUDE.md and the house rules.

Usage

/optimize                                   # prompts once for secondary sources
/optimize --update-cache                    # force a cache refresh first
/optimize --skip-cache                      # analyse against the current cache
/optimize https://example.com/guide.md ./docs/notes.md   # secondary sources, no prompt

Flags

Flag	Description
`--update-cache`	Force cache update without version check
`--skip-cache`	Skip cache update entirely

Arguments that start with http:// or https:// are URLs; everything else is a local file path. Empty input, "keine", "none" or "no" at the prompt skips secondary sources; sources that contradict the cache are ignored.

Cache Configuration

.claude/docs-cache/sources.json is the single source of truth for the cache: sources (type md for GitHub raw files and the .md form of Anthropic's docs pages, spa/html as fallbacks, pdf maintained by hand), the coverage.ignore prefixes, and cache.updateBehavior:

Behavior	Description
`never`	Never check or update the cache
`always`	Always update without asking
`auto`	Update automatically when a new version is available (default)
`ask`	Ask when a new version is available
`askAlways`	Always ask, even if the cache is current

Related Commands

/lt-dev:plugin:check — quick validation without optimization
/lt-dev:plugin:element — create new elements

Install optimize 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.

# Optimize Marketplace Invoke the `marketplace-optimizer` skill with the arguments below and follow its execution protocol. The skill holds the procedure; `.claude/skills/marketplace-optimizer/house-rules.md` holds the decisions earlier runs settled. ## What a Run Does 1. **Cache, delta, coverage** — records the cached Claude Code version, refreshes `.claude/docs-cache/`, triages failed sources (pages split upstream are added as sources, then accepted with `--accept-shrink`), lists documentation pages the cache lacks, and cuts the changelog to the entries since the last run. 2. **Default model check** — reads which model the `opus`/`default` aliases resolve to; a changed default adds a model-specific prompt audit against that model's prompting guide. 3. **Secondary sources** — optional URLs or files, from the arguments or one prompt. 4. **Parallel analysis** — five element agents (skills, commands, agents, hooks, mcp) analyse without editing, starting from the documentation diff, with live session signals relayed to them (failed MCP servers, hooks firing on the wrong turn); then the marketplace agent checks structure, dependencies, cross-references and features. 5. **Verification** — the high-impact claims are re-checked against the cached pages before anything is shown. 6. **Findings and selection** — the numbered findings are printed first, then selected via grouped multi-select. 7. **Execution** — approved changes are applied by agents on disjoint file partitions; the coordinator handles everything outside them. Nothing is staged or committed. 8. **Final checks** — plugin validation, cross-references, cache integrity, hook and node tests, a verification pass over the diff, and updates to CLAUDE.md and the house rules. ## Usage ```bash /optimize # prompts once for secondary sources /optimize --update-cache # force a cache refresh first /optimize --skip-cache # analyse against the current cache /optimize https://example.com/guide.md ./docs/notes.md # secondary sources, no prompt ``` ## Flags | Flag | Description | |------|-------------| | `--update-cache` | Force cache update without version check | | `--skip-cache` | Skip cache update entirely | Arguments that start with `http://` or `https://` are URLs; everything else is a local file path. Empty input, "keine", "none" or "no" at the prompt skips secondary sources; sources that contradict the cache are ignored. ## Cache Configuration `.claude/docs-cache/sources.json` is the single source of truth for the cache: sources (type `md` for GitHub raw files and the `.md` form of Anthropic's docs pages, `spa`/`html` as fallbacks, `pdf` maintained by hand), the `coverage.ignore` prefixes, and `cache.updateBehavior`: | Behavior | Description | |----------|-------------| | `never` | Never check or update the cache | | `always` | Always update without asking | | `auto` | Update automatically when a new version is available (default) | | `ask` | Ask when a new version is available | | `askAlways` | Always ask, even if the cache is current | ## Related Commands - `/lt-dev:plugin:check` — quick validation without optimization - `/lt-dev:plugin:element` — create new elements

{ "prompt": "# Optimize Marketplace\n\nInvoke the `marketplace-optimizer` skill with the arguments below and follow its execution protocol. The skill\nholds the procedure; `.claude/skills/marketplace-optimizer/house-rules.md` holds the decisions earlier runs settled.\n\n## What a Run Does\n\n1. **Cache, delta, coverage** — records the cached Claude Code version, refreshes `.claude/docs-cache/`, triages\n failed sources (pages split upstream are added as sources, then accepted with `--accept-shrink`), lists\n documentation pages the cache lacks, and cuts the changelog to the entries since the last run.\n2. **Default model check** — reads which model the `opus`/`default` aliases resolve to; a changed default adds a\n model-specific prompt audit against that model's prompting guide.\n3. **Secondary sources** — optional URLs or files, from the arguments or one prompt.\n4. **Parallel analysis** — five element agents (skills, commands, agents, hooks, mcp) analyse without editing,\n starting from the documentation diff, with live session signals relayed to them (failed MCP servers, hooks firing\n on the wrong turn); then the marketplace agent checks structure, dependencies, cross-references and features.\n5. **Verification** — the high-impact claims are re-checked against the cached pages before anything is shown.\n6. **Findings and selection** — the numbered findings are printed first, then selected via grouped multi-select.\n7. **Execution** — approved changes are applied by agents on disjoint file partitions; the coordinator handles\n everything outside them. Nothing is staged or committed.\n8. **Final checks** — plugin validation, cross-references, cache integrity, hook and node tests, a verification pass\n over the diff, and updates to CLAUDE.md and the house rules.\n\n## Usage\n\n```bash\n/optimize # prompts once for secondary sources\n/optimize --update-cache # force a cache refresh first\n/optimize --skip-cache # analyse against the current cache\n/optimize https://example.com/guide.md ./docs/notes.md # secondary sources, no prompt\n```\n\n## Flags\n\n| Flag | Description |\n|------|-------------|\n| `--update-cache` | Force cache update without version check |\n| `--skip-cache` | Skip cache update entirely |\n\nArguments that start with `http://` or `https://` are URLs; everything else is a local file path. Empty input,\n\"keine\", \"none\" or \"no\" at the prompt skips secondary sources; sources that contradict the cache are ignored.\n\n## Cache Configuration\n\n`.claude/docs-cache/sources.json` is the single source of truth for the cache: sources (type `md` for GitHub raw\nfiles and the `.md` form of Anthropic's docs pages, `spa`/`html` as fallbacks, `pdf` maintained by hand), the\n`coverage.ignore` prefixes, and `cache.updateBehavior`:\n\n| Behavior | Description |\n|----------|-------------|\n| `never` | Never check or update the cache |\n| `always` | Always update without asking |\n| `auto` | Update automatically when a new version is available (default) |\n| `ask` | Ask when a new version is available |\n| `askAlways` | Always ask, even if the cache is current |\n\n## Related Commands\n\n- `/lt-dev:plugin:check` — quick validation without optimization\n- `/lt-dev:plugin:element` — create new elements", "variables": [], "notes": "Optimize this marketplace against the current Claude Code documentation and default model, with optional secondary sources Tools: Read, Write, Edit, Glob, Grep, Agent, SendMessage, Skill, AskUserQuestion, WebFetch, Bash(bun .claude/scripts/:*), Bash(claude plugin validate:*). Arguments: [--update-cache|--skip-cache] [secondary-sources...].", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/lenneTech/claude-code", "path": ".claude/commands/optimize.md", "ref": "354845d44210159b708071cc388da5f24be9fdab", "url": "https://github.com/lenneTech/claude-code/blob/354845d44210159b708071cc388da5f24be9fdab/.claude/commands/optimize.md", "key": "lenneTech/claude-code/.claude/commands/optimize.md" } } }

optimize

About

Optimize Marketplace

What a Run Does

Usage

Flags

Cache Configuration

Related Commands

Install optimize 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