CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

94

1.73x
Quality

Does it follow best practices?

Impact

92%

1.73x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A tight, actionable quick-reference that offloads detail to a single well-signaled reference file with a helpful navigation table. Its only gap is the absence of an explicit debug/verify workflow sequence with checkpoints, which keeps workflow_clarity at 2.

Suggestions

Add a short debugging workflow sequence (e.g., reproduce the error -> check against the Critical Mistakes list -> fix one mistake at a time -> re-run and verify the chart renders) with an explicit validation step.

Include a minimal end-to-end runnable snippet or app skeleton so users can validate a configuration loads without external context.

Note how to surface runtime errors (e.g., where Vizro logs blank-chart or type-mismatch failures) to make the verification loop concrete.

DimensionReasoningScore

Conciseness

The body is lean and high-signal — one-liner mistakes, compact YAML patterns, an import block, and a navigation table — with no padding explaining what Vizro or YAML is, assuming Claude's competence throughout.

3 / 3

Actionability

Provides copy-paste-ready executable YAML (scatter, kpi_card, ag_grid, filter), concrete import lines, and specific corrective prescriptions like '_target_: custom_charts.my_chart, not _target_: my_chart'.

3 / 3

Workflow Clarity

Content is well-organized but this is a reference catalog rather than a sequenced process; it lacks an explicit multi-step workflow with validation/checkpoint steps (e.g., run app, verify charts render, re-check) for the debugging use case.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview with one-level-deep, clearly-signaled references to the real file references/yaml-reference.md, plus a 'search for' navigation table mapping needs to reference sections.

3 / 3

Total

11

/

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-style description that states concrete capabilities and gives explicit activation triggers tied to natural user phrasing. It is concise yet comprehensive and clearly distinguishable from other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'writing or debugging Vizro YAML dashboard configurations — component syntax, data_manager registration, custom function wiring, filter/parameter setup, or AG Grid tables' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Answers both what (the enumerated configuration tasks) and when via the explicit trigger clause 'Activate when the user is building a Vizro app, encountering YAML or runtime errors, or asking about Vizro component patterns.'

3 / 3

Trigger Term Quality

Covers natural terms a user would actually say — 'building a Vizro app', 'YAML or runtime errors', 'AG Grid tables', 'Vizro component patterns' — giving good coverage of natural trigger language.

3 / 3

Distinctiveness Conflict Risk

The Vizro YAML dashboard niche with Vizro-specific triggers (data_manager, dash_ag_grid, Vizro app) is clearly distinct and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 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.