community-kpi-dashboard

Took a look at your community KPI dashboard skill—the approach to tracking metrics across distributed teams is solid, though the implementation could use some refinement on the PDA side to handle token efficiency better.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 62/100, which puts you in D territory. This is based on Anthropic's 5-pillar rubric for agentic skills. Your strongest area is Spec Compliance (11/15) — the YAML frontmatter is clean and properly formatted. The biggest drag is Utility (10/20) — you're laying out a conceptual framework without the implementation teeth to back it up, plus PDA (18/30) where you're missing the reference files you're promising.

What's Working Well

• Solid YAML structure — Frontmatter is valid with required fields; name convention follows hyphen-case correctly
• Clear metric taxonomy — Breaking health, engagement, and business impact metrics into distinct buckets helps users understand what to measure
• Objective tone — No fluff marketing language; stays instructional and grounded
• Real problem domain — Community measurement is genuinely hard; you're addressing a gap

The Big One: Missing Templates Kill Your Utility Score

Your Templates section promises three concrete deliverables—"BI dashboard schema," "KPI definition sheet," and "executive digest template"—but there's nothing backing it up. This tanks your score on two fronts:

1. PDA breakdown: You're claiming to provide reference files that don't exist. Readers expect references/dashboard-schema.md, references/kpi-definitions.md, and references/executive-digest-template.md.
2. Utility collapse: Without actual templates, users get a framework but no starting point. They have to build dashboards from scratch, which defeats the skill's purpose.

Fix: Create those three reference files with real, usable content. Even lightweight examples (a 10-line schema, a sample KPI definition format, a 5-section digest outline) would push you 5+ points and make this actually actionable.

Other Things Worth Fixing

1. No trigger phrases in description — Your frontmatter description says "Measurement system tracking engagement..." but includes zero trigger terms like "track community metrics" or "measure engagement." Users won't find this skill when they ask for it. Rewrite to: "Build community KPI dashboards tracking engagement, health, and business impact. Use when asked to 'track community metrics', 'measure engagement', 'community OKRs'..." → +2 points

2. Framework lists categories, not steps — "Health Metrics" is descriptive, but there's no numbered workflow saying "1) Identify business objective, 2) Select 3-5 metrics, 3) Define data sources..." Without that, users can't actually build anything. → +4 points

3. Inconsistent voice throughout — "Establishing community OKRs" mixes with "Blend qualitative highlights"—you're jumping between gerunds, nouns, and imperatives. Pick imperative ("Establish OKRs") or infinitive ("To establish...") and stick with it. → +2 points

4. Zero validation guidance — No way to verify the dashboard is correct once built. Add a Validation section: "Run dashboard against previous quarter, compare auto metrics to manual reports (variance <5%), verify data refresh schedules." → +3 points

Quick Wins

• Most impactful: Create the three reference files you're already promising (dashboard schema, KPI definitions, exec digest)
• Easy: Add trigger phrases to the frontmatter description
• Medium effort: Convert Framework into numbered implementation steps
• Polish: Standardize voice across all sections

Fixing these four gets you to ~76/100 pretty cleanly. Focus on the templates first—that's where most of your points are hiding.

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.