CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dashboard-build

Use this skill to build, implement, and test Vizro dashboards (Phase 2). Activate when the user wants to create a working app, says "just build it", or has data ready for implementation. Requires spec files from the dashboard-design skill (Phase 1), or user confirmation to skip design.

83

1.28x
Quality

89%

Does it follow best practices?

Impact

95%

1.28x

2 of 3 eval scenarios. Add 1 more for a full score.

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.

An excellent instruction-style skill body: every step is executable, validation and feedback loops are explicit, and detail is properly pushed into well-signaled reference files. The only trimmable cost is redundant repetition of the terminal-handling warning.

DimensionReasoningScore

Conciseness

The body is command-dense with no concept re-teaching (no 'what is Vizro' padding) and every guideline earns its place, but terminal-handling warnings are repeated 3-4 times ('ABSOLUTELY NEVER type ANY commands...', 'NEVER run any commands in that terminal', plus a checklist item) and could be consolidated. It is noticeably above the midpoint anchor but not fully lean.

4 / 5

Actionability

Fully executable throughout: exact commands ('uv run ./scripts/get_model_json_schema.py <model_name> <model_name2> ...', 'uv pip install playwright && uv run playwright install --with-deps chromium'), a copy-the-example-app starting strategy, validation scripts with flags (--custom-colors-requested), and concrete failure signatures to look for (Callback error messages, _dash-update-component 500s).

5 / 5

Workflow Clarity

Clear two-step sequence (Build, Testing) with explicit validation checkpoints (validation scripts, pre-Step-2 checklist, 'Done When' criteria), feedback loops ('go back to Step 1 to fix any issues, then come back here'), and a smart batch-fix/restart loop for browser testing that prevents one-error-at-a-time thrash.

5 / 5

Progressive Disclosure

Core workflow stays in SKILL.md while details are split one level deep into real, existing files (custom_charts_guide.md, data_management.md, example apps, schema scripts, asset templates), and the closing Reference Files table with a 'When to Load' column makes navigation trivial.

5 / 5

Total

19

/

20

Passed

Description

82%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 description with an explicit when-clause, natural trigger phrases, and clear Phase 1/Phase 2 differentiation from its sibling design skill. The main weakness is voice: 'Use this skill to build...' reads as second person, and the action list (build/implement/test) could be more concrete about capabilities.

DimensionReasoningScore

Specificity

The description names the domain and concrete actions ('build, implement, and test Vizro dashboards'), which would rate 4, but the rubric guideline penalizes second-person voice by 1: 'Use this skill to build...' implicitly addresses the reader as 'you', unlike the third-person anchors ('Processes files', 'Extract text and tables from PDF files').

3 / 5

Completeness

Explicitly answers both: what ('build, implement, and test Vizro dashboards (Phase 2)') and when ('Activate when the user wants to create a working app, says "just build it", or has data ready for implementation'), matching the anchor's concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases ('create a working app', 'just build it', 'has data ready for implementation') alongside 'Vizro dashboards', but misses common variations like 'make a dashboard', 'visualize data', or 'Plotly app'.

4 / 5

Distinctiveness Conflict Risk

'Vizro dashboards (Phase 2)' carves a clear niche, and the explicit boundary against the dashboard-design Phase 1 skill minimizes wrong-skill triggering; only 'create a working app' is slightly generic but is anchored by the Vizro context.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

mckinsey/vizro

Path

vizro-e2e-flow/skills/dashboard-build/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.