From experimentation-growth-engineering
Instrument trustworthy product analytics: a tracking plan first, a consistent typed event/property schema (object_action naming, versioned), identity stitching (anonymous -> known), CDP routing (instrument once), and event-quality validation as code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/experimentation-growth-engineering:event-instrumentationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Define events + properties + naming + types **before** instrumenting. Ad-hoc events = the data mess.
Define events + properties + naming + types before instrumenting. Ad-hoc events = the data mess.
object_action naming, one case convention, typed + validated properties, versioned. An event named 3 ways is 3 events.
Tie anonymous -> known on identify, so funnels/attribution survive login. Broken stitching breaks every cross-session analysis.
Instrument once (Segment-style), fan out (warehouse copy -> data-platform). Validate events against the plan; monitor volume; treat instrumentation as code.
npx claudepluginhub mcorbett51090/ravenclaude --plugin experimentation-growth-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.