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.

feedback - Skill - OpenSmartRoute

Name: feedback
Author: tinyfish-io

Imported from tinyfish-io/tinyfish-cookbook (plugins/tinyfish/skills/feedback/SKILL.md). Install upstream with npx skills add tinyfish-io/tinyfish-cookbook --skill feedback. Copyright stays with the author.

TinyFish Feedback

Collect the user's feedback, structure it, preview it, then file it. Nothing leaves the machine without the user seeing the exact text first.

Collect

Ask (briefly) for: what they were trying to do, what happened instead, and what they expected. For anything setup-, auth-, or connectivity-shaped, run npx -y @tiny-fish/cli@latest doctor and offer to attach its stdout JSON verbatim — it is schema-versioned and already redaction-safe (undeclared fields stripped on parse, messages authored rather than raw). Do not add fields, summarise it, or paste config contents alongside it. On exit 2 doctor produced no JSON — say so instead of attaching an empty report.

Structure

### What I was doing
…
### What happened
…
### Expected
…
### Environment
harness + version, CLI version (if known)
### Doctor report (optional)
`tinyfish doctor` stdout, verbatim

Preview gate

Show the complete issue body to the user and ask for an explicit yes before filing. Any edit they request happens before filing.

File

Preferred: write the body and the title to files, then gh issue create --repo tinyfish-io/tinyfish-cookbook --title "$(cat "$title_file")" --body-file "$body_file" (only if gh is installed and authenticated). Both values come from the user's free-form text (the body also carries doctor's JSON), so neither may reach the shell as literal text — including in a title=… assignment, where backticks or $(…) are evaluated just the same. cat's output is not re-parsed. Never build the command as a string or run it through eval.
Fallback: open a prefilled issue URL (https://github.com/tinyfish-io/tinyfish-cookbook/issues/new?title=…&body=…). Percent-encode both values — an unencoded # truncates the body and & splits it into junk parameters. URL length limits truncate long bodies anyway — if the body was truncated, tell the user and show the full text so they can paste the remainder.

This repo is public — remind the user of that in the preview if the report contains anything they typed free-form.

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

{ "ocm": "1", "id": "tinyfish-io-tinyfish-cookbook-feedback", "kind": "skill", "name": "feedback", "description": "File structured feedback about TinyFish — bug reports, confusing setup steps, missing features, or a doctor diagnostic report. Creates a GitHub issue on tinyfish-io/tinyfish-cookbook with the user's approval; nothing is sent without an explicit preview.", "publisher": "tinyfish-io", "version": "1.0.0", "capabilities": { "domains": [ "coding", "math" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "File structured feedback about TinyFish — bug reports, confusing setup steps, missing features, or a doctor diagnostic report. Creates a GitHub issue on tinyfish-io/tinyfish-cookbook with the user's approval; nothing is sent without an explicit preview." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/tinyfish-io/tinyfish-cookbook", "path": "plugins/tinyfish/skills/feedback/SKILL.md", "ref": "HEAD", "url": "https://github.com/tinyfish-io/tinyfish-cookbook/blob/HEAD/plugins/tinyfish/skills/feedback/SKILL.md", "key": "tinyfish-io/tinyfish-cookbook/plugins/tinyfish/skills/feedback/SKILL.md" } }, "instructions": "# TinyFish Feedback\n\nCollect the user's feedback, structure it, preview it, then file it. Nothing\nleaves the machine without the user seeing the exact text first.\n\n## Collect\n\nAsk (briefly) for: what they were trying to do, what happened instead, and\nwhat they expected. For anything setup-, auth-, or connectivity-shaped, run\n`npx -y @tiny-fish/cli@latest doctor` and offer to attach its stdout JSON\nverbatim — it is schema-versioned and already redaction-safe (undeclared\nfields stripped on parse, messages authored rather than raw). Do not add\nfields, summarise it, or paste config contents alongs", "cost": { "context_tokens": 526 } }

feedback

About

TinyFish Feedback

Collect

Structure

Preview gate

File

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