CtrlK
BlogDocsLog inGet started
Tessl Logo

wiring-vizro-actions

Use this skill when adding cross-filter, cross-highlight, drill-through, or data export interactions to a Vizro dashboard — both for choosing the right interaction pattern during design and for implementing actions in code. Activate when the user wants clicks on a chart or table to filter or highlight other charts, tables, or figures, needs cross-page navigation with pre-set filters, or wants users to download data.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

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

Well-structured, actionable, and token-efficient content that moves detail into a single one-level-deep reference while keeping the overview navigable. The only minor gap is the absence of an explicit verification step after wiring an interaction.

Suggestions

Add a brief post-wiring sanity check (e.g. confirm the clicked control actually drives the target, or that show_in_url filters appear in the URL) to give the workflow an explicit verification checkpoint.

Consider noting how to verify a pattern choice is correct (re-check the decision flow's terminal branch) before committing to the code recipe.

DimensionReasoningScore

Conciseness

Lean throughout — it explains only Vizro-specific mechanics (Source→Control→Target, the vm.Action wrapping error) that Claude would not already know, and assumes competence for everything else; every section earns its place.

5 / 5

Actionability

Copy-paste-ready executable code for the common cases (export, cross-filter, actions chain, cross-page drill-through) with correct/wrong contrasts and concrete identifiers like control ids and show_in_url=True.

5 / 5

Workflow Clarity

The decision flow is an explicit gated sequence that walks from data shape to pattern choice, but there is no validate/verify feedback loop after wiring an action — acceptable since these are non-destructive interactions, leaving it just shy of the top anchor.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview that pushes full pattern templates into one-level-deep references/actions-reference.md, with a deep-dive navigation table mapping needs to section headers; referenced headers (Pattern 1–5, Common Implementation Mistakes) exist in the bundle.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 that pairs concrete capabilities with explicit activation triggers tied to a clearly named product niche. The only minor gap is natural-term synonym coverage for the triggers.

Suggestions

Add a few everyday synonyms a user might say (e.g. "click-to-filter", "interactive dashboard", "chart that updates other charts") to round out the trigger term coverage.

Optionally surface the most common trigger phrase earlier in the description so the dominant use case is unmissable.

DimensionReasoningScore

Specificity

Lists multiple concrete interaction types — "cross-filter, cross-highlight, drill-through, or data export" — plus both design ("choosing the right interaction pattern") and implementation ("implementing actions in code"), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers what (adding cross-filter/highlight/drill-through/export interactions to a Vizro dashboard) and when ("Activate when the user wants clicks on a chart or table to filter…") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasing is present ("clicks on a chart or table to filter or highlight other charts", "cross-page navigation with pre-set filters", "download data"), but it omits common synonyms and product-specific shorthand a user might say, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to "Vizro dashboard" interactions with distinct trigger language, so it occupies a clear niche with minimal overlap risk against generic dashboard or data skills.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.