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.
quintet - Skill - OpenSmartRoute
Skillv1.0.0
quintet
Respond to users in the language they use in their messages * Comments in source code are generally not required. When explanation is necessary, write comments in English. * Do not respond based on sp
Imported from yoshinorin/quintet (AGENTS.md). Install upstream with npx skills add yoshinorin/quintet. Copyright stays with the author.
Respond to users in the language they use in their messages
Comments in source code are generally not required. When explanation is necessary, write comments in English.
Do not respond based on speculation or assumptions. If you must speculate or assume, declare it explicitly.
Keep explanations as concise as possible.
When writing implementations or tests, ensure there are no duplicates in the content.
When installing libraries or dependencies, explain which libraries or dependencies will be installed before implementation.
When changes or implementations are expected to be substantial, explain what changes will be made beforehand.
When requirements are ambiguous, ask clarifying questions before implementation
When conducting research, provide primary sources when available.
Never reference, modify, or write to directories above the current directory where the agent is running.
When creating commit messages, write them in English as a single sentence.
Use Conventional Commits format for commit messages (e.g., feat:, fix:, refactor:, docs:, chore:).
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 quintet 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.
yoshinorin-quintet-quintet.ocm.jsonjson
{
"ocm": "1",
"id": "yoshinorin-quintet-quintet",
"kind": "skill",
"name": "quintet",
"description": "Respond to users in the language they use in their messages * Comments in source code are generally not required. When explanation is necessary, write comments in English. * Do not respond based on speculation or assumptions. If you must speculate or assume, declare it explicitly. * Keep explanations as concise as possible. * When writing implementations or tests, ensure there are no duplicates in the content. * When installing libraries or dependencies, explain which libraries or dependencies will be installed before implementation. * When changes or implementations are expected to be substantial, explain what changes will be made beforehand. * When requirements are ambiguous, ask clarifying questions before implementation * When conducting research, provide primary sources when available. * Never reference, modify, or write to directories above the current directory where the agent is running. * When creating commit messages, write them in English as a single sentence. * Use Conventional Commits format for ",
"publisher": "yoshinorin",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Respond to users in the language they use in their messages * Comments in source code are generally not required. When explanation is necessary, write comments in English. * Do not respond based on speculation or assumptions. If you must speculate or assume, declare it explicitly. * Keep explanations as concise as possible. * When writing implementations or tests, ensure there are no duplicates in the content. * When installing libraries or dependencies, explain which libraries or dependencies will be installed before implementation. * When changes or implementations are expected to be substantial, explain what changes will be made beforehand. * When requirements are ambiguous, ask clarifying questions before implementation * When conducting research, provide primary sources when available. * Never reference, modify, or write to directories above the current directory where the agent is running. * When creating commit messages, write them in English as a single sentence. * Use Conventional Commits format for "
],
"primary": false,
"metadata": {
"source": {
"provider": "github-agents",
"repository": "https://github.com/yoshinorin/quintet",
"path": "AGENTS.md",
"ref": "9275485ce9f9babc63ba5b6ef213c6f9b1207e9d",
"url": "https://github.com/yoshinorin/quintet/blob/9275485ce9f9babc63ba5b6ef213c6f9b1207e9d/AGENTS.md",
"key": "yoshinorin/quintet/AGENTS.md"
}
},
"instructions": "* Respond to users in the language they use in their messages\n* Comments in source code are generally not required. When explanation is necessary, write comments in English.\n* Do not respond based on speculation or assumptions. If you must speculate or assume, declare it explicitly.\n* Keep explanations as concise as possible.\n* When writing implementations or tests, ensure there are no duplicates in the content.\n* When installing libraries or dependencies, explain which libraries or dependencies will be installed before implementation.\n* When changes or implementations are expected to be subst",
"cost": {
"context_tokens": 272
}
}
Fetch it by URL: GET /api/v1/registry/yoshinorin-quintet-quintet/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.
