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.

96

1.53x
Quality

Does it follow best practices?

Impact

86%

1.53x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A well-structured, token-efficient skill body that gives concrete Vizro-specific rules and decision tables, with extended material cleanly delegated to a real one-level-deep reference. It balances actionability with progressive disclosure and avoids restating knowledge Claude already has.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows; every line is an actionable rule, and the @capture("graph") rationale earns its place by explaining the non-obvious broken-chart failure mode rather than generic background.

3 / 3

Actionability

Provides exact import paths and API names (from vizro.themes import palettes, colors; vm.AgGrid; dash_ag_grid; kpi_card) plus concrete parameter constraints (data_frame not df), giving executable direction; the absence of a full inline code block is a deliberate disclosure choice rather than vagueness.

3 / 3

Workflow Clarity

As a decision/guidance skill, the single action is made unambiguous via the data-question-to-chart table and explicit "Never use" guardrails; no destructive batch operation is involved, so the simple-skill allowance applies.

3 / 3

Progressive Disclosure

The body is a concise overview that splits extended detail into references/chart-best-practices.md, which is verified one level deep with no nested references and is clearly signaled with descriptions of what each link contains.

3 / 3

Total

12

/

12

Passed

Description

100%

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, third-person description that clearly states both capabilities and explicit activation triggers tied to a distinct Vizro-dashboard niche. It avoids vague language and over-claims while naming concrete, natural trigger phrases.

DimensionReasoningScore

Specificity

Lists five distinct concrete actions — "choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid)" — matching the multi-action score-3 anchor rather than naming a domain with only some actions.

3 / 3

Completeness

Explicitly answers both what (the enumerated actions) and when via the "Use this skill when..." plus "Activate when..." trigger clause, matching the score-3 anchor with explicit triggers.

3 / 3

Trigger Term Quality

Natural user phrasings like "which chart fits their data", "set colors or palettes", "KPI metric cards", and "tabular detail view" give good coverage of terms a user would actually say, matching the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

The actions are bound specifically "to Vizro dashboards" with Vizro-specific triggers (AG Grid, Plotly Express, KPI cards), giving a clear niche unlikely to conflict with non-Vizro 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.