recharts

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

Links:

• GitHub
• Your skill on SkillzWave

The TL;DR

You're at 77/100, solid C-grade territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Spec Compliance (14/15) — the frontmatter and structure are clean. The biggest drag is Progressive Disclosure Architecture (19/30) — everything's crammed into one 351-line file without the layered reference structure that helps users navigate efficiently.

What's Working Well

• Spec compliance is tight — Valid YAML, proper naming conventions, good description with 30+ triggers covering chart types and natural language patterns like "show data over time"
• Strong trigger coverage — You've got regex patterns and variations that'll catch real developer queries
• Practical examples — Four complete chart type examples with realistic data; the custom tooltip and tick templates are useful for common customization needs
• Clear decision making — The chart type decision tree helps devs pick the right component without guessing

The Big One: No Reference Architecture

Your entire skill is one monolithic file. With 351 lines, this violates progressive disclosure — devs can't easily navigate to what they need, and you're not leveraging the token efficiency that reference files provide.

The fix: Split it up:

• references/chart-types.md — Detailed specs for BarChart, LineChart, AreaChart, PieChart (move your current chart type sections here)
• references/customization.md — All the tooltip, tick, and styling examples
• Keep your main SKILL.md lean with quick start and decision tree

This structure alone could get you +6 points and makes the skill way easier to use.

Other Things Worth Fixing

1. Add a table of contents — At 351 lines, users need a roadmap. Add a ## Contents section at the top with links to Quick Start, Chart Types, Customization, etc. (+2 points)

2. Consolidate imports — Each chart example has a full import block. Show one comprehensive import at the top, then reference it in examples. Cuts redundancy and saves tokens. (+1 point)

3. Add workflow steps — Your examples show code blocks but lack numbered implementation steps (Install → Import → Prepare Data → Compose Chart → Wrap in ResponsiveContainer). Helps devs follow along. (+2 points)

4. Explicit verification loops — Your success criteria checklist exists but needs verification commands. For example: "Verify ResponsiveContainer: resize browser window and confirm chart adapts; Check accessibility: run color contrast analyzer." (+2 points)

Quick Wins

• Highest impact: Split into reference files (+6 points)
• Easy adds: TOC, consolidated imports, numbered steps (+5 points combined)
• Together: These get you from 77 to solid B territory (85+)

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