Cursor
Skill
verifying-markdown-formatting
Verify that a Markdown file has correct formatting — headings, lists, links, code blocks, spacing, and consistent style.
Virus-scanned
Reviewed automatically before listing.
Download
spencerpauly-awesome-cursor-skills-resources_verifying-markdown-formatting-99cd265.zip · 1 KB
Install
skills CLI
npx skills add https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/verifying-markdown-formatting
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install spencerpauly-awesome-cursor-skills@llmmart
Git
git clone https://github.com/spencerpauly/awesome-cursor-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole spencerpauly/awesome-cursor-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Verifying Markdown Formatting
Check a Markdown file for formatting issues and fix them.
What to Check
Structure
- Exactly one
# H1heading at the top of the file - Headings increment by one level (no jumping from
##to####) - Blank line before and after every heading
- Blank line before and after every code block, list, and blockquote
- File ends with a single trailing newline
Lists
- Consistent marker style within each list (
-not mixed with*or+) - Nested items indented with 2 or 4 spaces (consistent throughout)
- Blank line before the first item in a top-level list
- No blank lines between items in a tight list (or all items separated — pick one)
Links & Images
- All links have non-empty display text:
[text](url)not[](url) - No bare URLs outside of code blocks — wrap in
<url>or[text](url) - Reference-style links have matching definitions
- Image alt text is present:
not
Code Blocks
- Fenced code blocks use triple backticks, not tildes
- Language identifier is present on every fenced block (
```python,```bash, etc.) - Inline code uses single backticks for short references
- No indented code blocks (use fenced instead for clarity)
Formatting
- Bold uses
**text**not__text__ - Italic uses
*text*not_text_ - No trailing whitespace on any line
- Lines under 120 characters where practical (prose, not tables)
- Consistent use of ATX-style headings (
# Heading, not underline style)
Tables
- Header row has separator row with
---in each column - Cell content is trimmed (no excessive padding)
- Column alignment markers (
:---,:---:,---:) used consistently if present
Horizontal Rules
- Use
---on its own line with blank lines above and below - Consistent style (don't mix
---,***,___)
Workflow
- Read the target Markdown file
- Walk through each check above
- Fix any issues found using exact string replacements
- Re-read the file to confirm all fixes applied cleanly
- Report what was fixed and what was already correct
Notes
- This skill is formatting-only — it does not validate content accuracy, broken links, or spelling
- Preserve the author's intended structure; don't reorganize sections
- When fixing list markers, match whatever style the file already uses most
Files (awesome-cursor-skills)
-
SKILL.md 2.6 KB
--- name: verifying-markdown-formatting description: Verify that a Markdown file has correct formatting — headings, lists, links, code blocks, spacing, and consistent style. user-invocable: true --- # Verifying Markdown Formatting Check a Markdown file for formatting issues and fix them. ## What to Check ### Structure - [ ] Exactly one `# H1` heading at the top of the file - [ ] Headings increment by one level (no jumping from `##` to `####`) - [ ] Blank line before and after every heading - [ ] Blank line before and after every code block, list, and blockquote - [ ] File ends with a single trailing newline ### Lists - [ ] Consistent marker style within each list (`-` not mixed with `*` or `+`) - [ ] Nested items indented with 2 or 4 spaces (consistent throughout) - [ ] Blank line before the first item in a top-level list - [ ] No blank lines between items in a tight list (or all items separated — pick one) ### Links & Images - [ ] All links have non-empty display text: `[text](url)` not `[](url)` - [ ] No bare URLs outside of code blocks — wrap in `<url>` or `[text](url)` - [ ] Reference-style links have matching definitions - [ ] Image alt text is present: `` not `` ### Code Blocks - [ ] Fenced code blocks use triple backticks, not tildes - [ ] Language identifier is present on every fenced block (` ```python `, ` ```bash `, etc.) - [ ] Inline code uses single backticks for short references - [ ] No indented code blocks (use fenced instead for clarity) ### Formatting - [ ] Bold uses `**text**` not `__text__` - [ ] Italic uses `*text*` not `_text_` - [ ] No trailing whitespace on any line - [ ] Lines under 120 characters where practical (prose, not tables) - [ ] Consistent use of ATX-style headings (`# Heading`, not underline style) ### Tables - [ ] Header row has separator row with `---` in each column - [ ] Cell content is trimmed (no excessive padding) - [ ] Column alignment markers (`:---`, `:---:`, `---:`) used consistently if present ### Horizontal Rules - [ ] Use `---` on its own line with blank lines above and below - [ ] Consistent style (don't mix `---`, `***`, `___`) ## Workflow 1. Read the target Markdown file 2. Walk through each check above 3. Fix any issues found using exact string replacements 4. Re-read the file to confirm all fixes applied cleanly 5. Report what was fixed and what was already correct ## Notes - This skill is formatting-only — it does not validate content accuracy, broken links, or spelling - Preserve the author's intended structure; don't reorganize sections - When fixing list markers, match whatever style the file already uses most
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.