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.
facts - Skill - OpenSmartRoute
Skillv1.0.0
facts
Give a capable engineer a terse, jargon-free briefing on the critical facts and implications of an effort before it is built or after it is completed.
Imported from backnotprop/bro (skills/facts/SKILL.md). Install upstream with npx skills add backnotprop/bro --skill facts. Copyright stays with the author.
What are the most important facts I should know about we plan to build in this subject scope/next phase (or after if we've completed the subject scope). Instead of an exhaustive list, list only the most critical things with implications across any existing part of the system or future part - for development but also end use. Every fact must be terse, direct, and stated without jargon. Assume I am new here, but am a capable engineer: do not use sloganese or chiasmus, be clear&direct and as minimally verbose as possible (concise but coherent).
subject scope pertains to whatever has been in discussion/planning or just built in recent efforts.
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 facts 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-facts.ocm.jsonjson
{
"ocm": "1",
"id": "backnotprop-bro-facts",
"kind": "skill",
"name": "facts",
"description": "Give a capable engineer a terse, jargon-free briefing on the critical facts and implications of an effort before it is built or after it is completed. Use when the human explicitly invokes $facts, and never otherwise; do not invoke this skill automatically.",
"publisher": "backnotprop",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Give a capable engineer a terse, jargon-free briefing on the critical facts and implications of an effort before it is built or after it is completed. Use when the human explicitly invokes $facts, and never otherwise; do not invoke this skill automatically."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/backnotprop/bro",
"path": "skills/facts/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/backnotprop/bro/blob/HEAD/skills/facts/SKILL.md",
"key": "backnotprop/bro/skills/facts/SKILL.md"
}
},
"instructions": "What are the most important facts I should know about we plan to build in this subject scope/next phase (or after if we've completed the subject scope). Instead of an exhaustive list, list only the most critical things with implications across any existing part of the system or future part - for development but also end use. Every fact must be terse, direct, and stated without jargon. Assume I am new here, but am a capable engineer: do not use sloganese or chiasmus, be clear&direct and as minimally verbose as possible (concise but coherent).\n\n<meta-rule>\nThis is a skill invocation. The user is",
"cost": {
"context_tokens": 222
}
}
Fetch it by URL: GET /api/v1/registry/backnotprop-bro-facts/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.
