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 po...