Map users, accounts, entities, value flows, and the codebase into a structured product model before designing telemetry.
Product Analytics Skills for Claude Code, Codex & AI Agents
These skills help an agent instrument a product and turn usage data into decisions. Members cover event plans, typed tracking, retention, attribution, experiments, SDK guides, and product analytics cases.
17 skillsExplore Product Analytics skills
8 skillsUse a product model and current-state audit to define events, properties, entities, and a documented delta from existing tracking.
Generate typed event definitions, SDK wrappers, identity handling, validation helpers, and integration examples from a tracking plan.
Seven workflows for modeling a SaaS product, auditing analytics, designing tracking plans, and implementing maintainable instrumentation.
Translate an approved tracking plan into SDK-specific identify, group, and track patterns with architecture and integration guidance.
Assess a feature change, decide whether events need to change, and update the tracking plan, mini-delta, and changelog together.
Write a stakeholder-ready case for analytics instrumentation, connecting product blind spots, implementation scope, and expected business questions.
Inspect analytics SDK calls, identity handling, and live instrumentation to produce a factual tracking inventory and current-state report.
Related topics
How to choose Product Analytics skills
Begin with a tracking plan before changing code, then use retention or attribution entries after events are flowing; choose experiment skills for a measured product change.
- Design an event tracking plan
- Analyze retention for a product feature
- Plan an experiment from product data