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.
unslop - Skill - OpenSmartRoute
Skillv1.0.0
unslop
Write plain, concise human-facing prose for replies, plans, docs, commits, and PRs. Skip code, identifiers, logs, tests, and inline comments.
Imported from ajaysinghpanwar2002/workflow (templates/skills/unslop/SKILL.md). Install upstream with npx skills add ajaysinghpanwar2002/workflow --skill unslop. Copyright stays with the author.
Plain writing
Preserve meaning, facts, technical terms, and uncertainty.
Say what changed, why it matters, and what happens next when relevant.
Use direct sentences and concrete details. Cut repetition, filler, generic
praise, promotional language, and conclusions that add nothing.
Use headings and lists only when they help the reader. Keep the user's tone.
Do not invent facts, sources, personal experiences, or personality.
Do not rewrite code or sacrifice necessary explanation for brevity.
Return the requested prose without narrating these editing rules.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/ajaysinghpanwar2002-workflow-unslop/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
ajaysinghpanwar2002-workflow-unslop.ocm.jsonjson
{
"ocm": "1",
"id": "ajaysinghpanwar2002-workflow-unslop",
"kind": "skill",
"name": "unslop",
"description": "Write plain, concise human-facing prose for replies, plans, docs, commits, and PRs. Skip code, identifiers, logs, tests, and inline comments.",
"publisher": "ajaysinghpanwar2002",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Write plain, concise human-facing prose for replies, plans, docs, commits, and PRs. Skip code, identifiers, logs, tests, and inline comments."
],
"primary": false,
"metadata": {
"source": {
"provider": "github",
"repository": "https://github.com/ajaysinghpanwar2002/workflow",
"path": "templates/skills/unslop/SKILL.md",
"ref": "8613a56107576750195892347aaeb1303d99e53e",
"url": "https://github.com/ajaysinghpanwar2002/workflow/blob/8613a56107576750195892347aaeb1303d99e53e/templates/skills/unslop/SKILL.md",
"key": "ajaysinghpanwar2002/workflow/templates/skills/unslop/SKILL.md"
}
},
"instructions": "# Plain writing\n\nPreserve meaning, facts, technical terms, and uncertainty.\nSay what changed, why it matters, and what happens next when relevant.\nUse direct sentences and concrete details. Cut repetition, filler, generic\npraise, promotional language, and conclusions that add nothing.\nUse headings and lists only when they help the reader. Keep the user's tone.\nDo not invent facts, sources, personal experiences, or personality.\nDo not rewrite code or sacrifice necessary explanation for brevity.\nReturn the requested prose without narrating these editing rules.",
"cost": {
"context_tokens": 141
}
}
Fetch it by URL: GET /api/v1/registry/ajaysinghpanwar2002-workflow-unslop/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.
