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.
skill-locations - Skill - OpenSmartRoute
Skillv1.0.0
skill-locations
Document Remotion skill placement. Use when adding, moving, or editing Remotion skills to decide whether a skill belongs in .agents/skills as an internal skill or packages/skills as a public skill.
Imported from remotion-dev/remotion (.agents/skills/skill-locations/SKILL.md) via skills.sh. Install upstream with npx skills add remotion-dev/remotion --skill skill-locations. Copyright stays with the author.
Remotion Skill Locations
Place internal agent-only skills in .agents/skills/<skill-name>/SKILL.md.
Place public, redistributable skills in packages/skills/skills/<skill-name>/SKILL.md.
Expose every public skill to agents with a symlink at .agents/skills/<skill-name>.
Run bun run syncskills after adding a public skill; CI verifies the symlinks with
bun run checkskills.
When in doubt, ask whether the skill is internal or public before moving it between these roots.
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 skill-locations 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": "remotion-dev-remotion-skill-locations",
"kind": "skill",
"name": "skill-locations",
"description": "Document Remotion skill placement. Use when adding, moving, or editing Remotion skills to decide whether a skill belongs in .agents/skills as an internal skill or packages/skills as a public skill.",
"publisher": "remotion-dev",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Document Remotion skill placement. Use when adding, moving, or editing Remotion skills to decide whether a skill belongs in .agents/skills as an internal skill or packages/skills as a public skill."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/remotion-dev/remotion",
"path": ".agents/skills/skill-locations/SKILL.md",
"ref": "HEAD",
"url": "https://www.skills.sh/remotion-dev/remotion/skill-locations",
"key": "remotion-dev/remotion/.agents/skills/skill-locations/SKILL.md"
}
},
"instructions": "# Remotion Skill Locations\n\nPlace internal agent-only skills in `.agents/skills/<skill-name>/SKILL.md`.\n\nPlace public, redistributable skills in `packages/skills/skills/<skill-name>/SKILL.md`.\nExpose every public skill to agents with a symlink at `.agents/skills/<skill-name>`.\nRun `bun run syncskills` after adding a public skill; CI verifies the symlinks with\n`bun run checkskills`.\n\nWhen in doubt, ask whether the skill is internal or public before moving it between these roots.",
"cost": {
"context_tokens": 120
}
}
Fetch it by URL: GET /api/v1/registry/remotion-dev-remotion-skill-locations/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.