Markdown Block Skill

Wrap the markdown you want the user to copy in a single fenced code block tagged markdown.

Never fold the prose inside the block

Write each paragraph on ONE line. The fence makes the text copyable; it does not make it code, so the never-wrap rule in root CLAUDE.md § Writing still binds. A hard wrap at 80 columns hard-codes a width the destination does not have, and the user pastes it into a GitHub issue that autowraps at its own.

Fence rules—escape inner code blocks

Triple-backtick fences cannot nest: an inner fence prematurely closes the outer one and breaks the copy block.

Rule: the outer fence must use strictly more backticks than the longest backtick run anywhere inside the content.

Inner content contains	Outer fence to use
no backtick fences	```
``` (3 backticks)	````
```` (4 backticks)	`````

Scan the content first, find the longest backtick run, then add at least one more backtick to the outer fence.

Example

User asks: “Give me a copyable markdown snippet for a README install section.”

Respond with a 4-backtick fence because the inner content has a 3-backtick block:

# Install

Run the following:

```bash
pnpm install
```

Other escaping notes

• Tildes (~~~) are an alternate fence—apply the same “more than the longest inner run” rule if you choose them instead of backticks.
• Indented (4-space) code blocks inside the markdown need no escaping.
• Do not add commentary inside the fence. Put any explanation outside the block so the user copies clean markdown.