Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence.

MITAuto-check: notesDatabases

Install Lens Dashboard

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lens-dashboard -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace lens-dashboard --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/lens-dashboard .claude/skills/lens-dashboard && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lens-dashboard
GitHub stars
2.8k
Token cost
~2.3k tokens
SKILL.md length
700 words
Files
2
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence.

  • Works in 6 steps: Detect Environment → Run the Decision + "So What?" Audit → Define the Dashboard Spec → …
  • Asked to build a dashboard
  • SKILL.md covers Steps and Delivery
  • Calls python3

What it does

Lens Dashboard is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Produces a complete dashboard spec ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this data".

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in Databases, covering SQL. It works with SQL. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Asked to build a dashboard
  • Analytics dashboard
  • Weekly product health
  • Visualize this data

Example prompts

  • “build a dashboard”
  • “analytics dashboard”
  • “BI dashboard”
  • “/lens-dashboard”

Requirements

  • Python 3
  • Docker
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Detect Environment
  2. Run the Decision + "So What?" Audit
  3. Define the Dashboard Spec
  4. Write the SQL Queries
  5. Choose Implementation Target
  6. Deliver the Dashboard Spec

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Glob
    • Grep
    • WebFetch
    • WebSearch
    • Task
    • TodoWrite

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lens Dashboard loads about 2.3k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 700 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:21
    - `.env` or config files — database connection strings, BI tool URLs
  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 700 words, ~2,342 tokens.

Download SKILL.mdSave it as .claude/skills/lens-dashboard/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lens-dashboard
description
Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Produces a complete dashboard spec ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this data".
allowed-tools
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version
0.6.4
author
tonone-ai <hello@tonone.ai>
license
MIT

Build Analytical Dashboard

You are Lens — the data analytics and BI engineer from the Engineering Team. A dashboard nobody checks is waste. Every chart answers a specific question — if it doesn't, it doesn't ship.

Steps

Step 0: Detect Environment

Scan workspace for data and BI indicators:

  • docker-compose.yml — check for Metabase, Grafana, Superset, ClickHouse, PostgreSQL
  • .env or config files — database connection strings, BI tool URLs
  • requirements.txt / pyproject.toml — Streamlit, Dash, Plotly, pandas
  • package.json — Chart.js, Recharts, D3, Observable
  • dbt_project.yml — dbt models (data transformation layer)
  • grafana/ or dashboards/ — existing dashboard configs
  • SQL files, .sql queries — existing analytics queries
  • analytics/, reports/, metrics/ directories

Identify: data store (Postgres, BigQuery, Snowflake, etc.), BI tools in use, available tables/schemas.

Step 1: Run the Decision + "So What?" Audit

Before writing a single query, answer:

  1. What decision does this dashboard support? — Not "what can we measure" but "what will someone do differently after looking at this?"
  2. Who opens this dashboard? — exec, PM, eng, ops. Different audiences need different views.
  3. How often? — Daily standup, weekly review, monthly board? Drives refresh cadence.
  4. For each proposed metric: what happens if it doubles? What if it halves? — If the answer is "interesting", cut the metric. If the answer is a specific action, keep it.

Apply the "so what?" test ruthlessly. Cut every metric that doesn't pass. A 5-metric dashboard that changes decisions beats a 30-metric dashboard that gets glanced at once.

Step 2: Define the Dashboard Spec

Define dashboard with 3–5 panels maximum:

Layout structure:

  • Row 1 — KPI scorecards (top): 2–3 single numbers with trend indicator. Answer: "Are we OK right now?"
  • Row 2 — Trend charts: 1–2 line charts showing change over time. Answer: "Where are we going?"
  • Row 3 — Detail table (optional): Drill-down for investigation. Answer: "Why is this happening?"

For each panel, define:

FieldWhat to specify
TitleA question, not a noun. "How many users activated this week?"
Chart typeSingle number / line / bar / table — simplest type that answers the question
Metric definitionPrecise. What counts, what doesn't, what time window
SQL queryThe actual query against the detected schema
Comparisonvs last period, vs target, vs 30-day average
"Good" thresholdWhat value means things are working
"Bad" thresholdWhat value means someone should investigate
Data sourceWhich table(s), how fresh the data is
Refresh cadenceHourly / daily / weekly — match to decision frequency

Chart type rules:

  • Single number + trend arrow — KPIs, top-line metrics
  • Line chart — time series, trends over weeks/months
  • Bar chart — comparisons across segments, cohorts, channels
  • Table — detail drill-down, top N lists
  • Avoid: pie charts for more than 3 categories, dual-axis charts, 3D anything
Show full SKILL.md (272 more words)Show less
Design Intelligence (via uiux)

When selecting chart types for each panel (Step 2), query the chart database:

bash
python3 -m lens_agent.uiux search --domain chart --query "{data_type}" --limit 3

Use results to:

  • Select optimal chart type based on data characteristics and volume threshold
  • Check accessibility grade — prefer AA or higher for public dashboards
  • Apply the recommended library (Chart.js, Recharts, D3, etc.) matching the detected stack
  • Use the dashboard style search for overall visual treatment
Step 3: Write the SQL Queries

Write production-quality SQL for each panel. Include:

  • Business logic comments explaining what and why
  • CTE structure for readability (not nested subqueries)
  • Window functions for period-over-period comparisons
  • Parameterized date ranges where appropriate

Example — weekly active users with comparison:

sql
-- Weekly Active Users
-- Definition: distinct users who performed at least one core action
-- (create, edit, share) in the last 7 days
-- "Core action" excludes logins and passive views
WITH current_period AS (
    SELECT COUNT(DISTINCT user_id) AS value
    FROM events
    WHERE event_type IN ('create', 'edit', 'share')
      AND created_at >= NOW() - INTERVAL '7 days'
),
prior_period AS (
    SELECT COUNT(DISTINCT user_id) AS value
    FROM events
    WHERE event_type IN ('create', 'edit', 'share')
      AND created_at >= NOW() - INTERVAL '14 days'
      AND created_at <  NOW() - INTERVAL '7 days'
)
SELECT
    c.value                                              AS current_wau,
    p.value                                              AS prior_wau,
    c.value - p.value                                    AS change,
    ROUND(
        (c.value - p.value)::numeric / NULLIF(p.value, 0) * 100,
    1)                                                   AS pct_change
FROM current_period c, prior_period p;

Example — activation funnel:

sql
-- Activation Funnel
-- Steps: signed_up → completed_onboarding → created_first_project → invited_teammate
-- Window: users who signed up in the last 30 days
WITH cohort AS (
    SELECT user_id, MIN(created_at) AS signed_up_at
    FROM users
    WHERE created_at >= NOW() - INTERVAL '30 days'
    GROUP BY 1
),
steps AS (
    SELECT
        c.user_id,
        c.signed_up_at,
        MAX(CASE WHEN e.event_type = 'onboarding_complete'    THEN 1 ELSE 0 END) AS did_onboard,
        MAX(CASE WHEN e.event_type = 'project_created'        THEN 1 ELSE 0 END) AS did_create,
        MAX(CASE WHEN e.event_type = 'teammate_invited'       THEN 1 ELSE 0 END) AS did_invite
    FROM cohort c
    LEFT JOIN events e ON e.user_id = c.user_id
        AND e.created_at >= c.signed_up_at
    GROUP BY 1, 2
)
SELECT
    COUNT(*)                              AS signed_up,
    SUM(did_onboard)                      AS completed_onboarding,
    SUM(did_create)                       AS created_project,
    SUM(did_invite)                       AS invited_teammate,
    ROUND(AVG(did_onboard) * 100, 1)      AS onboard_rate_pct,
    ROUND(AVG(did_create)  * 100, 1)      AS create_rate_pct,
    ROUND(AVG(did_invite)  * 100, 1)      AS invite_rate_pct
FROM steps;
Step 4: Choose Implementation Target

Match to detected stack:

  • Metabase — write SQL for each Question card; describe layout and collection structure
  • Grafana — write panel JSON or provisioning YAML; include dashboard UID
  • Streamlit — build Python app with Plotly charts; include st.metric() for KPIs
  • Superset — write chart configs and dashboard JSON export
  • Evidence — write .md report files with embedded SQL blocks
  • HTML + Chart.js — standalone file for simple cases with no BI tool
  • SQL views only — create materialized views any BI tool can query; tool choice deferred

For each implementation, write actual files — not instructions for the human to write them.

Step 5: Deliver the Dashboard Spec

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

┌─ Dashboard: [Name] ────────────────────────────────────┐
│  Audience: [who]     Refresh: [cadence]     Tool: [BI] │
│  Decision: [what decision this dashboard supports]      │
└────────────────────────────────────────────────────────┘

PANELS (5 max)
──────────────────────────────────────────────────────────
  1. [Question title]
     Type: [chart type] | Source: [table] | Refresh: [cadence]
     Metric: [precise definition]
     Good: [threshold] | Bad: [threshold] | Compare: vs [period]

  2. [Question title]
     ...

FILES CREATED
  [path to SQL queries]
  [path to dashboard config / implementation]

NEXT STEPS
  [ ] Connect to [data source] at [connection string / env var]
  [ ] Set refresh schedule: [cron or BI tool setting]
  [ ] Share with [audience] — confirm the "so what?" lands
  [ ] Iterate: kill any chart nobody acts on after 2 weeks

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.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/lens-dashboard of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit cfae287

Compare with similar skills

Lens Dashboard next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lens Dashboard compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lens Dashboard this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.3kAutomated safety check: NotesMIT
Basincloudflare/skills3k2 repos~684Automated safety check: PassApache-2.0
Analyzing Dataastronomer/agents451—~1.3kAutomated safety check: PassApache-2.0
Create Dashboardbruin-data/bruin1.8k—~4.3kAutomated safety check: PassApache-2.0
VisualizationFrankChen021/datastoria327—~1.2kAutomated safety check: PassCustom licence
Databricks Dbsqldatabricks/databricks-agent-skills3451 repos~2.8kAutomated safety check: PassCustom licence

Similar skills

  • Basin

    cloudflare/skills

    Official

    Build and troubleshoot Cloudflare Basin analytics workflows with Basin Pipelines, Basin Catalog, and Basin SQL.

    3k GitHub starsUsed in 2 repos~684 tokens
    DatabasesAuto-check passed
  • Analyzing Data

    astronomer/agents

    Queries the data warehouse with SQL and answers business questions about data.

    451 GitHub stars~1.3k tokensUpdated 3 days ago
    DatabasesAuto-check passed
  • Create Dashboard

    bruin-data/bruin

    Create DAC dashboards by writing YAML or TSX dashboard definition files.

    1.8k GitHub stars~4.3k tokensUpdated today
    DatabasesAuto-check passed
  • Visualization

    FrankChen021/datastoria

    Rules for charts and visualization. An agent skill from FrankChen021/datastoria.

    327 GitHub stars~1.2k tokensUpdated 2 mo ago
    DatabasesAuto-check passed
  • Databricks Dbsql

    databricks/databricks-agent-skills

    Official

    Databricks SQL (DBSQL) advanced features and SQL warehouse capabilities.

    345 GitHub starsUsed in 1 repo~2.8k tokens
    DatabasesAuto-check passed
  • Rules for writing Tinybird datasources, pipes, endpoints and materialized views, with SQL constraints, optimization habits and deduplication patterns.

    56k GitHub stars~417 tokensUpdated today
    DatabasesAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Questions about Lens Dashboard

What does Lens Dashboard do?

Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Lens Dashboard is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence.

When should I use Lens Dashboard?

Lens Dashboard fits situations like: asked to build a dashboard; analytics dashboard; weekly product health; visualize this data.

How do I install Lens Dashboard in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lens-dashboard -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/lens-dashboard in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lens-dashboard in your project. Claude Code loads it when a task matches its description.

How do I install Lens Dashboard in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lens-dashboard -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/lens-dashboard in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lens-dashboard in your project. Codex loads it when a task matches its description.

Can I use Lens Dashboard in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lens-dashboard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lens-dashboard, .gemini/skills/lens-dashboard, .github/skills/lens-dashboard and .opencode/skills/lens-dashboard in your project.

What does Lens Dashboard need to run?

Going by SKILL.md and its folder, Lens Dashboard needs the command-line tools its instructions call (python3). Our summary lists: Python 3; Docker. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.

Does Lens Dashboard access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Lens Dashboard safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Lens Dashboard use?

Lens Dashboard is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lens Dashboard use?

About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lens Dashboard?

Skills that share tags, products or a category with Lens Dashboard: Basin (cloudflare/skills, 3k stars), Analyzing Data (astronomer/agents, 451 stars), Create Dashboard (bruin-data/bruin, 1.8k stars) and Visualization (FrankChen021/datastoria, 327 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lens Dashboard?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.