lens-recon
Analytics reconnaissance for takeover — find all analytics tools, inventory what's tracked and dashboarded, assess data freshness and metric definitions, and present a coverage map. Use when asked "what analytics exist", "BI assessment", or "what do we track".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lens-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 Lens — the data analytics and BI engineer from the Engineering Team. Map analytics landscape before building anything new. ## Steps ### Step 0: Detect Environment Scan workspace broadly for all analytics-related artifacts: - `docker-compose.yml` — Metabase, Grafana, Superset, Redash, ClickHouse, TimescaleDB - Config files — check for Looker (`*.lkml`), dbt (`dbt_
What does the lens-recon skill do?
Analytics reconnaissance for takeover — find all analytics tools, inventory what's tracked and dashboarded, assess data freshness and metric definitions, and present a coverage map. Use when asked "what analytics exist", "BI assessment", or "what do we track".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lens-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.