MarkdownLint

Format and lint Markdown documents for consistent headings, lists, and links.

5|3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/N4M3Z/forge-core --skill markdownlint-n4m3z
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MarkdownLint
Source: https://github.com/N4M3Z/forge-core/tree/main/skills/MarkdownLint
Command: npx skills add https://github.com/N4M3Z/forge-core --skill markdownlint-n4m3z

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Markdown documents often suffer from inconsistent formatting, broken lists, and poorly structured headings, which slows collaboration and degrades readability.

Core Features & Use Cases

  • Enforces consistent formatting for headings, lists, and code references to improve readability.
  • Validates and optionally checks frontmatter and schemas to ensure metadata quality.
  • Useful in documentation pipelines and note-taking workflows to clean existing content or enforce style on new documents.

Quick Start

Provide a Markdown file path and approve the suggested formatting changes after linting.

Frequently Asked Questions about MarkdownLint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent formatting for Markdown headings and lists?

Yes, the linting process validates frontmatter and checks schemas to ensure metadata quality. It specifically preserves your frontmatter and protected zones while applying formatting rules to the rest of the Markdown file.

How do I fix broken URLs and Wikilinks in my Markdown documentation?

To lint a Markdown file, you simply provide the file path to the linter. It analyzes the content, suggests formatting changes for headings and lists, and writes the corrected file after you explicitly approve the suggested modifications.

Does Markdown linting work with existing documentation pipelines?

Markdown linting does not permanently alter files without user confirmation. The linter preserves frontmatter and protected zones, suggesting corrections for backticks, URLs, and list validation, and only writes the corrected file after you approve the changes.

What is the best way to clean up inconsistent Markdown formatting?

The best way to clean up inconsistent Markdown formatting is using a linter that applies a defined set of rules for headings, lists, and code references. This enforces a consistent style and improves readability across all documentation.

Do I need to manually review every formatting change when linting Markdown?

No, you do not need to manually review every change individually because the linter suggests formatting modifications and writes the corrected file after user confirmation. This allows you to approve all applied rules for backticks, URLs, and list validation at once.