analytics
Use this skill when the user needs to set up analytics, design event tracking, define key metrics, build funnels, or instrument their SaaS product for data-driven decisions. Covers event naming conventions, tracking strategy, funnel analytics, and data quality.
Best use case
analytics is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill when the user needs to set up analytics, design event tracking, define key metrics, build funnels, or instrument their SaaS product for data-driven decisions. Covers event naming conventions, tracking strategy, funnel analytics, and data quality.
Teams using analytics should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/analytics/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How analytics Compares
| Feature / Agent | analytics | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill when the user needs to set up analytics, design event tracking, define key metrics, build funnels, or instrument their SaaS product for data-driven decisions. Covers event naming conventions, tracking strategy, funnel analytics, and data quality.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Analytics & Instrumentation Track decisions, not dashboards. This skill helps you set up analytics that answer the questions that matter — without drowning in data. ## Core Principles - Every metric should connect to an action you'd take differently based on the result. - Instrument events at build time, not as an afterthought. It's 10x easier. - More data ≠ better decisions. Focus on 5-10 key metrics per stage. - Data quality matters more than data quantity. One clean funnel beats fifty broken ones. --- ## Choosing an Analytics Tool You don't need to write code to track events. Pick a tool, add the snippet, and configure in the UI. ### Recommended by Stage | Stage | Tool | Why | Cost | |-------|------|-----|------| | Pre-revenue | **PostHog** | Product analytics, funnels, session replay. Built for SaaS. | Free (1M events/mo) | | Pre-revenue | **Plausible** | Simple, privacy-first traffic analytics. | $9/mo | | $0-5K MRR | **PostHog** or **Mixpanel** | Deeper funnel analysis, cohort retention | Free tier or ~$200/mo | | $5K+ MRR | **Amplitude** or **Heap** | Advanced analytics, experimentation | $500+/mo | **Recommendation for solo founders:** Start with **PostHog** (free tier). It covers product analytics, funnels, session recordings, and feature flags — all things you'll need. For basic traffic analytics (where visitors come from), add **Plausible** or **Google Analytics 4** (free). ### Setup **Tell AI:** ``` Set up PostHog analytics: 1. Create a PostHog project and get the API key 2. Add the PostHog JavaScript snippet to our app (in the <head> or layout component) 3. Verify it's tracking page views by checking the PostHog dashboard 4. Configure: exclude admin/test accounts from tracking ``` --- ## What to Track (By Stage) ### Pre-Launch (Just These 3) 1. Landing page visits (traffic source) 2. Waitlist/signup conversions 3. Where visitors drop off ### 0-$1K MRR (Add These) 4. Signup → activation rate (completed key action) 5. Time to activate (hours from signup to key action) 6. D7 retention (% returning after 1 week) 7. Free-to-paid conversion ### $1K-$10K MRR (Add These) 8. Feature adoption (% of users using each feature weekly) 9. Cohort retention curves (track each month's signups over time) 10. Expansion revenue triggers (what behavior precedes upgrades) 11. Churn rate and reasons --- ## Event Naming Conventions Use a consistent schema so events make sense to anyone reading them. **Format:** [Object] [Action] in past tense, Title Case. | Event Name | When It Fires | |------------|--------------| | Signup Form Submitted | User completes registration | | Project Created | User creates their first/any project | | Dashboard Viewed | User visits the main dashboard | | Report Exported | User downloads or shares a report | | Subscription Upgraded | User moves to a higher plan | | Invite Sent | User invites a teammate | **Rules:** - Object first, then action (makes grouping in tools easier) - Past tense (the event already happened) - Be specific: "Signup Form Submitted" not "Form Submitted" - Never include personal data in the event name ### Event Properties Every event should include context: ``` "Project Created" template_used: "blank" | "marketing" | "engineering" source: "dashboard" | "onboarding" | "api" "Subscription Upgraded" from_plan: "free" to_plan: "pro" billing_period: "annual" trigger: "usage_limit" | "feature_gate" | "self_serve" ``` **Tell AI:** ``` Set up event tracking for our core funnel: - Track these events: [list your key events from the table above] - Include these properties with each event: [relevant properties] - Set user-level properties on identify: plan, signup_date, role - Verify events are firing correctly in PostHog/Mixpanel ``` --- ## Core Metrics Framework ### The 5 Metrics That Matter | Metric | What It Tells You | How to Calculate | |--------|------------------|-----------------| | **Signup rate** | Is your marketing working? | Visitors → Signups | | **Activation rate** | Is your onboarding working? | Signups → Completed key action | | **D7 retention** | Does your product deliver ongoing value? | % of users returning 7 days later | | **Free-to-paid** | Is your product worth paying for? | Free users → Paying users | | **MRR** | Is your business growing? | Sum of all monthly subscription revenue | ### Setting Up Your Dashboard **Tell AI:** ``` Create an analytics dashboard with these 5 charts: 1. Daily signups (line chart, last 30 days, by source) 2. Activation rate (% of signups who [completed key action], last 30 days) 3. D7 retention (% of each week's signups who returned 7 days later) 4. Free-to-paid conversion rate (last 30 days) 5. MRR (line chart, all time) This should be the first thing I see when I open analytics. ``` --- ## Funnel Instrumentation Define your core funnel and track every step: ``` Typical SaaS funnel: 1. Landing Page Viewed 2. Signup Form Viewed 3. Signup Form Submitted 4. Onboarding Started 5. [Key Activation Action] Completed 6. Second Session (returned next day/week) 7. Upgrade Page Viewed 8. Subscription Created ``` **The biggest drop-off between steps = your biggest opportunity.** Fix that first. **Tell AI:** ``` Instrument our conversion funnel: - Track these events in order: [list your funnel steps] - Build a funnel visualization showing drop-off between each step - Set up an alert if any step's conversion drops below [X]% week-over-week ``` --- ## Privacy and Compliance Add these before you launch: - [ ] Add analytics tool reference to your Privacy Policy - [ ] Add cookie consent banner if required (depends on tool and geography) - [ ] Enable "anonymize IP" in your analytics tool - [ ] Exclude admin/test accounts from tracking - [ ] Never track PII (email, name) in event properties without consent - [ ] Allow users to opt out of tracking - [ ] Respect Do Not Track (DNT) browser settings **Tell AI:** ``` Add privacy compliance for analytics: - Add a cookie consent banner that loads analytics only after consent - Exclude users with DNT enabled - Add an "opt out of tracking" toggle in account settings - Ensure no PII is sent in event properties ``` --- ## Common Mistakes | Mistake | Fix | |---------|-----| | Tracking everything from day one | Start with 5 metrics. Add more when you have questions they can't answer. | | No analytics until post-launch | Add the snippet during build. Track from first user. | | Dashboard but no actions | Every metric should have an "if this drops, I'll do X" response | | Ignoring data quality | Check that events are firing correctly once a week for the first month | | Paying for expensive tools too early | PostHog free tier handles most needs until $5K MRR | --- ## If You Can't Set Up Analytics Right Now Track these manually in a spreadsheet until you can: | Week | Signups | Activated | Retained (D7) | Paid | MRR | |------|---------|-----------|---------------|------|-----| | Week 1 | | | | | | | Week 2 | | | | | | Even rough manual tracking beats flying blind. Graduate to a real tool as soon as you can.
Related Skills
validate
Use this skill when the user needs to validate a business idea, test demand before building, run a smoke test, create an MVP experiment, or decide whether an idea is worth pursuing. Covers demand validation, smoke tests, fake-door tests, landing page experiments, and go/no-go decision frameworks for bootstrapped founders.
ux-design
Use this skill when flows feel clunky, users are confused, navigation needs planning, onboarding needs design, or accessibility needs implementation. Covers information architecture, user flows, interaction patterns, progressive disclosure, and error handling UX.
ui-patterns
Use this skill when the user needs to build a dashboard, settings page, data table, or any page layout. Also use when choosing component libraries, implementing responsive design, dark mode, or handling UI states (loading, empty, error). Covers component selection, page composition, and responsive implementation.
translate
Use this skill when the user is a domain expert (lawyer, doctor, contractor, accountant, etc.) who wants to turn their professional knowledge into a software product. Also use when the user says 'I have an idea for my industry,' 'I know this problem exists,' 'I want to build something for [profession],' or is struggling to describe what they want the software to do. Helps identify which professional pain is worth building for, then translates it into requirements AI tools can execute.
test
Use this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders.
technical-seo
Use this skill to implement technical SEO optimizations in code — meta tags, schema markup, Core Web Vitals, crawlability, robots.txt, sitemaps, and GEO (Generative Engine Optimization) for AI search engines. This is the implementation skill — for strategy see seo, for content writing see seo-content, for auditing see seo-audit.
support
Use this skill when the user needs to create help docs, build a knowledge base, set up self-serve support, or reduce support tickets. Covers documentation strategy, help center structure, support tone, and scaling support without hiring.
social-media
Use this skill when the user needs to grow a social media presence, create content for Twitter/X, LinkedIn, or other platforms, build a founder brand, or use social media as a distribution channel. Covers platform strategy, content frameworks, posting cadence, and audience building for bootstrapped SaaS founders.
seo
Use this skill when the user needs to plan SEO content, do keyword research, build a content calendar, map search intent to page types, or create an internal linking strategy. Also use when the user says 'how do I rank higher,' 'what should I write about for SEO,' 'SEO plan,' 'what keywords should I target,' or 'how to get organic traffic.' This is the strategy and planning skill — for writing content see seo-content, for technical implementation see technical-seo, for auditing see seo-audit.
seo-content
Use this skill when the user needs to write SEO content — blog posts, landing pages, feature pages, comparison pages, how-to guides, or any content meant to rank in search and get cited by AI. Covers content briefs, humanized writing that avoids AI detection, SERP feature targeting, entity optimization, content refresh, and quality self-checks. This is the writing skill — for strategy see seo, for technical implementation see technical-seo, for auditing see seo-audit.
seo-audit
Audit a codebase for SEO and AI-answer visibility, then produce a prioritized fix-it plan. Use this skill whenever a user says things like "audit my SEO", "check my site for search visibility", "how do I rank better", "optimize for Google", "optimize for AI answers", "SEO review", "GEO audit", "run the SEO agent", or anything about improving organic traffic or search rankings. Also trigger when someone mentions wanting visibility in AI-generated answers (ChatGPT, Gemini, Perplexity, Claude). Works on any web project — static sites, Next.js, Astro, Hugo, WordPress themes, or anything that outputs HTML.
secure
Use this skill when the user needs to secure their SaaS app, implement authentication, protect user data, secure APIs, or check for vulnerabilities. Also use when the user says 'is my app secure,' 'security check,' 'I'm worried about hackers,' 'how do I protect user data,' or 'security before launch.' Covers OWASP Top 10, auth best practices, data protection, and security checklists for apps built with AI tools.