What problem does it solve? DevRel teams report vanity numbers like stars, impressions, and event counts that cannot survive an executive asking "so what would you do differently?". This Skill replaces activity logs with a defensible measurement framework: five to eight metrics tiered from reach to business impact, each with a written attribution rule, a baseline-derived target, an owner, and a named action. ## Core Features & Use Cases - Metric framework construction: Brainstorms two or three measurement spines (driver-anchored AAARRRP, journey-stage, or function-split), then shortlists 5-8 metrics across a five-tier ladder from reach to business impact, ranked by value per unit of effort. - Attribution realism: Writes the attribution rule before the period starts, choosing among self-reported attribution, tagged links, influenced pipeline, and pre/post lift, with each method's known bias stated. - Anti-vanity guardrails: Cuts monotonic metrics, pairs incentivised volume targets with counter-metrics, enforces a small-N floor, and tags every threshold as sourced, baseline, or hypothesis. - Use Case: A DevRel lead whose VP asked "what is any of this for?" about a monthly report of stars and downloads uses this Skill to produce a framework document with a metric sheet, attribution rule, blind-spots section, and a kill rule for metrics that never change a decision. ## Quick Start Ask the assistant to build a DevRel measurement framework for your program, describing your funded driver, who reads the numbers, and what data sources already exist.
