markdown

I took a look at your markdown skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

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: +3 points (taking you to 83/100, solid B+)

Other Things Worth Fixing

1. Add a table of contents — At 269 lines, readers shouldn't have to scroll to find "Execution Pattern" or "Manual Fixes Required." Add a TOC after your workflow overview. (+2 points)

2. Expand trigger phrases — Your description only has 1-2 triggers. Add phrases like "markdown validation," "style checker," "linting tool" to your metadata description. This helps discoverability. (+1 point)

3. Consolidate workflow steps — Your "Workflow Overview" (lines 11-18) is brief, then detailed execution patterns scattered across sections. Give people a single numbered checklist with all commands, even if it's a bit longer. Makes it less hunting-around-y.

4. Watch the second-person voice — One instance: "Most common rules Claude will encounter" (line 249). Should be "Most common rules encountered:" Shift to imperative throughout.

Quick Wins

• Create references/common-rules.md and pare down inline rules (+3 points)
• Add TOC to main file (+2 points)
• Expand trigger phrases in metadata (+1 point)
• Fix voice consistency (+1 point)

You're already at 80/100 — these changes get you past 85 with minimal effort.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.