Individual skill
product-analytics
Stands up product analytics from decision questions backward - a north-star metric with an input-metric tree, an object-action event taxonomy with a governed tracking plan, and the priority analyses to build first: activation funnels, cohort retention curves, and feature adoption correlated with retention. Use when someone asks "what events should we track", "set up our analytics taxonomy", "where do users drop off before first value", or "what's our activation moment". Do NOT use for growth-accounting decompositions of MAU changes - use growth-accounting instead - or for deep funnel diagnosis on existing data - use funnel-analysis instead.
skills/product-analytics/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Product Analytics
You cannot improve what you do not measure, but most teams measure the wrong
things badly. A messy event taxonomy is technical debt that misleads every
decision built on it. This skill sets up analytics that actually inform product
work.
## Start With Questions, Not Events
Before instrumenting anything, write the decisions analytics must inform:
- Where do users drop off before first value?
- Which features correlate with retention?
- What does an activated user do that a churned one did not?