What problem does it solve? Developer-relations numbers disagree across tools: docs analytics undercount a developer audience that blocks client-side scripts, registry download counts include CI and bots, and repository traffic history expires after 14 days. This Skill produces a written tracking plan that makes DevRel measurement real and defensible. ## Core Features & Use Cases - Surface register and event taxonomy: Maps every surface (docs, repositories, package registries, community venues, off-web talks) to its actual data source, retention window, and bias, then defines an Object-Action event taxonomy with a property registry. - Identity spine and attribution discipline: Defines anonymous_id, user_id, and account_id stitching, plus source, source_basis, and source_confidence fields so attribution claims carry their evidence type. - Link-tagging convention and quality gate: Fixes a controlled UTM vocabulary, a link registry, and a four-check quality gate (decision coverage, verified traces, join coverage, tag well-formedness). - Use Case: A DevRel lead whose GitHub traffic numbers vanished learns the 14-day retention window, schedules a daily snapshot export, and captures a dated baseline before instrumenting anything else. ## Quick Start Ask the assistant to build a DevRel tracking plan for your docs site, repositories, and package registry before an upcoming launch.
