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.
vendored-example-skill - Skill - OpenSmartRoute
Skillv1.0.0
vendored-example-skill
An upstream skill, vendored verbatim — a worked example of the migration spec's vendored-skill carve-out: this file itself is stamped (`vendored: true`, `origin:`) like any other `SKILL.md`, but every
Imported from yes-404/gi-pricing-plan (tests/fixtures/docs-migration/.claude/skills/vendored-example-skill/SKILL.md). Install upstream with npx skills add yes-404/gi-pricing-plan --skill vendored-example-skill. Copyright stays with the author.
vendored-example-skill
An upstream skill, vendored verbatim — a worked example of the migration spec's
vendored-skill carve-out: this file itself is stamped (vendored: true, origin:) like
any other SKILL.md, but everything beneath this directory (LICENSE,
references/extra.md) is exempt from stamping, citation rewrite and shape checks,
because this directory's name is declared as vendored (tests/test_doc_id_migrate.py's
own fixture setup adds it to _VENDORED_SKILLS for the duration of each test in that
module — Ruling 69's declared-constant mechanism, not detection by this directory's
LICENSE file, which is carried only to prove a vendored skill's own licence text
survives byte-for-byte).
Cites FR-EX-1 here, in the one file that does get touched, so a test can tell the
citation-rewrite pass apart from the vendored exemption: this occurrence must rewrite,
the one in references/extra.md (beneath the vendored boundary) must not.
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 vendored-example-skill 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.
{
"ocm": "1",
"id": "yes-404-gi-pricing-plan-vendored-example-skill",
"kind": "skill",
"name": "vendored-example-skill",
"description": "An upstream skill, vendored verbatim — a worked example of the migration spec's vendored-skill carve-out: this file itself is stamped (`vendored: true`, `origin:`) like any other `SKILL.md`, but everything beneath this directory (`LICENSE`, `references/extra.md`) is exempt from stamping, citation rewrite and shape checks, because this directory's name is declared as vendored (`tests/test_doc_id_migrate.py`'s own fixture setup adds it to `_VENDORED_SKILLS` for the duration of each test in that module — Ruling 69's declared-constant mechanism, not detection by this directory's `LICENSE` file, which is carried only to prove a vendored skill's own licence text survives byte-for-byte).",
"publisher": "yes-404",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding",
"math"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"An upstream skill, vendored verbatim — a worked example of the migration spec's vendored-skill carve-out: this file itself is stamped (`vendored: true`, `origin:`) like any other `SKILL.md`, but everything beneath this directory (`LICENSE`, `references/extra.md`) is exempt from stamping, citation rewrite and shape checks, because this directory's name is declared as vendored (`tests/test_doc_id_migrate.py`'s own fixture setup adds it to `_VENDORED_SKILLS` for the duration of each test in that module — Ruling 69's declared-constant mechanism, not detection by this directory's `LICENSE` file, which is carried only to prove a vendored skill's own licence text survives byte-for-byte)."
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/yes-404/gi-pricing-plan",
"path": "tests/fixtures/docs-migration/.claude/skills/vendored-example-skill/SKILL.md",
"ref": "cfbc0390c119736a23bdd18b98ff7f4fd595be5f",
"url": "https://github.com/yes-404/gi-pricing-plan/blob/cfbc0390c119736a23bdd18b98ff7f4fd595be5f/tests/fixtures/docs-migration/.claude/skills/vendored-example-skill/SKILL.md",
"key": "yes-404/gi-pricing-plan/tests/fixtures/docs-migration/.claude/skills/vendored-example-skill/SKILL.md"
}
},
"instructions": "# vendored-example-skill\n\nAn upstream skill, vendored verbatim — a worked example of the migration spec's\nvendored-skill carve-out: this file itself is stamped (`vendored: true`, `origin:`) like\nany other `SKILL.md`, but everything beneath this directory (`LICENSE`,\n`references/extra.md`) is exempt from stamping, citation rewrite and shape checks,\nbecause this directory's name is declared as vendored (`tests/test_doc_id_migrate.py`'s\nown fixture setup adds it to `_VENDORED_SKILLS` for the duration of each test in that\nmodule — Ruling 69's declared-constant mechanism, not detection by this dire",
"cost": {
"context_tokens": 241
}
}
Fetch it by URL: GET /api/v1/registry/yes-404-gi-pricing-plan-vendored-example-skill/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.
