Markdown No Artificial Line Wraps Agent Skill
>- 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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/prisma/prisma --skill markdown-no-artificial-line-wrapsThe instruction itself
3 sections, as written by the authorMarkdown: 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
textlink 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 diffand 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.
.tscomment blocks) unless the user asks for Markdown-style prose there.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take prisma/markdown-no-artificial-line-wraps from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.