CtrlK
BlogDocsLog inGet started
Tessl Logo

selecting-vizro-charts

Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or needs a tabular detail view.

91

1.53x
Quality

92%

Does it follow best practices?

Impact

86%

1.53x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written, well-structured skill body that uses tables and guardrails efficiently and routes detail to a real one-level reference. The main gap is actionability: the body offers concrete API conventions and rules but delegates executable code to references rather than including copy-paste snippets.

Suggestions

Add one small copy-paste executable snippet per major area (e.g. a minimal @capture("graph") bar-aggregation function and a vm.AgGrid dash_ag_grid factory) directly in the body so guidance is immediately runnable, not just referenced.

Show the canonical @capture("ag_grid") signature inline (with data_frame as the DataFrame argument name) instead of only describing it and linking to the dashboard-build skill.

Include a brief wrong-vs-right inline example for the most common footgun (raw vs pre-aggregated bar/line) so the rule is self-contained without loading the reference.

DimensionReasoningScore

Conciseness

Lean, dense tables and rules with no explanation of basic Plotly/Vizro concepts; the one inline rationale (raw px.bar stacking rows as separate rectangles) describes a genuine non-obvious footgun, not padding.

3 / 3

Actionability

Gives concrete API names and explicit 'Never' rules, but the body provides pattern-level guidance and references rather than complete copy-paste executable code blocks, so it is not fully copy-paste ready.

2 / 3

Workflow Clarity

A data-question→chart decision table plus 'Use when' criteria and 'Never' guardrails give an unambiguous selection flow; this is a selection/guidance skill rather than a destructive multi-step operation, so the absence of validate→fix loops is acceptable.

3 / 3

Progressive Disclosure

Well-organized overview body with clearly signaled one-level-deep references to the verified references/chart-best-practices.md and a dedicated 'Deep Dive' section stating when to load it.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit 'Use when'/'Activate when' triggers covering both capabilities and activation conditions. It clearly occupies a distinct Vizro-charting niche with natural trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid)' — matching the score-3 anchor of several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('choosing chart types... adding tables') and when via 'Use this skill when...' and 'Activate when...' trigger clauses.

3 / 3

Trigger Term Quality

Uses natural user phrasing ('which chart fits their data', 'set colors or palettes', 'KPI metric cards', 'tabular detail view') with good coverage of variations a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped to Vizro dashboard chart/table/color/KPI work with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
mckinsey/vizro
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.