markdownlint-integration

43 stars 4 forks

Integrate markdownlint into development workflows including CLI usage, programmatic API, CI/CD pipelines, and editor integration.

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 →

Claude Code (CLI) Fast

skilz install TheBushidoCollective/han/markdownlint-integration

OpenCode (CLI) Fast

skilz install TheBushidoCollective/han/markdownlint-integration --agent opencode

OpenAI Codex (CLI) Native

skilz install TheBushidoCollective/han/markdownlint-integration --agent codex

Gemini CLI (Project) Project

skilz install TheBushidoCollective/han/markdownlint-integration --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/TheBushidoCollective/han

2. Copy the agent skill directory:

cp -r han/jutsu/jutsu-markdown/skills/markdownlint-integration ~/.claude/skills/

Owner: TheBushidoCollective (GitHub)
Repository: han
Stars: 43
Forks: 4
Type: Technical
Meta-Domain: web api
Primary Domain: api
Market Score: 58

Agentic Skill Grades →

Agent Skill Grade

Score: 58/100 Click to see breakdown

Score Breakdown

Spec Compliance

12/15

PDA Architecture

12/30

Ease of Use

17/25

Writing Style

6/10

Utility

14/20

Modifiers: -3

Areas to Improve

Description needs trigger phrases
Monolithic structure violates PDA
Missing table of contents

Recommendations

Focus on improving Pda (currently 12/30)
Address 2 high-severity issues first
Add trigger phrases to description for discoverability

Graded: 2026-01-05

Developer Feedback

I took a look at your markdownlint-integration skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 58/100, which is F territory. This skill covers a lot of ground on markdownlint integration—your Ease of Use is solid at 17/25, and Spec Compliance hits 12/15—but the biggest drag is Progressive Disclosure Architecture at just 12/30. The core issue? You've crammed 910 lines into a single SKILL.md file when it should be broken into modular reference files. That's killing your token efficiency and navigation.

What's Working Well

Comprehensive coverage: You're touching CLI, API, CI/CD (GitHub Actions, GitLab, CircleCI, Jenkins, Azure), hooks, and editors. That's thorough.
Valid frontmatter: Your YAML checks out with all required fields present.
Consistent terminology: Good use of consistent language around "markdownlint," "linting," and "configuration" throughout.
Real code examples: You're not skipping over the implementation details—there are actual command examples and configurations people can use.

The Big One: Break Up That Monolithic File

Your skill is essentially a 910-line encyclopedia squeezed into one file. This violates progressive disclosure architecture hard. The fix is straightforward:

Create a references/ directory with external files:

references/cli.md - Command-line usage
references/api.md - Node.js API integration
references/ci-github.md, ci-gitlab.md, ci-circleci.md, etc. - Each CI platform gets its own file
references/editors.md - VS Code, Vim, Neovim configurations
references/hooks.md - Pre-commit and Husky setups

Your main SKILL.md becomes a ...

Browse Category

More web api Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?