---
name: lens-audit-4853a623feb1
description: 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".
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [engineering, analytics, bi, audit]
---

# 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/`, `reports/`, `queries/`, `sql/` directories
- Scheduled jobs — cron, Airflow DAGs, GitHub Actions that generate reports
- `dbt_project.yml` — dbt models and metrics
- Python scripts — Streamlit apps, Dash apps, report generators
- Product analytics configs — Mixpanel, Amplitude, PostHog, GA4 setup
- Slack webhook configs — automated report delivery

### Step 1: Inventory All Dashboards and Reports

For each dashboard or report found, document:

- **Name** — what it's called
- **Location** — where it lives (URL, file path, tool)
- **What it shows** — which metrics, what data
- **Last modified** — when last updated (check git log, file timestamps)
- **Creator** — who built it (git blame, tool metadata)
- **Schedule** — if automated, how often it runs

### Step 2: Assess Usage and Value

For each dashboard or report, evaluate:

- **Who looks at it?** — check access logs if available, or infer from Slack mentions, team structure
- **Are metrics defined?** — precise definition for each number shown, or ambiguous?
- **Does it drive decisions?** — can someone act on what they see, or is it "interesting"?
- **Is data fresh?** — pulling current data, or pipeline broken/stale?
- **Is it maintained?** — updated as product evolved?

### Step 3: Identify Issues

Flag:

- **Dashboards nobody uses** — no access in 30+ days, or nobody can name who checks it
- **Metrics without definitions** — numbers that mean different things to different people
- **Vanity metrics** — feel good but don't drive decisions (e.g., total signups ever)
- **Coverage gaps** — critical areas with no analytics (e.g., no funnel analysis on signup flow)
- **Duplicate metrics** — same metric calculated differently in different places
- **Broken pipelines** — scheduled reports that fail silently

### Step 4: Present Audit Results

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

```
## Analytics Audit

**Dashboards found:** [N] | **Reports found:** [N] | **Active:** [N] | **Stale:** [N]

### Inventory
| Name | Tool | Last Modified | Used By | Verdict |
|------|------|--------------|---------|---------|
| [name] | [Metabase/Grafana/etc] | [date] | [who/nobody] | [keep/kill/update] |
| ...    | ...                    | ...    | ...          | ...                |

### Issues Found
- [N] dashboards with no recent access — candidates for removal
- [N] metrics without clear definitions
- [N] vanity metrics that don't drive decisions
- [coverage gap] — [critical area with no analytics]

### Recommendations

**Keep** (valuable, maintained):
- [dashboard] — [why it's valuable]

**Kill** (unused, stale, or misleading):
- [dashboard] — [why: no users / broken data / vanity metric]

**Update** (valuable concept, needs work):
- [dashboard] — [what needs fixing]

**Add** (missing coverage):
- [area] — [why it matters, what to measure]
```

Be direct about what to kill. Fewer, better dashboards beat many neglected ones.

## 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.


---
Source attribution: tonone-ai
Original project: https://github.com/tonone-ai/tonone/blob/1ceec80367a4e846e2f209cc87eea9d7544bd978/skills/lens-audit/SKILL.md
License: MIT
License information: https://opensource.org/license/mit
Original upstream instructions; downloaded from Mega AI Hub.

## Upstream license notice

MIT License

Copyright (c) 2026 tonone-ai

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.



# Mega AI Hub resource metadata

Creator / publisher: tonone-ai
Original project: https://github.com/tonone-ai/tonone/blob/1ceec80367a4e846e2f209cc87eea9d7544bd978/skills/lens-audit/SKILL.md
Attribution basis: Source repository record

Fields of work: Data & Analytics, Marketing, Operations, Product Management
Roles: Business Process Analyst, Data Analyst, Growth Marketer, Marketing Analyst, Product Manager
Specialties: API, Database
Tools: Amplitude, Docker, Ga4, Grafana, Metabase, Mixpanel, Posthog, Redash, Superset
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: 3da3bdc04f09aba400d8318ec41034b469a77bb08fc9a8aa767d057a8e045be7
