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.
novasaga-prose-editor - Skill - OpenSmartRoute
Skillv1.0.0
novasaga-prose-editor
Review or refine NovaSaga prose while preserving authorial intent and avoiding unrequested draft rewrites.
Imported from Wolfrine/NovaSaga (skills/prose-editor/SKILL.md). Install upstream with npx skills add Wolfrine/NovaSaga --skill prose-editor. Copyright stays with the author.
NovaSaga Prose Editor
Use this skill only when the user explicitly asks for prose review, line editing, style tightening, or draft revision.
Boundaries
Do not rewrite drafts/ unless asked.
Do not convert wiki notes into prose chapters.
Preserve the user's narrative intent, point of view, and emotional direction.
Prefer comments, options, or focused edits over sweeping rewrites.
Flag continuity issues against wiki/ and meta/CanonPolicy.md, but do not silently change canon to fit prose.
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 novasaga-prose-editor 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.
wolfrine-novasaga-prose-editor.ocm.jsonjson
{
"ocm": "1",
"id": "wolfrine-novasaga-prose-editor",
"kind": "skill",
"name": "novasaga-prose-editor",
"description": "Review or refine NovaSaga prose while preserving authorial intent and avoiding unrequested draft rewrites.",
"publisher": "Wolfrine",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Review or refine NovaSaga prose while preserving authorial intent and avoiding unrequested draft rewrites."
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/Wolfrine/NovaSaga",
"path": "skills/prose-editor/SKILL.md",
"ref": "d188825bcee26dbd1000380786bd668aaa176808",
"url": "https://github.com/Wolfrine/NovaSaga/blob/d188825bcee26dbd1000380786bd668aaa176808/skills/prose-editor/SKILL.md",
"key": "Wolfrine/NovaSaga/skills/prose-editor/SKILL.md"
}
},
"instructions": "# NovaSaga Prose Editor\n\nUse this skill only when the user explicitly asks for prose review, line editing, style tightening, or draft revision.\n\n## Boundaries\n\n- Do not rewrite `drafts/` unless asked.\n- Do not convert wiki notes into prose chapters.\n- Preserve the user's narrative intent, point of view, and emotional direction.\n- Prefer comments, options, or focused edits over sweeping rewrites.\n- Flag continuity issues against `wiki/` and `meta/CanonPolicy.md`, but do not silently change canon to fit prose.",
"cost": {
"context_tokens": 128
}
}
Fetch it by URL: GET /api/v1/registry/wolfrine-novasaga-prose-editor/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.