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.
doc-code-sync - Skill - OpenSmartRoute
Skillv1.0.0
doc-code-sync
If a PR makes a structural change — new feature, renamed concept, changed CLI flag, new device or backend type — check whether the [OpenVMM Guide](https://openvmm.dev) (`Guide/src/`) covers that…
Instruction file imported from microsoft/openvmm (.github/instructions/doc-code-sync.instructions.md). Copyright stays with the author.
Documentation Sync
If a PR makes a structural change — new feature, renamed concept, changed CLI
flag, new device or backend type — check whether the
OpenVMM Guide (Guide/src/) covers that topic. If it
does, the PR should update the Guide or flag a follow-up.
Quick heuristics
CLI args changed in openvmm_entry → Guide/src/reference/openvmm/management/cli.md
Device crate under vm/devices/ changed → look for a matching page under Guide/src/reference/
Crate renamed or moved → grep Guide/src/ for the old name
New crate under vm/devices/ → consider whether it needs a reference page
For the full maintenance procedures, load the guide-maintenance skill.
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 slot
curl -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}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "microsoft-openvmm-doc-code-sync-instructions",
"kind": "skill",
"name": "doc-code-sync",
"description": "If a PR makes a structural change — new feature, renamed concept, changed CLI flag, new device or backend type — check whether the [OpenVMM Guide](https://openvmm.dev) (`Guide/src/`) covers that topic. If it does, the PR should update the Guide or flag a follow-up.",
"publisher": "microsoft",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"If a PR makes a structural change — new feature, renamed concept, changed CLI flag, new device or backend type — check whether the [OpenVMM Guide](https://openvmm.dev) (`Guide/src/`) covers that topic. If it does, the PR should update the Guide or flag a follow-up."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/microsoft/openvmm",
"path": ".github/instructions/doc-code-sync.instructions.md",
"ref": "f60e3d6a57ce5d0cfee48ead3bca5ce9908effba",
"url": "https://github.com/microsoft/openvmm/blob/f60e3d6a57ce5d0cfee48ead3bca5ce9908effba/.github/instructions/doc-code-sync.instructions.md",
"key": "microsoft/openvmm/.github/instructions/doc-code-sync.instructions.md"
},
"applies_to": "**/*.rs,**/Cargo.toml"
},
"instructions": "# Documentation Sync\n\nIf a PR makes a structural change — new feature, renamed concept, changed CLI\nflag, new device or backend type — check whether the\n[OpenVMM Guide](https://openvmm.dev) (`Guide/src/`) covers that topic. If it\ndoes, the PR should update the Guide or flag a follow-up.\n\n## Quick heuristics\n\n- CLI args changed in `openvmm_entry` → `Guide/src/reference/openvmm/management/cli.md`\n- Device crate under `vm/devices/` changed → look for a matching page under `Guide/src/reference/`\n- OpenHCL internals changed (`openhcl/`) → `Guide/src/reference/architecture/openhcl/`\n- Crate renamed ",
"cost": {
"context_tokens": 200
}
}
Fetch it by URL: GET /api/v1/registry/microsoft-openvmm-doc-code-sync-instructions/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.
