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.
technical-communication - Skill - OpenSmartRoute
Skillv1.0.0
technical-communication
Write clear technical communications including emails, reports, and status updates. Use when communicating technical information to stakeholders or team members.
Imported from nuday-ai/nuday-plugins (plugins/nuday-complete/skills/technical-communication/SKILL.md). Install upstream with npx skills add nuday-ai/nuday-plugins --skill technical-communication. Copyright stays with the author.
Technical Communication
Lead with what the reader most needs, usually the conclusion, decision or ask, then the
supporting detail. Match the technical depth to the audience and define terms they may
not know.
Use the structure that fits the document:
Status update: summary, completed, in progress, blockers, next steps
Technical proposal: problem, proposed solution, alternatives considered,
trade-offs, implementation plan, how success will be measured
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}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "nuday-ai-nuday-plugins-technical-communication",
"kind": "skill",
"name": "technical-communication",
"description": "Write clear technical communications including emails, reports, and status updates. Use when communicating technical information to stakeholders or team members.",
"publisher": "nuday-ai",
"version": "1.0.0",
"capabilities": {
"domains": [
"observability"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Write clear technical communications including emails, reports, and status updates. Use when communicating technical information to stakeholders or team members."
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/nuday-ai/nuday-plugins",
"path": "plugins/nuday-complete/skills/technical-communication/SKILL.md",
"ref": "7c3e1fb14c7ec55eb9ecb4a68f2a1fdcd1e02309",
"url": "https://github.com/nuday-ai/nuday-plugins/blob/7c3e1fb14c7ec55eb9ecb4a68f2a1fdcd1e02309/plugins/nuday-complete/skills/technical-communication/SKILL.md",
"key": "nuday-ai/nuday-plugins/plugins/nuday-complete/skills/technical-communication/SKILL.md"
}
},
"instructions": "# Technical Communication\n\nLead with what the reader most needs, usually the conclusion, decision or ask, then the\nsupporting detail. Match the technical depth to the audience and define terms they may\nnot know.\n\nUse the structure that fits the document:\n- **Status update**: summary, completed, in progress, blockers, next steps\n- **Technical proposal**: problem, proposed solution, alternatives considered,\n trade-offs, implementation plan, how success will be measured\n- **Incident report**: impact summary, timeline, root cause, resolution, lessons\n learned, action items",
"cost": {
"context_tokens": 144
}
}
Fetch it by URL: GET /api/v1/registry/nuday-ai-nuday-plugins-technical-communication/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.
