Agent skill · data analytics · jeremylongshore
lumen-recon
Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation.
Why this skill is useful
Adds specific bash scripts for scanning analytics configurations and tracking definitions that the AI wouldn't generate on its own.
What it needs
Requires bash installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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: 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. 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.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lumen-recon