revenue-health-dashboard

I've been digging into financial dashboarding skills lately, and I noticed your revenue-health-dashboard takes a pretty opinionated approach to metrics visualization—curious what drove some of those architectural choices, especially given the D-grade landing on utility and polish.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 62/100, solidly in D territory. The grading is based on Anthropic's best practices for agentic skills—progressive disclosure, ease of use, spec compliance, writing clarity, and real-world utility. Your Spec Compliance is decent (11/15), but Utility (11/20) and Progressive Disclosure Architecture (18/30) are dragging the score down. Basically, the framework is there conceptually, but it lacks the scaffolding and actionable depth to actually guide someone through building this.

What's Working Well

• Spec-compliant frontmatter – Your YAML structure is clean and valid; the hyphen-case naming follows conventions perfectly
• Clear conceptual framework – The KPI Stack, Segmentation Layer, and Guardrail components make intuitive sense for revenue dashboards
• Relevant terminology consistency – You stick with KPIs, guardrails, and dashboard language throughout, which keeps things cohesive
• Real use cases – The tips section acknowledges practical needs like snapshot-before-remediation tracking

The Big One: Missing Progressive Disclosure Architecture

Here's the thing: you've got 31 lines of content crammed into a single SKILL.md file with zero reference structure. For a dashboard skill, that's leaving a ton of value on the table.

Why it matters: Developers need progressive disclosure—give them the quick framework first, then let them drill down into specifics (examples, templates, implementation guides) without cluttering the main file. Right now, someone reading this has to imagine what a KPI dial config actually looks like or how to set guardrail thresholds in practice.

The fix: Create a references/ directory with:

• references/kpi-definitions.md – concrete examples: bookings ($ revenue closed), pipeline coverage (pipeline $ / quota), win rate (won deals / qualified pipeline)
• references/dashboard-template.md – actual JSON/YAML schema for dashboard config
• references/implementation-guide.md – step-by-step numbered workflow (define KPIs → configure segmentation → set thresholds → build tiles → link drill-downs)

This alone bumps you +7 points and fixes your architecture score from weak to strong.

Other Things Worth Fixing

1. Trigger phrases missing – Your description says "Visualization blueprint for revenue KPIs" but doesn't tell LLMs when to use this. Add: Use when asked to "build revenue dashboard", "create KPI dashboard", "visualize revenue health", or "track revenue metrics". → +2 points

2. No workflow steps – The Framework section lists components but doesn't walk through implementation order. Add numbered steps: 1) Define KPIs, 2) Configure segmentation, 3) Set guardrails, etc. → +3 points

3. Examples are mentioned but missing – You reference "executive summary slide" and "traffic lights" without actual mockups or config samples. Add these to references. → +3 points

4. No validation checklist – The "snapshot before/after" tip is good, but it's not operationalized. Add a validation section: check that guardrails trigger correctly, drill-downs navigate properly, metrics update in real-time. → +2 points

Quick Wins

• Add trigger phrases to description (+2 points, 5 min)
• Create references directory with 3 markdown files (+7 points, 30 min)
• Number your implementation steps in Framework section (+3 points, 10 min)
• Add concrete examples/templates to references (+3 points, 20 min)

That's roughly +15 points and 65 minutes of work to land in the B-range territory (77/100).

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.