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.
Imported from prisma/prisma-next (skills-contrib/markdown-no-artificial-line-wraps/SKILL.md). Install upstream with npx skills add prisma/prisma-next --skill markdown-no-artificial-line-wraps. Copyright stays with the author.
Markdown: no artificial line wraps
Instructions
Prose paragraphs — Keep each paragraph as one line (or join wrapped lines into one) so the renderer can wrap in the viewer. Do not break lines mid-sentence to stay under ~80 characters.
When hard newlines are correct
Lists: one line per list item is fine; keep item text on one line unless the item is genuinely multiple paragraphs.
Headings: single line.
Fenced code blocks: preserve author intent; do not reflow code to 80 cols.
Tables, block quotes, HTML: follow normal Markdown rules; table rows may be long.
Poetry / intentional line breaks: keep explicit breaks where semantics require them.
Links and emphasis — Prefer not splitting a paragraph so that a [text](url) link is alone on a continuation line in a way that obscures reading; the whole paragraph can be one line.
Rationale — GitHub and most Markdown renderers wrap to the viewport. Fixed-width breaks in source only help in raw terminals; they harm git diff and merge conflict resolution.
Don’t
Reformat existing Markdown by hard-wrapping every paragraph to 80 columns unless the user explicitly asks for that style in that file.
Apply this rule to non-Markdown formats (e.g. .ts comment blocks) unless the user asks for Markdown-style prose there.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
Installed into a catalogue, chosen by a router
Install markdown-no-artificial-line-wraps 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.
# 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.
{
"ocm": "1",
"id": "prisma-prisma-next-markdown-no-artificial-line-wraps",
"kind": "skill",
"name": "markdown-no-artificial-line-wraps",
"description": "Writes and edits Markdown without inserting manual hard line breaks at a fixed column (e.g. 72 or 80). GitHub, docs sites, and editors soft-wrap prose; artificial breaks make diffs noisy and reflow awkward. Use when creating or editing .md files, PR bodies, ADRs, READMEs, rulecards, or any Markdown where the user cares about readable source and clean diffs — or when the user asks to avoid \"hard wrapping\" or \"80-column\" line breaks in prose.",
"publisher": "prisma",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding",
"data_analysis"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Writes and edits Markdown without inserting manual hard line breaks at a fixed column (e.g. 72 or 80). GitHub, docs sites, and editors soft-wrap prose; artificial breaks make diffs noisy and reflow awkward. Use when creating or editing .md files, PR bodies, ADRs, READMEs, rulecards, or any Markdown where the user cares about readable source and clean diffs — or when the user asks to avoid \"hard wrapping\" or \"80-column\" line breaks in prose."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/prisma/prisma-next",
"path": "skills-contrib/markdown-no-artificial-line-wraps/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/prisma/prisma-next/blob/HEAD/skills-contrib/markdown-no-artificial-line-wraps/SKILL.md",
"key": "prisma/prisma-next/skills-contrib/markdown-no-artificial-line-wraps/SKILL.md"
}
},
"instructions": "# Markdown: no artificial line wraps\n\n## Instructions\n\n1. **Prose paragraphs** — Keep each paragraph as **one line** (or join wrapped lines into one) so the renderer can wrap in the viewer. Do not break lines mid-sentence to stay under ~80 characters.\n\n2. **When hard newlines are correct**\n - **Lists**: one line per list item is fine; keep item text on one line unless the item is genuinely multiple paragraphs.\n - **Headings**: single line.\n - **Fenced code blocks**: preserve author intent; do not reflow code to 80 cols.\n - **Tables, block quotes, HTML**: follow normal Markdown rules; table rows may be long.\n - **Poetry / intentional line breaks**: keep explicit breaks where semantics require them.\n\n3. **Links and emphasis** — Prefer not splitting a paragraph so that a `[text](url)` link is alone on a continuation line in a way that obscures reading; the whole paragraph can be one line.\n\n4. **Rationale** — GitHub and most Markdown renderers wrap to the viewport. Fixed-width breaks in source only help in raw terminals; they harm `git diff` and merge conflict resolution.\n\n## Don’t\n\n- Reformat existing Markdown by hard-wrapping every paragraph to 80 columns unless the user explicitly asks for that style in that file.\n- Apply this rule to non-Markdown formats (e.g. `.ts` comment blocks) unless the user asks for Markdown-style prose there.",
"cost": {
"context_tokens": 341
}
}
Fetch it by URL: GET /api/v1/registry/prisma-prisma-next-markdown-no-artificial-line-wraps/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.