selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, or building KPI cards for Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, or is creating KPI metric cards.
91
87%
Does it follow best practices?
Impact
97%
1.38xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with clear 'when' triggers and good domain-specific terminology. Its main weakness is that the capability descriptions are somewhat categorical rather than listing granular concrete actions. The description also uses second person ('Use this skill when...') which is a minor style issue, though the rubric specifically penalizes first/second person in the specificity dimension.
Suggestions
List more specific concrete actions, e.g., 'Recommends optimal chart types (bar, line, scatter, etc.) for given data shapes, creates custom Plotly Express chart functions, configures hex colors and categorical/sequential palettes, builds KPI metric cards with delta indicators.'
Rephrase to third person voice: 'Guides chart type selection, applies Plotly Express conventions...' instead of 'Use this skill when...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Vizro dashboards) and several actions (choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards), but these are more like categories of activity than concrete, specific actions. It doesn't list granular operations like 'create bar charts, configure color scales, add annotations'. | 2 / 3 |
Completeness | The description clearly answers both 'what' (choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards for Vizro dashboards) and 'when' (explicit 'Activate when...' clause with specific trigger scenarios like asking which chart fits their data, needing custom chart functions, etc.). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'chart types', 'Plotly Express', 'colors', 'palettes', 'KPI cards', 'Vizro dashboards', 'custom chart functions', 'metric cards'. These are terms a user working with Vizro would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of Vizro dashboards, Plotly Express, and KPI cards creates a very specific niche. This is unlikely to conflict with generic charting or dashboard skills due to the explicit mention of Vizro and Plotly Express as the framework context. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that efficiently covers chart selection, Plotly conventions, color rules, custom charts, and KPI cards for Vizro dashboards. Its main weakness is the lack of executable code examples, particularly for the @capture('graph') custom chart pattern which is described as needed for 'most bar and line charts' — a concrete example would significantly improve actionability. The progressive disclosure and conciseness are excellent.
Suggestions
Add a concrete, executable @capture('graph') code example showing pre-aggregation for a bar chart, since the skill emphasizes most charts need this pattern and the absence of an example is the biggest actionability gap.
Add a brief KPI card usage example showing the _target_/title pattern to make that section copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and information-dense. No unnecessary explanations of what Plotly or Vizro are. The table format for chart selection is maximally efficient, and rules are stated as direct imperatives without padding. | 3 / 3 |
Actionability | Provides concrete rules and conventions (e.g., color rules, KPI card usage, when to use @capture), but lacks executable code examples. A custom chart function example with @capture('graph') showing aggregation would make this significantly more actionable, especially given the emphasis on how most bar/line charts need it. | 2 / 3 |
Workflow Clarity | For this type of skill (decision-making guidance rather than multi-step destructive operations), the workflow is clear: select chart type → apply Plotly conventions → handle colors → decide if custom chart needed → use KPI cards correctly. The decision criteria for @capture('graph') are explicit, and the 'Never' constraints serve as validation guardrails. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview covering all key topics, then a clearly signaled single-level reference to chart-best-practices.md for extended details. The 'Deep Dive' section explicitly lists what the reference file contains, making navigation easy. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- mckinsey/vizro
- Commit
27d4055
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.