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.
sharpen - Skill - OpenSmartRoute
Skillv1.0.0
sharpen
Sharpen a task before starting: the expert approach, what the user is really after, and the right level of specification. Use for /sharpen.
Imported from backnotprop/bro (skills/sharpen/SKILL.md). Install upstream with npx skills add backnotprop/bro --skill sharpen. Copyright stays with the author.
Before starting, ask how a top expert would approach this task (their raw sources, their real methods, an outside check that the result is right), what the user is really after, and whether the task is over- or underspecified. Loosen constraints that don't serve the goal as readily as you add ones that do, and leave choices that are the user's to make open instead of deciding them. Fold in only what makes the work better, not bigger, but always keep one outside check that the result is right, without narrating the framing, then do the work. Don't hand back a rewritten prompt.
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://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/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 sharpen 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.
backnotprop-bro-sharpen.ocm.jsonjson
{
"ocm": "1",
"id": "backnotprop-bro-sharpen",
"kind": "skill",
"name": "sharpen",
"description": "Sharpen a task before starting: the expert approach, what the user is really after, and the right level of specification. Use for /sharpen.",
"publisher": "backnotprop",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Sharpen a task before starting: the expert approach, what the user is really after, and the right level of specification. Use for /sharpen."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/backnotprop/bro",
"path": "skills/sharpen/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/backnotprop/bro/blob/HEAD/skills/sharpen/SKILL.md",
"key": "backnotprop/bro/skills/sharpen/SKILL.md"
}
},
"instructions": "Before starting, ask how a top expert would approach this task (their raw sources, their real methods, an outside check that the result is right), what the user is really after, and whether the task is over- or underspecified. Loosen constraints that don't serve the goal as readily as you add ones that do, and leave choices that are the user's to make open instead of deciding them. Fold in only what makes the work better, not bigger, but always keep one outside check that the result is right, without narrating the framing, then do the work. Don't hand back a rewritten prompt.",
"cost": {
"context_tokens": 145
}
}
Fetch it by URL: GET /api/v1/registry/backnotprop-bro-sharpen/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.
