Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/markdown-formatting
Enforces markdown line-wrap and structure rules for clean git diffs.
Passed 16 of 21 test cases with the skill, and 14 of 21 without it.
2 fixed15 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
Reformat this long sentence into markdown prose: 'Although the deployment succeeded without returning any server errors, the secondary background worker thread crashed, causing processing delays across all queued tasks.' Ensure it wraps under 80 columns.
| Checked | Without skill | With skill |
|---|---|---|
| The line break occurs immediately following a comma boundary before column 80 | Missed | Passed |
The instructions your model reads when the skill loads.
These conventions apply to all markdown documentation generated or modified by any plugin. The goal: produce prose that creates clean, reviewable git diffs and reads well on mobile devices.
When writing or editing markdown prose:
# Heading, never setext underlines)Wrap these content types at 80 characters:
>)- or 1. )test cases passed, vs 14 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.