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.
product-help - Skill - OpenSmartRoute
Skillv1.0.0
product-help
OpenChatCut product knowledge — UI layout, editor features, and how generation providers are configured.
Imported from 0xsline/openchatcut (src/agent/skills/product-help/SKILL.md). Install upstream with npx skills add 0xsline/openchatcut --skill product-help. Copyright stays with the author.
OpenChatCut Product Help
Product knowledge base for answering user questions and guiding GUI operations.
When to Use
User asks about the product, a feature, or how something works
User asks how to configure AI providers / API keys
User needs to perform a GUI action that the agent cannot do directly
A task fails and you need to guide the user through manual steps as a fallback
Reference Files
Read the relevant file on demand — do NOT read all files at once.
Question about
File
Product UI, layout, panels, buttons, features
references/ui-and-features.md
API keys, providers, which features need a key
references/providers-and-keys.md
What generation models/tools are wired
references/generation-capabilities.md
Official generation API documentation
references/generation-official-docs.md
Guidelines
Try to do it first. If the task is something you can handle (adding captions, changing aspect ratio, etc.), do it. Only guide GUI operations as a fallback.
Use visible UI names. When guiding manual operations, give clear numbered steps with labels and panel locations that are confirmed in the references. If the user says they cannot find an entry, re-anchor from major visible regions such as the AI panel, top bar, asset/library panels, and timeline.
Missing keys. If a provider is not configured, say which key is missing and how to set it in Settings.
Generation confirmations. Some generation tools may show an in-app confirmation (skill guard / proposal) before running.
Provider costs. If the user asks about cloud cost, point them at their provider dashboard; do not invent rates.
Installed into a catalogue, chosen by a router
Install product-help 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.
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://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
0xsline-openchatcut-product-help.ocm.jsonjson
{
"ocm": "1",
"id": "0xsline-openchatcut-product-help",
"kind": "skill",
"name": "product-help",
"description": "OpenChatCut product knowledge — UI layout, editor features, and how generation providers are configured. Use when the user asks about the product interface, how to use a feature, where to find something, or needs GUI guidance for something the agent cannot do directly. Also use as fallback when a task fails and the user needs to complete it manually in the UI. NOT for live project-state queries (\"where are my folders?\", \"what's on my timeline?\", \"where is clip X?\") — those are answered by `read_project`, not by this skill.",
"publisher": "0xsline",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding",
"data_analysis"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"OpenChatCut product knowledge — UI layout, editor features, and how generation providers are configured. Use when the user asks about the product interface, how to use a feature, where to find something, or needs GUI guidance for something the agent cannot do directly. Also use as fallback when a task fails and the user needs to complete it manually in the UI. NOT for live project-state queries (\"where are my folders?\", \"what's on my timeline?\", \"where is clip X?\") — those are answered by `read_project`, not by this skill."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/0xsline/openchatcut",
"path": "src/agent/skills/product-help/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/0xsline/openchatcut/blob/HEAD/src/agent/skills/product-help/SKILL.md",
"key": "0xsline/openchatcut/src/agent/skills/product-help/SKILL.md"
}
},
"instructions": "# OpenChatCut Product Help\n\nProduct knowledge base for answering user questions and guiding GUI operations.\n\n## When to Use\n\n- User asks about the product, a feature, or how something works\n- User asks how to configure AI providers / API keys\n- User needs to perform a GUI action that the agent cannot do directly\n- A task fails and you need to guide the user through manual steps as a fallback\n\n## Reference Files\n\nRead the relevant file on demand — do NOT read all files at once.\n\n| Question about | File |\n| --- | --- |\n| Product UI, layout, panels, buttons, features | `references/ui-and-features.md` |\n| API keys, providers, which features need a key | `references/providers-and-keys.md` |\n| What generation models/tools are wired | `references/generation-capabilities.md` |\n| Official generation API documentation | `references/generation-official-docs.md` |\n\n## Guidelines\n\n1. **Try to do it first.** If the task is something you can handle (adding captions, changing aspect ratio, etc.), do it. Only guide GUI operations as a fallback.\n2. **Use visible UI names.** When guiding manual operations, give clear numbered steps with labels and panel locations that are confirmed in the references. If the user says they cannot find an entry, re-anchor from major visible regions such as the AI panel, top bar, asset/library panels, and timeline.\n3. **Missing keys.** If a provider is not configured, say which key is missing and how to set it in Settings.\n4. **Generation confirmations.** Some generation tools may show an in-app confirmation (skill guard / proposal) before running.\n5. **Provider costs.** If the user asks about cloud cost, point them at their provider dashboard; do not invent rates.",
"cost": {
"context_tokens": 426
}
}
Fetch it by URL: GET /api/v1/registry/0xsline-openchatcut-product-help/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.