writing-vizro-yaml

Use this skill when writing or debugging Vizro YAML dashboard configurations — component syntax, data_manager registration, custom function wiring, filter/parameter setup, or AG Grid tables. Activate when the user is building a Vizro app, encountering YAML or runtime errors, or asking about Vizro component patterns.

1.73x

Quality

100%

Does it follow best practices?

Impact

92%

1.73x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

100%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 well-structured reference skill body: concise, actionable code patterns and imports up front, a quick-referable mistakes list, and clean one-level-deep navigation to a verified deep-dive file. It respects token budget while remaining immediately usable.

Dimension	Reasoning	Score
Conciseness	The body is lean: a numbered mistakes list, copy-paste YAML/Python snippets, an imports block, and a navigation table — no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Provides fully executable YAML patterns (scatter, kpi_card, dash_ag_grid, filter) and exact import lines, plus concrete mistake fixes like '_target_: custom_charts.my_chart' and 'column: "Version #"'.	3 / 3
Workflow Clarity	This is a single-purpose reference skill (write/debug Vizro YAML) with an unambiguous lookup flow: scan the Critical Mistakes list, then use the Deep Dive table to locate the exact reference section. No destructive/batch operation is involved, so the absence of validation checkpoints does not cap the score.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview with a single one-level-deep reference (references/yaml-reference.md, verified to exist) and a navigation table mapping each need to a specific section heading, making discovery easy.	3 / 3
	Total	12 / 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, third-person description that states concrete capabilities and gives explicit activation triggers tied to natural user phrasing. It is concise, domain-specific, and clearly distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'component syntax, data_manager registration, custom function wiring, filter/parameter setup, or AG Grid tables' — each naming a specific capability rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('writing or debugging Vizro YAML dashboard configurations — ...') and when ('Activate when the user is building a Vizro app, encountering YAML or runtime errors...').	3 / 3
Trigger Term Quality	Covers natural trigger phrasings a user would actually say: 'building a Vizro app', 'YAML or runtime errors', and 'Vizro component patterns', plus 'writing or debugging Vizro YAML'.	3 / 3
Distinctiveness Conflict Risk	'Vizro' is a narrow, well-defined niche with distinct triggers (Vizro app, AG Grid tables, data_manager), making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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/writing-vizro-yaml/SKILL.md
Commit: 49f0d2b

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.