markdown-formatter

Format and lint Markdown with markdownlint, admonitions, and KaTeX math.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/lucasgaldinos/my-skills --skill markdown-formatter-lucasgaldinos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: markdown-formatter
Source: https://github.com/lucasgaldinos/my-skills/tree/main/skills/markdown-formatter
Command: npx skills add https://github.com/lucasgaldinos/my-skills --skill markdown-formatter-lucasgaldinos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Markdown outputs often suffer from drift in formatting, inconsistent linting, and inconsistent rendering of math and references. This Skill standardizes markdown generation by applying formatting rules, enforcing markdownlint compliance, GitHub-style admonitions, reference labels, footnotes, code block citations, and KaTeX formatting.

Core Features & Use Cases

  • Enforces markdownlint-compliant formatting, admonitions, and reference labeling across new and updated Markdown files.
  • Ensures consistent footnotes, code block source citations, and KaTeX math environments in documentation.
  • Use Case: before publishing a README or documentation page, run this skill to auto-correct style, ensure citations and math render properly, and produce diff-friendly Markdown.

Quick Start

Activate the Markdown Formatter on your markdown outputs to automatically apply styling, linting, and KaTeX formatting rules.

Frequently Asked Questions about markdown-formatter

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

FAQPage Schema
How do I enforce markdownlint compliance and fix formatting in README files?

To enforce markdownlint compliance in README files, apply automated formatting rules that standardize heading structure, list indentation, and spacing to produce clean, diff-friendly Markdown output.

What is the best way to format KaTeX math environments and footnotes in markdown documentation?

Formatting KaTeX math environments and footnotes in markdown involves applying specialized linting rules that ensure proper syntax rendering and consistent reference labeling across documentation files.

Does this markdown formatting approach support GitHub-style admonitions and reference labels?

Yes, this markdown formatting approach supports GitHub-style admonitions and reference labels by enforcing consistent syntax for callout blocks and citation linking during the text generation process.

How do I auto-correct markdown style and ensure code block citations before publishing?

Auto-correcting markdown style before publishing requires running a formatting pass that applies linting rules, normalizes code block source citations, and outputs standardized, portable markdown.

Can I use this markdown linter on existing documentation without breaking frontmatter metadata?

You can use this markdown linter on existing documentation because it reads frontmatter metadata to guide activation and behavior, ensuring formatting changes align with existing document structures.