markdownlint-custom-rules

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

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 65/100, which puts you in D territory—solid foundation, but needs meaningful work to really shine. The evaluation uses Anthropic's best practices rubric. Your strongest spot is Spec Compliance (12/15), but Progressive Disclosure Architecture is dragging you down hard at just 12/30. That's the biggest opportunity.

What's Working Well

• Comprehensive coverage — You've got 15+ complete code examples showing different parser types (markdown-it, markdownlint-cli, etc.), which is genuinely helpful for someone building custom rules
• Solid spec compliance — Your YAML frontmatter is clean, naming follows conventions (hyphen-case), and you're using allowed-tools properly
• Consistent terminology — Throughout the 756 lines, you're consistent with markdownlint, parser, onError, fixInfo—no confusion about terminology
• Real problem solving — This addresses an actual gap; custom markdownlint rules aren't trivial, and you show multiple approaches (sync/async, different parsers, etc.)

The Big One: Progressive Disclosure Architecture

Here's what's holding you back: everything is in one 756-line SKILL.md file with no references. Every time this skill activates, it loads all 756 lines. That's brutal for token economy.

Why it matters: Skills should reveal complexity progressively. A user asking "how do I write a basic markdownlint rule?" doesn't need your async rule examples or parser deep-dives in the initial context window.

The fix: Create a references/ directory with these files:

• parser-examples.md — ...