insight-driven-event-tracking
Transform raw data into actionable insights by shifting from tracking "what happened" to "why it happened." Use this skill when designing instrumentation specs for new features, auditing analytics dashboards that provide no clear direction, or diagnosing sudden drops in conversion.
npx skills add majiayu000/claude-skill-registry --skill insight-driven-event-tracking --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Insight-Driven Event Tracking Most analytics efforts fail because they track "entertainment" (data that is interesting but doesn't change behavior) rather than "news" (information that forces a change in the real world). This framework shifts instrumentation from simple event logging to capturing the context necessary to explain user intent. ## The Core Principles ### 1. Observation vs. Insight * **Observation:** A raw fact from the database (e.g., "Power users book 4x more than new users"). This has no context and offers no clear action. * **Insight:** An observation plus the "Why" (e.g., "Power users convert at 2x the rate when they see at least 5 drivers on the map"). This tells you exactly what lever to pull (increase supply density). ### 2. The Physics of the Growth Model Before tracking, define the "physics" of your specific universe to identify where levers actually exist: * **Market:** Who are the users and suppliers? * **Product:** What is the core value proposition? * **Model:** How do you charge or capture value? * **Channel:** How do users find you? (e.g., In Southeast Asia, Gojek’s physical drivers in green jackets were a primary growth channel). ## The Instrumentati
- The Core Principles
- 1. Observation vs. Insight
- 2. The Physics of the Growth Model
- The Instrumentation Workflow
- Step 1: Identify the "Step Before"
- Step 2: Define Contextual Properties
- Step 3: Run the "News Test"
- Examples
- Benchmarks for Success
- Common Pitfalls to Avoid
What does the insight-driven-event-tracking skill do?
Transform raw data into actionable insights by shifting from tracking "what happened" to "why it happened." Use this skill when designing instrumentation specs for new features, auditing analytics dashboards that provide no clear direction, or diagnosing sudden drops in conversion.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill insight-driven-event-tracking --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.