CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

designing-vizro-layouts

Use this skill when designing or building Vizro dashboard layouts — grid configuration, component sizing, filter/parameter placement, selector types, or container patterns. Activate when the user is creating wireframes, defining page structure, placing controls, or sizing charts.

96

1.53x
Quality

95%

Does it follow best practices?

Impact

100%

1.53x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-structured guidelines body that puts only decision rules inline and delegates examples and detail to a single clearly-signaled reference. The only gap is the absence of a minimal complete grid YAML example in the body itself.

Suggestions

Add one minimal copy-paste-ready grid YAML example (a page Grid with a couple of components and -1 empty cells) to the Core Rules section so the common case is executable without loading the reference.

Show the exact form of 'just provide the column name to Filter' with a one-line YAML snippet in the Selectors section to make the default-selector rule fully executable.

DimensionReasoningScore

Conciseness

Every line is Vizro-specific constraint or judgment guidance (e.g. 'Use `-1` for empty cells', 'Charts need at least 2–3 rows to avoid looking squeezed'); nothing re-explains concepts Claude already knows and no section is padded.

5 / 5

Actionability

Highly concrete guidance — 12 columns, 140px rows, a component sizing table, and a data-type-to-selector mapping with examples — but no complete grid YAML snippet in the body; the executable examples live only in the reference file, a minor gap.

4 / 5

Workflow Clarity

Qualifies for the simple-skill exception (under 50 lines, single task): applying the layout constraints is unambiguous, and the 'Modifying existing layouts' rule gives a clear conditional branch. No destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

Core rules are inline with details split into references/layout-guidelines.md (verified to exist), linked three times with correct one-level-deep paths, and the 'Deep Dive' section enumerates exactly what the reference contains.

5 / 5

Total

19

/

20

Passed

Description

96%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, domain-anchored description that explicitly states what the skill does and when to activate it, with concrete natural-language triggers and no fluff. The only weakness is that a few triggers (wireframes, sizing charts) are tool-agnostic and could overlap with general visualization skills.

Suggestions

Tie the generic trigger phrases to the tool, e.g. 'creating Vizro wireframes' or 'sizing charts in a Vizro dashboard', to reduce overlap with general chart-design skills.

Consider naming the dashboard/.vizro YAML context in the 'when' clause so plain 'make me a dashboard' requests in other frameworks are less likely to trigger.

DimensionReasoningScore

Specificity

It enumerates multiple concrete capability areas — 'grid configuration, component sizing, filter/parameter placement, selector types, or container patterns' — covering both designing and building; comprehensive for the Vizro layout domain.

5 / 5

Completeness

Both questions are answered explicitly: what ('designing or building Vizro dashboard layouts — grid configuration, component sizing, ...') and when ('Activate when the user is creating wireframes, defining page structure, placing controls, or sizing charts').

5 / 5

Trigger Term Quality

Natural phrases users would actually say: 'dashboard layouts', 'wireframes', 'page structure', 'placing controls', 'sizing charts', spanning design- and build-time vocabulary without relying on jargon alone.

5 / 5

Distinctiveness Conflict Risk

'Vizro' anchors a clear niche, but generic triggers like 'creating wireframes' or 'sizing charts' could also fire for general (non-Vizro) chart or dashboard work — minor overlap risk with closely related visualization skills.

4 / 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

Path

vizro-e2e-flow/skills/designing-vizro-layouts/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.