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.
card-twitter - Skill - OpenSmartRoute
Skillv1.0.0
card-twitter
Twitter quote or data card designed to pair with a post.
Imported from nexu-io/open-design (skills/card-twitter/SKILL.md) via skills.sh. Install upstream with npx skills add nexu-io/open-design --skill card-twitter. Copyright stays with the author.
【模板: Twitter 分享卡】
容器 w-[1600px] h-[900px], 暗色 / 亮色二选一根据内容情绪。
中央一句 hero 金句 (text-6xl, font-semibold, 限 2-3 行)。
下方作者署名 + 头像占位 + handle。
左上角小标签 (类型: "Insight" / "Data" / "Quote")。
右下角品牌水印。
整张卡片有微妙的纹理 (grid 网格 / noise / dot pattern)。
截图后可直接配推文发出, 视觉简洁有力。
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}'
Installed into a catalogue, chosen by a router
Install card-twitter 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.