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.
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lumen-recon --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: ```bash # Analytics libraries find . -name "package.json" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude\|heap\|analytics\|gtag\|ga4" 2>/dev/null | head -5 find . -nam
What does the lumen-recon skill do?
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.
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lumen-recon --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.