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.
share-github-pr - Skill - OpenSmartRoute
Skillv1.0.0
share-github-pr
Use this plugin when the user wants to package an accepted plugin or artifact as a GitHub pull request for OpenDesign or another target repository.
Imported from nexu-io/open-design (plugins/spec/examples/share-github-pr/SKILL.md). Install upstream with npx skills add nexu-io/open-design --skill share-github-pr. Copyright stays with the author (MIT).
Share GitHub PR
Workflow
Confirm the target repository, branch, and PR intent before making externally visible changes.
Read the changed artifact or plugin folder and create a concise PR summary.
Run available validation commands.
Stage only relevant files.
Open or prepare the PR and report the URL or exact next command.
Output Contract
Produce pr-summary.md and a PR URL or prepared branch summary.
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 share-github-pr 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.
nexu-io-open-design-share-github-pr.ocm.jsonjson
{
"ocm": "1",
"id": "nexu-io-open-design-share-github-pr",
"kind": "skill",
"name": "share-github-pr",
"description": "Use this plugin when the user wants to package an accepted plugin or artifact as a GitHub pull request for OpenDesign or another target repository.",
"publisher": "nexu-io",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding",
"legal"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use this plugin when the user wants to package an accepted plugin or artifact as a GitHub pull request for OpenDesign or another target repository."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/nexu-io/open-design",
"path": "plugins/spec/examples/share-github-pr/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/nexu-io/open-design/blob/HEAD/plugins/spec/examples/share-github-pr/SKILL.md",
"key": "nexu-io/open-design/plugins/spec/examples/share-github-pr/SKILL.md"
},
"license": "MIT"
},
"instructions": "# Share GitHub PR\n\n## Workflow\n\n1. Confirm the target repository, branch, and PR intent before making externally visible changes.\n2. Read the changed artifact or plugin folder and create a concise PR summary.\n3. Run available validation commands.\n4. Stage only relevant files.\n5. Open or prepare the PR and report the URL or exact next command.\n\n## Output Contract\n\nProduce `pr-summary.md` and a PR URL or prepared branch summary.",
"cost": {
"context_tokens": 107
}
}
Fetch it by URL: GET /api/v1/registry/nexu-io-open-design-share-github-pr/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.
