CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

77

Quality

97%

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.

The body is an excellent skill document: lean and Vizro-specific, immediately actionable with copy-paste recipes, and cleanly split against a well-signaled one-level-deep reference whose section targets check out. The only notable gap is the absence of an explicit post-wiring verification step; there is also a small duplication error in the target list ('vm.Graph, vm.Table, vm.Figure, vm.Table').

Suggestions

Add a brief verification step after wiring an interaction (e.g., 'Run the app, click the source component, and confirm the target updates — a silent no-op usually means a missing custom_data or a wrong controls id') to close the workflow_clarity gap.

Fix the duplicated 'vm.Table' in the target-components list in the 'Core concept' section (line 14) — one instance should presumably be a different component or be removed.

DimensionReasoningScore

Conciseness

The body is dense with non-inferable, Vizro-specific knowledge (set_controls mechanics, custom_data for non-positional columns, filter_interaction removed in 1.0.0, Flex-vs-Grid layout rationale) and never explains concepts Claude already knows; every section earns its tokens, fitting the 'lean and efficient' anchor rather than anchor 4's trimmable over-explanation.

5 / 5

Actionability

It provides four copy-paste-ready recipes (export button, cross-filter, actions chain, cross-page drill-through with back button), a correct-vs-wrong example for built-in action wiring, exact flags in the gotchas, and a key-imports block — covering the common cases across all five patterns.

5 / 5

Workflow Clarity

The Source → Control → Target steps and the explicit decision-flow tree give a clear, sequenced process, and gotchas flag build-time failure modes (ValueError without show_in_url). However, there is no verification checkpoint after wiring an interaction (e.g., run the app and click to confirm the target updates), which keeps it below the anchor-5 'explicit validation steps' bar.

4 / 5

Progressive Disclosure

SKILL.md stays an overview (concepts, pattern table, quick recipes) while full templates, wireframes, and the mistakes table live in references/actions-reference.md, referenced one level deep with a need-to-'Search for' navigation table whose target headings (## Pattern 1–4, ## Common Implementation Mistakes) all exist in the bundle.

5 / 5

Total

19

/

20

Passed

Description

100%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.

The description is exemplary: it names the domain and every concrete interaction type the skill covers, gives explicit 'what' and 'when' clauses with natural user phrasings, and is tightly scoped to Vizro so conflict risk is minimal. Voice is appropriately impersonal and there is no padding.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'adding cross-filter, cross-highlight, drill-through, or data export interactions', 'choosing the right interaction pattern during design', 'implementing actions in code', 'cross-page navigation with pre-set filters', 'download data' — comprehensively covering all interaction families the skill handles, matching the anchor-5 pattern rather than the 'minor gaps' of anchor 4.

5 / 5

Completeness

It explicitly answers both questions: 'what' (design-phase pattern selection plus code implementation of the four interaction types) and 'when' ('Use this skill when adding...' and 'Activate when the user wants clicks on a chart or table to filter or highlight...'), with concrete trigger phrases as in the anchor-5 example.

5 / 5

Trigger Term Quality

Natural trigger phrasing is comprehensive: 'cross-filter', 'cross-highlight', 'drill-through', 'data export', 'clicks on a chart or table to filter or highlight other charts, tables, or figures', 'download data', and 'Vizro dashboard', with synonyms covered (export/download, filter/cross-filter).

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — interaction wiring for Vizro dashboards specifically — with distinct triggers (cross-filter, drill-through, cross-page navigation), so it is unlikely to fire for the wrong skill.

5 / 5

Total

20

/

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

Path

vizro-e2e-flow/skills/wiring-vizro-actions/SKILL.md

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.