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.
ddot - Skill - OpenSmartRoute
Skillv1.0.0
ddot
These rules must be strictly followed by all AI agents contributing to this repository:
Imported from xbvuno/ddot (AGENTS.md). Install upstream with npx skills add xbvuno/ddot. Copyright stays with the author.
Agent Coding Rules and Guidelines
These rules must be strictly followed by all AI agents contributing to this repository:
Git Commit Notation: Always use Conventional Commits format for commits (e.g., feat(cli): ..., fix(core): ..., chore(git): ..., docs: ...). All commits must strictly follow this notation.
Clean Output: CLI tools and commands outputting formatted data (like JSON schema) must write directly and cleanly to stdout to support shell piping and redirection (e.g., > file.json), with any diagnostic logs/errors written to stderr.
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}'
Installed into a catalogue, chosen by a router
Install ddot 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.
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
xbvuno-ddot-ddot.ocm.jsonjson
{
"ocm": "1",
"id": "xbvuno-ddot-ddot",
"kind": "skill",
"name": "ddot",
"description": "These rules must be strictly followed by all AI agents contributing to this repository:",
"publisher": "xbvuno",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"These rules must be strictly followed by all AI agents contributing to this repository:"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/xbvuno/ddot",
"path": "AGENTS.md",
"ref": "484b6e81168ebfae7255f3f5261d5bbbc421c595",
"url": "https://github.com/xbvuno/ddot/blob/484b6e81168ebfae7255f3f5261d5bbbc421c595/AGENTS.md",
"key": "xbvuno/ddot/AGENTS.md"
}
},
"instructions": "# Agent Coding Rules and Guidelines\n\nThese rules must be strictly followed by all AI agents contributing to this repository:\n\n- **Git Commit Notation**: Always use Conventional Commits format for commits (e.g., `feat(cli): ...`, `fix(core): ...`, `chore(git): ...`, `docs: ...`). All commits must strictly follow this notation.\n- **Clean Output**: CLI tools and commands outputting formatted data (like JSON schema) must write directly and cleanly to `stdout` to support shell piping and redirection (e.g., `> file.json`), with any diagnostic logs/errors written to `stderr`.",
"cost": {
"context_tokens": 143
}
}
Fetch it by URL: GET /api/v1/registry/xbvuno-ddot-ddot/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.
