Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
checkout - Skill - OpenSmartRoute
Skillv1.0.0
checkout
Checkout a requested branch or ref in the Remotion repo, rename the current task to the associated PR title when running in Codex, then install dependencies and build.
Imported from remotion-dev/remotion (.agents/skills/checkout/SKILL.md) via skills.sh. Install upstream with npx skills add remotion-dev/remotion --skill checkout. Copyright stays with the author.
Checkout the user-provided ref. Only when running in Codex, use
gh pr view --json title --jq .title to get the associated PR title, then use
set_thread_title to rename the current Codex task to that title. If the ref has no
associated PR, leave the task title unchanged and continue. Outside Codex, skip the
PR title lookup and task rename.
Then run:
bun ibun run build
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install checkout 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.
When a provider is down or over quota the request moves on; the trace says it did.
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
remotion-dev-remotion-checkout.ocm.jsonjson
{
"ocm": "1",
"id": "remotion-dev-remotion-checkout",
"kind": "skill",
"name": "checkout",
"description": "Checkout a requested branch or ref in the Remotion repo, rename the current task to the associated PR title when running in Codex, then install dependencies and build. Use when the user asks to checkout a ref and prepare the workspace.",
"publisher": "remotion-dev",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Checkout a requested branch or ref in the Remotion repo, rename the current task to the associated PR title when running in Codex, then install dependencies and build. Use when the user asks to checkout a ref and prepare the workspace."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/remotion-dev/remotion",
"path": ".agents/skills/checkout/SKILL.md",
"ref": "HEAD",
"url": "https://www.skills.sh/remotion-dev/remotion/checkout",
"key": "remotion-dev/remotion/.agents/skills/checkout/SKILL.md"
}
},
"instructions": "Checkout the user-provided ref. Only when running in Codex, use\n`gh pr view --json title --jq .title` to get the associated PR title, then use\n`set_thread_title` to rename the current Codex task to that title. If the ref has no\nassociated PR, leave the task title unchanged and continue. Outside Codex, skip the\nPR title lookup and task rename.\n\nThen run:\n\n```bash\nbun i\nbun run build\n```",
"cost": {
"context_tokens": 97
}
}
Fetch it by URL: GET /api/v1/registry/remotion-dev-remotion-checkout/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.