Skill

lens-chart

Recommends BI chart types for analytics dashboards and data displays based on data types like sales trends or KPIs. Evaluates density, drill-down, real-time support in CLI format.

Python

Bash

design

data-engineering

npx claudepluginhub tonone-ai/tonone --plugin warden-threat

Tool Access

This skill is limited to using the following tools:

ReadBashGlobGrep

Preview

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

SKILL.md

Similar Skills

chart-type-recommender

2.0k

Provides step-by-step guidance, code, and configurations for chart type recommendations in data analytics workflows covering visualization, SQL queries, statistics, and BI.

5 tools

jeremylongshore-claude-code-plugins-plus-skills

charting

Guides full-stack data visualization: selects optimal charts for data and goals, engineers pipelines from databases to rendered charts, recommends libraries by scale, optimizes performance and accessibility.

bopen-tools

prism-chart

Recommends chart types, libraries (Chart.js, Recharts, D3, Plotly), accessibility grades, and fallbacks for data types like time series or comparisons. Useful for chart implementation requests.

4 tools

tonone

Stats

Stars35

Forks3

Last CommitApr 12, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

lens-chart — BI & Analytics Chart Selection

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

When to use

User needs chart type selection or visualization recommendations for analytics dashboards or BI contexts.

Workflow

Identify data type and BI context from user request (sales trends, cohort analysis, funnel, KPI comparison, etc.)

Search chart knowledge base:

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

Search style for BI context:

python3 -m lens_agent.uiux search --domain style --query "{context}" --limit 2

Evaluate for BI requirements: data density, drill-down capability, real-time support, library recommendation
Output optimized for decision-making, not decoration

Output format

┌─ BI Chart Recommendation — {data_type} ─────────────────────────────┐
│ Chart type:        {chart_type}                                      │
│ Library:           {library}                                         │
│ Data density:      {density} (low / medium / high)                  │
│ Drill-down:        {drill_down} (yes / no / limited)                │
│ Real-time support: {real_time} (yes / no)                           │
│ Accessibility:     {grade}                                           │
├─ Decision test ─────────────────────────────────────────────────────┤
│ "Does this answer a decision?" → {yes_no}: {rationale}              │
└──────────────────────────────────────────────────────────────────────┘

Anti-patterns

Never choose decorative over data-dense visualizations for BI contexts
Never skip the "does this answer a decision?" test — every chart must justify its inclusion
Never skip accessibility fallback for charts graded below AA
Never recommend real-time charts without confirming the data pipeline supports streaming

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.