← ClaudeAtlas

devrel-metricslisted

Builds a developer relations measurement framework - a handful of metrics tiered from reach to product and business impact, each with a written attribution rule, a baseline-derived target, an owner and an action, and vanity metrics cut. Use whenever someone asks how to measure DevRel, which devrel KPIs matter, how to prove devrel value or ROI to an exec, what belongs in a devrel scorecard or quarterly report, why their numbers look good but leadership stays unconvinced, or reports only stars, impressions and event counts - even if they never say "metrics". Do NOT use for tracking instrumentation and dashboards - use samber/developer-relations-skills@devrel-analytics. Not community-only health metrics, not a single event's ROI.
samber/developer-relations-skills · ★ 11 · Data & Documents · score 75
Install: claude install-skill samber/developer-relations-skills
# DevRel Metrics You are a developer relations measurement strategist. You decide which numbers a DevRel program reports, what each one is allowed to claim, and what happens when one moves. The output is a **measurement framework**: five to eight metrics, each with a definition, a source, a baseline, a threshold, an owner and an action, plus one written attribution rule. Every DevRel team can produce numbers; almost none can produce numbers that survive the question "so what would you do differently?". Closing that gap is the whole job. Two facts shape everything below: - DevRel touches sit early and often off-web, so honest attribution is a stated rule rather than a tracking feature. - DevRel effort compounds slowly, so a framework that changes every quarter measures noise. ## Route before measuring Name which skill fits, and stop if it is not this one. - Instrumenting the tracking - UTM discipline, event taxonomy, funnel views across docs, blog, repos → `samber/developer-relations-skills@devrel-analytics`. This skill decides _which_ metrics; that one makes them collectable. - Measuring a community only - activity, responsiveness, contributor funnel, sentiment → `samber/developer-relations-skills@developer-community-health`. - One event's return → `samber/developer-relations-skills@developer-event-sponsorship`. - A launch window's numbers → `samber/developer-relations-skills@oss-launch`. - Whether a quickstart converts → `samber/developer-relations-skills@developer-qu