Your analytics tool isn't the problem. Your product tracking is.
Most SaaS products have inconsistent events, missing context, and no real tracking plan. Product Tracking Skills scans your codebase, audits what's tracked, and generates the instrumentation needed to make your analytics tools actually work.
or install directly
Works in
Most products are flying blind
You're paying for Amplitude, Mixpanel, or PostHog — and they work fine. You still can't answer basic questions:
- — Which features do your customers actually use?
- — Where do users drop off in your core workflow?
- — Which accounts are at risk of churning?
Your analytics tool isn't the problem. Your product tracking is. The instrumentation feeding it is missing, inconsistent, or decayed — and no one has time to fix it.
The cost of staying blind
Product decisions
Made on gut feel, not data
Customer success
No visibility into account health
Investor conversations
No credible usage metrics
Engineering time
Wasted on ad-hoc tracking requests
Analytics ROI
Zero — the tools work, but the tracking feeding them doesn't
Seven skills. Your analytics tools finally work.
Product Tracking Skills walks you through a structured process — from understanding your product to generating real, typed, SDK-specific code.
Each skill produces artifacts that feed the next. Everything lives in your repo. Context survives across sessions and engineers.
Model
(what)
Audit
(is)
Design
(should)
Instrument
(how)
Implement
(apply)
Maintain
(evolve)
Model (what)
Scans your codebase, asks targeted questions about value and entities
Audit (is)
Reverse-engineers current tracking from your code
Design (should)
Designs an opinionated target plan + explicit delta
Instrument (how)
Maps the plan to your specific SDK
Implement (apply)
Generates real code following the guide
Maintain (evolve)
Updates tracking when features ship
Model
Scans your codebase, asks targeted questions about value and entities
Product model: what your product does, who uses it, how value flows
Audit
Reverse-engineers current tracking from your code
Factual inventory of what's actually tracked today
Design
Designs an opinionated target plan + explicit delta
Tracking plan + the exact diff from current to target
Instrument
Maps the plan to your specific SDK
SDK-specific instrumentation guide with template code
Implement
Generates real code following the guide
TypeScript types, typed wrapper functions, usage examples
Maintain
Updates tracking when features ship
Versioned plan updates + changelog
Three commands. Tracking that actually works.
Install the skills
Add the skills to your AI agent tool. Works with Claude Code, Codex, VS Code — any tool with agent support.
Point it at your codebase
Say "model this product" and the skills scan your routes, models, and controllers to understand what your product does.
Run the lifecycle
Audit what's tracked. Design what should be tracked. Generate the code to close the gap. Done.
Product model saved to .telemetry/product.md
Saved to .telemetry/current-state.yaml
Built for the people who feel the pain
Founders
You know you need product analytics. You've been meaning to set it up for months. You've probably tried once and ended up with five inconsistently-named events. These skills do it properly in a fraction of the time.
Product Engineers
Tracking code scattered across 23 files. Mixed casing. No one knows what's tracked. You need a system: audit reality, design intent, generate typed code, maintain as features ship. That's what this is.
CS / Success Teams
You need visibility into how accounts use the product. Feature adoption. Engagement signals. Churn risk. You can't build it yourself, but you can hand engineering a clear process: "Run these skills. Get us the data."
Users and accounts are first-class
This isn't web analytics adapted for B2B. It's built for products where users belong to accounts, accounts have hierarchies, and feature adoption matters at the account level.
- Group hierarchy built in (account > workspace > project)
- User and account traits designed as part of the plan
- Event attribution at the correct group level
- Identity management (identify, group, reset) handled per SDK
DESTINATIONS
Supports 25+ platforms across 7 categories
Pre-built destination guides for product analytics, CDPs, web analytics, error monitoring, feature flags, and session replay tools.
Not a prompt. Not a template. A process.
Everything lives in .telemetry/
Every artifact is a file in your repo. Git tracks how your understanding evolved. Nothing lives in someone's head or a third-party tool.
.telemetry/
├── product.md # What your product does
├── current-state.yaml # What's tracked today
├── tracking-plan.yaml # What should be tracked
├── delta.md # Current → target diff
├── instrument.md # SDK-specific guide
├── changelog.md # How the plan evolved
└── audits/
└── 2026-02-13.md # Audit snapshotsWe take positions so you don't have to debate them
- dot.notation for events. report.created, not Created Report or reportCreated. Object then action, always.
- snake_case for properties and traits. plan_type, company_size, last_seen_at. Consistent, predictable, queryable.
- Properties over events. One event with a type property beats three similar events.
- Minimalist coverage. Track what matters. Skip what doesn't. Less is cheaper.
- Audit before design. Describe reality before deciding intent. No assumptions.
- Delta-driven. Current → target diff is the implementation backlog. No ambiguity.
Opinionated starting points for common product types
B2B SaaS Core
Generic B2B SaaS baseline
AI/ML Tools
AI products, generation, models
Developer Tools
APIs, SDKs, CLI tools
Collaboration Tools
Team workspaces, real-time collab
Form Builders
Form creation, submissions
Security Products
Security events, alerts, compliance
Analytics Platforms
Analytics products tracking their own usage
Frequently asked questions
Fix your tracking. Make your analytics tools actually work.
MIT-licensed. Install in 2 minutes. Run "audit tracking" to see what you're missing.