markdown-linter-fixer

78
C

Systematically fix linting issues in markdown files using markdownlint-cli2. This skill should be used when needing to scan, diagnose, and fix markdown formatting issues in projects with one or more .md files, with special attention to ordered list numbering (MD029) errors.

Marketplace

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install s2005/markdown-linter-fixer-skill/markdown-linter-fixer
skilz install s2005/markdown-linter-fixer-skill/markdown-linter-fixer --agent opencode
skilz install s2005/markdown-linter-fixer-skill/markdown-linter-fixer --agent codex
skilz install s2005/markdown-linter-fixer-skill/markdown-linter-fixer --agent gemini

First time? Install Skilz: pip install skilz

Works with 14 AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/s2005/markdown-linter-fixer-skill
2. Copy the agent skill directory:
cp -r markdown-linter-fixer-skill/skills/markdown-linter-fixer ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

Agentic Skill Details

Type
Non-Technical
Meta-Domain
productivity
Primary Domain
markdown
Market Score
78

Agent Skill Grade

C
Score: 78/100 Click to see breakdown

Score Breakdown

Spec Compliance
11/15
PDA Architecture
22/30
Ease of Use
20/25
Writing Style
7/10
Utility
16/20
Modifiers: +2

Areas to Improve

  • Description needs trigger phrases
  • Missing TOC for 328-line file
  • Redundant scenario section

Recommendations

  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-05

Developer Feedback

I took a look at your markdown-linter-fixer skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 78/100, solidly in C territory. This is based on Anthropic's progressive disclosure and developer experience best practices. Your strongest area is Ease of Use (20/25)—the workflow is clear and the trigger terms hit the mark. Weakest area is Spec Compliance (11/15)—mainly because your description is missing explicit trigger phrases that help people discover the skill.

What's Working Well

  • Structured workflow: Six numbered phases that actually guide someone through the process systematically. Phase 5's deep-dive on error types (MD029, MD036) is chef's kiss—those reference guides solve a real problem.
  • Smart discoverability: You've got trigger terms baked in—'markdown linting', 'markdownlint', 'MD029'. The "When to Use" section makes it clear what this skill is for.
  • Practical depth: The combination of auto-fix commands plus manual reference guides for stubborn errors shows you understand real-world usage. Not everything auto-fixes, and you're honest about that.

The Big One

Your description needs trigger phrases, and it's costing you points. Right now it reads like a feature description: "Systematically fix linting issues in markdown files using markdownlint-cli2..."

What it should do is tell people how to ask for this skill. Change it to something like: "Fix markdownlint errors in markdown files. Use when asked to 'markdown linter fixer', 'run markdown linter fixer', 'MD029 errors', or 'ordered list issues'."

This single change nets you +2 points on spec compliance and improves discoverability. Takes 30 seconds.

Other Thi...

Report Security Issue

Found a security vulnerability in this agent skill?