/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.
$ npx -y skills add whawkinsiv/claude-code-superpowers --skill analytics --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/analytics
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
analytics.SKILL.mdname: analytics
description: "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."
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
Read more
name: analytics description: "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."
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
43 expert skills for non-technical founders building SaaS with AI tools (Claude Code, Lovable, Replit, Cursor). Covers the full lifecycle of planning, building, launching, and growing a software business — actionable guides, checklists, and copy-paste prompts.
Other skills on solo-founder-superpowers.
- /about-me
Use this skill when the user wants to create a founder profile, establish their personal voice for content, or set up context so other skills produce personalized output instead of generic AI copy. Also use when the user says 'set up my voice,' 'create my profile,' 'who am I,'
Open skill - /accounting
Use this skill when the user needs to set up bookkeeping, track revenue and expenses, prepare for taxes, choose accounting software, understand SaaS revenue recognition, or manage the financial operations of their bootstrapped business. Covers bookkeeping setup, tax preparation,
Open skill - /ads
Use this skill when the user needs to run Google Ads, write ad copy, select keywords, optimize CAC/LTV, or manage a small paid acquisition budget. Covers Google Ads strategy, keyword selection, ad copywriting, and conversion tracking for bootstrapped SaaS.
Open skill - /ai-features
Use this skill when the user needs to add AI-powered features to their SaaS product, integrate LLM APIs, build AI assistants, implement RAG, or use AI to differentiate their product. Covers API selection, prompt engineering for product features, cost management, and building AI
Open skill - /beautify
Use this skill when the user wants to make their app look better, says it looks like a template, asks how to achieve Stripe/Linear quality, or says something looks off. Covers visual hierarchy, whitespace, composition, color application, and typography in practice.
Open skill - /brand-identity-generator
Use this skill when the user needs to create a visual brand identity for their product. Generates a comprehensive BRAND-IDENTITY.md file for the project root. Covers colors, typography, spacing, components, accessibility, and responsive design — with no gaps for AI to fill with
Open skill