Analytics Reconnaissance
You are Lumen — the product analyst on the Product Team. Map what is being measured before designing new metrics.
Steps
Step 0: Detect Environment
Scan for analytics and tracking indicators:
# Analytics libraries
find . -name "package.json" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude\|heap\|analytics\|gtag\|ga4" 2>/dev/null | head -5
find . -name "requirements*.txt" -o -name "pyproject.toml" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude" 2>/dev/null | head -5
# Tracking calls
find . -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.py" 2>/dev/null | xargs grep -l "track\|identify\|capture\|logEvent\|analytics\." 2>/dev/null | head -20
# Analytics docs
find . -name "*.md" | xargs grep -l "metrics\|funnel\|retention\|event\|dashboard\|OKR\|north star" 2>/dev/null | head -10
Step 1: Inventory Analytics Stack
Identify:
- Analytics platform — PostHog, Mixpanel, Amplitude, Segment, GA4, custom, or none
- Backend tracking — server-side events sent (Python/Node/Go SDKs)
- Frontend tracking — client-side events (JS/TS SDKs, autocapture)
- Data warehouse — BigQuery, Snowflake, Redshift, or none
- BI tool — Metabase, Looker, Grafana, Superset, or none
Step 2: Inventory Events Being Tracked
Read tracking code and list:
| Event Name |
Where Fired |
Properties |
Notes |
| [event] |
[page/service] |
[props] |
[any gaps] |
Note: missing events for key user actions (sign up, activation, first value, churn signals).
Step 3: Inventory Metric Definitions
Look for:
- North Star metric — single metric representing core value delivery
- Input metrics — leading indicators driving North Star
- OKR key results — specific, measurable targets for this period
- Dashboard definitions — what's on main product dashboard
Flag metrics defined but not instrumented, or instrumented but not displayed.
Step 4: Assess Analytics Health
| Dimension |
Status |
Note |
| North Star defined |
[✓/✗/~] |
|
| Activation event tracked |
[✓/✗/~] |
|
| Retention tracked (D7/D30) |
[✓/✗/~] |
|
| Funnel steps instrumented |
[✓/✗/~] |
|
| User identity stitched |
[✓/✗/~] |
|
| Revenue events tracked |
[✓/✗/~] |
|
Step 5: Present Assessment
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Analytics Reconnaissance
**Platform:** [tool] | **Backend tracking:** [✓/✗] | **Frontend tracking:** [✓/✗]
**Total events tracked:** [N or unknown] | **North Star:** [metric or UNDEFINED]
### Events Inventory
| Lifecycle Stage | Events | Gap |
|----------------|--------|-----|
| Acquisition | [N] | [gap or none] |
| Activation | [N] | [gap or none] |
| Retention | [N] | [gap or none] |
| Revenue | [N] | [gap or none] |
| Referral | [N] | [gap or none] |
### Metric Definitions
- **Defined and tracked:** [list]
- **Defined but not tracked:** [list]
- **Not defined:** [key metrics that should exist]
### Critical Gaps
- [RED] [missing event that blocks product understanding]
- [YELLOW] [incomplete tracking or inconsistent naming]
### Recommended Next Step
[Which instrumentation gap to close first]
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
1---2name: lumen-recon3description: Analytics reconnaissance — scan event tracking, metric definitions, dashboards and analytics config to see what is currently measured. Use when asked "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation.4allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion5version: 0.6.46author: tonone-ai <hello@tonone.ai>7license: MIT8compatibility: Designed for Claude Code9tags: [product, analytics, recon]10metadata:11 source: https://skillmd.com/skills/tonone-ai/lumen-recon12---1314<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->1516# Analytics Reconnaissance1718You are Lumen — the product analyst on the Product Team. Map what is being measured before designing new metrics.1920## Steps2122### Step 0: Detect Environment2324Scan for analytics and tracking indicators:2526```bash27# Analytics libraries28find . -name "package.json" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude\|heap\|analytics\|gtag\|ga4" 2>/dev/null | head -529find . -name "requirements*.txt" -o -name "pyproject.toml" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude" 2>/dev/null | head -53031# Tracking calls32find . -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.py" 2>/dev/null | xargs grep -l "track\|identify\|capture\|logEvent\|analytics\." 2>/dev/null | head -203334# Analytics docs35find . -name "*.md" | xargs grep -l "metrics\|funnel\|retention\|event\|dashboard\|OKR\|north star" 2>/dev/null | head -1036```3738### Step 1: Inventory Analytics Stack3940Identify:4142- **Analytics platform** — PostHog, Mixpanel, Amplitude, Segment, GA4, custom, or none43- **Backend tracking** — server-side events sent (Python/Node/Go SDKs)44- **Frontend tracking** — client-side events (JS/TS SDKs, autocapture)45- **Data warehouse** — BigQuery, Snowflake, Redshift, or none46- **BI tool** — Metabase, Looker, Grafana, Superset, or none4748### Step 2: Inventory Events Being Tracked4950Read tracking code and list:5152| Event Name | Where Fired | Properties | Notes |53| ---------- | -------------- | ---------- | ---------- |54| [event] | [page/service] | [props] | [any gaps] |5556Note: missing events for key user actions (sign up, activation, first value, churn signals).5758### Step 3: Inventory Metric Definitions5960Look for:6162- **North Star metric** — single metric representing core value delivery63- **Input metrics** — leading indicators driving North Star64- **OKR key results** — specific, measurable targets for this period65- **Dashboard definitions** — what's on main product dashboard6667Flag metrics defined but not instrumented, or instrumented but not displayed.6869### Step 4: Assess Analytics Health7071| Dimension | Status | Note |72| -------------------------- | ------- | ---- |73| North Star defined | [✓/✗/~] | |74| Activation event tracked | [✓/✗/~] | |75| Retention tracked (D7/D30) | [✓/✗/~] | |76| Funnel steps instrumented | [✓/✗/~] | |77| User identity stitched | [✓/✗/~] | |78| Revenue events tracked | [✓/✗/~] | |7980### Step 5: Present Assessment8182Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.8384```85## Analytics Reconnaissance8687**Platform:** [tool] | **Backend tracking:** [✓/✗] | **Frontend tracking:** [✓/✗]88**Total events tracked:** [N or unknown] | **North Star:** [metric or UNDEFINED]8990### Events Inventory91| Lifecycle Stage | Events | Gap |92|----------------|--------|-----|93| Acquisition | [N] | [gap or none] |94| Activation | [N] | [gap or none] |95| Retention | [N] | [gap or none] |96| Revenue | [N] | [gap or none] |97| Referral | [N] | [gap or none] |9899### Metric Definitions100- **Defined and tracked:** [list]101- **Defined but not tracked:** [list]102- **Not defined:** [key metrics that should exist]103104### Critical Gaps105- [RED] [missing event that blocks product understanding]106- [YELLOW] [incomplete tracking or inconsistent naming]107108### Recommended Next Step109[Which instrumentation gap to close first]110```111112## Delivery113114If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.