markdown

> Markdown linting and automated fixing using markdownlint-cli2. Use when Claude needs to: (1) Check markdown files for style issues, (2) Fix markdown formatting problems, (3) Ensure markdown follows best practices, (4) Validate markdown documents, or (5) Apply consistent markdown styling

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 →

Claude Code (CLI) Fast

skilz install 46ki75/skills/markdown

OpenCode (CLI) Fast

skilz install 46ki75/skills/markdown --agent opencode

OpenAI Codex (CLI) Native

skilz install 46ki75/skills/markdown --agent codex

Gemini CLI (Project) Project

skilz install 46ki75/skills/markdown --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

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

View All Agents

For Claude Desktop Easy

Download Agent Skill ZIP

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

Manual Installation

1. Clone the repository:

git clone https://github.com/46ki75/skills

2. Copy the agent skill directory:

cp -r skills/public/markdown ~/.claude/skills/

Owner: 46ki75 (GitHub)
Repository: skills
Type: Non-Technical
Meta-Domain: general
Primary Domain: general
Sub-Domain: markdown documentation skill
Market Score: 80

Agentic Skill Grades →

Agent Skill Grade

Score: 80/100 Click to see breakdown

Score Breakdown

Spec Compliance

12/15

PDA Architecture

24/30

Ease of Use

21/25

Writing Style

8/10

Utility

17/20

Modifiers: -2

Areas to Improve

Missing Table of Contents
No Reference Files for Rule Details
Workflow Steps Scattered

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 skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 80/100, solid B territory. This evaluation is based on Anthropic's best practices. Your strongest area is Utility (17/20) — the skill actually solves a real problem. Weakest is Spec Compliance (12/15), mostly due to minimal trigger phrases in your metadata.

What's Working Well

Practical utility — You're addressing a real pain point with markdown linting and fixing. The before/after patterns and command examples give people confidence they can actually use this.
Solid rule reference — Your "Quick Rule Reference" section covering 14 rules is comprehensive. The troubleshooting guidance for common fixes is genuinely helpful.
Clear trigger scenarios — Your 5 trigger scenarios (linting files, fixing markdown, validating output, style issues, fixing CI failures) are specific and discoverable. Someone looking for markdown help will find this.

The Big One: Progressive Disclosure Architecture

Here's what's holding you back from an A: everything lives in one 269-line file with no references directory. You're taking a token hit that you don't need to.

Why it matters: Skills that use references directories layer content efficiently — basic stuff inline, deep details in separate files. Your file is dense and practical, but you're missing the architecture to make it even more token-efficient.

The fix: Extract your "Quick Rule Reference" section (lines 249-268) to references/common-rules.md. Keep only the top 5 rules inline in the main skill. This cuts your main file by ~50 lines while keeping everything accessible.

**Estimate...

Browse Category

More general Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?