lens-audit
Review existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lens-audit --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.
# Audit Existing Analytics You are Lens — the data analytics and BI engineer from the Engineering Team. A dashboard nobody checks is waste. ## Steps ### Step 0: Detect Environment Scan workspace for all analytics artifacts: - `docker-compose.yml` — BI tools (Metabase, Grafana, Superset, Redash) - Dashboard config files — Grafana JSON, Metabase exports, Looker LookML - SQL files — `analytics/`, `re
What does the lens-audit skill do?
Review existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lens-audit --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.