Guide · Agent skill
How to use the Markdown without hard line wraps agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
This guide explains what the markdown-no-artificial-line-wraps agent skill does, how to install it, and how to ask for its behaviour in plain language. It is for people who keep READMEs, ADRs or PR descriptions in Git and have noticed an agent breaking prose lines at a fixed width. By the end you will know how to install the skill, trigger it, and check its output.
Markdown without hard line wrapsprisma/orm · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Get the skill ZIP from the page you are reading.
- 2Unzip into the right folder. Extract it into ~/.claude/skills/ for personal use, or into the project's .claude/skills/ folder for one project.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP.
- 4Ask in plain language. Request prose without hard wrapping, such as asking for a README or PR description with unwrapped paragraphs.
- 5Review the diff. Check that paragraphs are single lines while code blocks and tables are unchanged.
What the skill makes the agent do
When this skill is active, the agent writes and edits Markdown files without inserting manual line breaks at a fixed column such as 72 or 80 characters. Each prose paragraph stays on one line, and GitHub, docs sites and editors wrap it to fit the screen.
The skill leaves code blocks, headings, tables, block quotes and intentional line breaks alone. Its source also says the agent should not reflow existing Markdown unless the user asks for that style in that file.
- Prose paragraphs are kept as one line.
- Fenced code blocks are not reflowed.
- Headings are single lines.
- Tables and block quotes follow normal Markdown rules.
- Poetry or other intentional line breaks are kept.
Install the skill
Download the ZIP for this skill from the page you are reading. The skill is a folder containing a SKILL.md file.
For a personal install, unzip it into ~/.claude/skills/. For a single project, unzip it into the project's .claude/skills/ folder.
In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
Trigger the skill with natural requests
The skill's description tells the agent when to use it: when creating or editing .md files, PR bodies, ADRs, READMEs or rulecards, or when you ask to avoid hard wrapping or 80-column line breaks in prose. You do not need a special command.
Ask in ordinary words, for example: "Update the README and keep the paragraphs unwrapped." or "Write the ADR for this decision without hard wrapping at 80 columns."
- "Write the PR description for this change. Don't hard-wrap the prose."
- "Edit docs/adr/0004.md and keep each paragraph on one line."
- "Avoid 80-column line breaks in the new section of the README."
Check the output and what it changes
After the agent edits a file, open the diff. Prose paragraphs should be single long lines, while code blocks, headings and tables should look as they did before. Because the skill does not reformat existing files unless asked, unrelated lines in the diff should not change.
If a paragraph was already wrapped by an earlier edit, the skill's instructions say to join its lines into one, so the renderer can wrap it.
What the skill needs and its safety notes
The listing states that this skill requires nothing and does not run scripts. It also does not use the network. The package contains only SKILL.md.
Because it runs no scripts and makes no network calls, it changes only how the agent formats Markdown text.
- Requires: nothing listed.
- Runs scripts: no.
- Uses network: no.
- Files: SKILL.md.
When this skill is the wrong choice
Do not use this skill if your project enforces a fixed column width for Markdown source through a linter or style guide, because the two rules would conflict.
Also avoid it where raw Markdown is read in a terminal without soft wrapping, since long lines become hard to read there.
- Projects with a fixed-width Markdown linter or style guide.
- Workflows where raw source is read in a terminal without soft wrapping.
What people use it for
- Writing pull request descriptions that read cleanly on GitHub.
- Editing architecture decision records (ADRs) kept in Git.
- Updating READMEs and docs where diffs should show only real content changes.
- Keeping prose in rulecards or other Markdown files on one line per paragraph.
Frequently asked questions
How do I install the markdown-no-artificial-line-wraps skill?
Download the ZIP from the page, then unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps, you can upload the ZIP under Settings → Capabilities → Skills.
Does this skill require anything else to run?
The listing says it requires nothing and does not run scripts or use the network. The package contains only a SKILL.md file.
Is the markdown-no-artificial-line-wraps skill free?
The skill is published under the Apache-2.0 licence. The source does not mention pricing, so check the listing for any other terms.
Will the skill reformat my existing Markdown files?
No, not unless you ask. The skill says the agent should not reformat existing Markdown by hard-wrapping every paragraph unless the user explicitly requests that style for that file.
Why does my agent keep wrapping lines at 80 characters?
Without this skill, the agent may insert manual breaks at a fixed width. Installing the skill and asking for unwrapped prose tells the agent to keep each paragraph on one line.
Does this skill conflict with a Markdown linter?
It can. If your project enforces a fixed column width for Markdown source through a linter or style guide, this skill would conflict with that rule, so do not use it in that case.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits developers and teams who keep Markdown in Git and review it on GitHub or docs sites, and who want clean diffs without fixed-width breaks. It is a poor fit for projects that enforce a fixed column width through a linter or style guide, or for workflows that read raw Markdown in a terminal without soft wrapping.
Download the skill