Vizro is an open-source Python toolkit for assembling data visualization applications from low-code configuration. It helps developers create dashboards and multi-page apps from charts, tables, controls, layouts, navigation, and interactions, with optional high-code customization. Catalogue add-ons support working with Vizro projects.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mckinsey/vizro --skill selecting-vizro-chartsgit clone --depth 1 https://github.com/mckinsey/vizroWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mckinsey/vizro/selecting-vizro-charts)<a href="https://agentmods.dev/skills/mckinsey/vizro/selecting-vizro-charts"><img src="https://agentmods.dev/badge/skills/mckinsey/vizro/selecting-vizro-charts/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mckinsey/vizro/selecting-vizro-charts"><img src="https://agentmods.dev/badge/skills/mckinsey/vizro/selecting-vizro-charts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00078 | $0.00910 |
| Opus 5.5 | $0.00031 | $0.00364 |
| Sonnet 5.5 | $0.00016 | $0.00182 |
| Haiku 4.5 | $0.00008 | $0.00091 |
Grade A, and why
selecting-vizro-charts scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 16d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vizro Chart Best Practices
Chart Selection
| Data question | Chart |
|---|---|
| Compare categories | Bar (horizontal preferred) |
| Trend over time | Line (12+ points) |
| Part-to-whole (simple) | Pie/donut (2–5 slices only) |
| Part-to-whole (complex) | Stacked bar |
| Distribution | Histogram or box |
| Correlation | Scatter |
Never use: 3D charts, pie with 6+ slices, dual Y-axis, bar charts not starting at zero.
Plotly Conventions
- Plotly Express does not aggregate. Pre-aggregate in
app.pyor custom chart functions. - Bar: sort by value (largest→smallest) unless time-based; always start at zero.
- Line: pre-aggregate and sort by x ascending.
- Remove axis title when ticks are self-explanatory. Remove legend title (keep items only).
Color Rules
- Plotly charts & KPI cards: Do not specify colors — no
marker_color, hex codes,color_discrete_map, orcolor_discrete_sequence. This applies even for categories with apparent semantic meaning. Only override when the user explicitly asks. - AG Grid: Does not pick up Vizro template colors automatically. Use
from vizro.themes import palettes, colorsfor cell styling. - See chart-best-practices.md for palette names and import patterns.
Custom Charts (@capture("graph"))
Use when: aggregation/sorting needed, update_layout()/update_traces() calls, reference lines, parameter-driven logic, dual-axis, multi-trace go.Figure(), shared legend control.
In practice, most bar and line charts need @capture("graph") functions that aggregate data inside. Inline px.bar(data_frame="raw", x="region", y="revenue") on detail-level data stacks individual rows as separate rectangles instead of summing — producing visually broken charts.
KPI Cards
- Use built-in
kpi_card/kpi_card_referencefromvizro.figuresinFiguremodel. - Never rebuild KPI cards as custom charts. Exception: strictly impossible with built-in (e.g. dynamic text).
- Titles go in figure args (
_target_: kpi_card→title:), not on the component.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 16d ago Changed 9e55e7c6df97
- 1mo ago First seen · 56 lines · 78 tokens per session scan A dcb10187c8bc
selecting-vizro-charts is a skill published in the GitHub repository mckinsey/vizro (3,810 stars, last pushed 3d ago), licensed Apache-2.0. It adds 78 tokens to every session and 910 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
developing-with-streamlit
Use for ALL Streamlit tasks: creating, editing, debugging, beautifying, styling, theming, optimizing, or deploying Streamlit apps. Also custom components, st.components.v2, HTML/JS/CSS work. Discovers and loads version-matched reference docs from the user's installed Streamlit (>=1.57). Triggers: streamlit, st.…
building-pydantic-ai-agents
Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), workspaces, structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydanticai, or asks to build an AI agent, add tools/capabilities, attach a workspace, defer capability…
marimo-pair
Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.
pydantic-ai-harness
Extend Pydantic AI agents with capabilities from pydantic-ai-harness -- the Coder coding agent, file and shell tools in local or sandboxed workspaces (Modal, E2B, Sprites, Daytona, smolvm, BoxLite), Code Mode, sub-agents and planning, memory and skills, context compaction, guardrails and spend limits, web research and…
fill-model-descriptions
Curate descriptions and provider-specific reasoning options and token limits in packages/llm-info/data/models.yml using models.dev, OpenRouter, and provider documentation. Use when the user asks to populate model descriptions, enrich the model catalog, or curate descriptions after running pnpm sync-models.
migrating-langchain-to-pydantic-ai
Migrate Python LangChain, LangGraph, or Deep Agents applications to Pydantic AI and, when the source uses harness features, Pydantic AI Harness. Use for LangChain agents, chains, LCEL, direct LangGraph graphs, persistence, interrupts, streaming, and createdeepagent projects with planning, filesystem or sandbox…