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.
91
87%
Does it follow best practices?
Impact
96%
1.77xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description that clearly defines its role within a two-phase workflow, includes natural trigger phrases, and explicitly states when to activate. Its main weakness is that the specific capabilities (build, implement, test) could be more granular—listing concrete actions like generating layout code, configuring data sources, or running test suites would strengthen specificity. The use of second-person 'Use this skill' is borderline but follows an imperative/instructional voice rather than true second person.
Suggestions
Add more specific concrete actions beyond 'build, implement, and test'—e.g., 'generate Vizro app code, configure chart components, set up data pipelines, run dashboard tests'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Vizro dashboards) and some actions (build, implement, test), but doesn't list specific concrete actions like 'create charts', 'configure layouts', 'set up data connections'. The actions are somewhat generic verbs applied to a specific domain. | 2 / 3 |
Completeness | Clearly answers both what ('build, implement, and test Vizro dashboards') and when ('when the user wants to create a working app, says "just build it", or has data ready for implementation'). Also specifies prerequisites (spec files from Phase 1 or user confirmation to skip), which adds useful context. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'build', 'implement', 'test', 'Vizro dashboards', 'just build it', 'data ready for implementation', 'working app'. These cover natural phrases a user would say when they want to move from design to implementation. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: specifically Phase 2 of Vizro dashboard building, clearly differentiated from the Phase 1 'dashboard-design' skill. The explicit phase numbering and dependency on spec files make it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides clear, actionable guidance for building Vizro dashboards. Its main strengths are the concrete commands, YAML output templates, validation checklists, and well-organized progressive disclosure. The only notable weakness is some redundancy in terminal handling warnings and occasional verbosity in emphasis formatting, though these serve a safety purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and contains necessary domain-specific guidance, but includes some redundant emphasis (e.g., the terminal warning is repeated multiple times across different sections) and some instructions that could be tightened. The bold/caps warnings, while important, add verbosity. | 2 / 3 |
Actionability | Provides concrete, executable commands (e.g., `uv run ./scripts/get_model_json_schema.py <model_name>`), specific file paths, exact YAML output templates, and clear references to scripts and example files. The guidance is copy-paste ready and leaves little ambiguity about what to do. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with numbered steps, explicit validation checklists before proceeding between phases, feedback loops (iterate on Step 1 from Step 2), and clear 'Done When' criteria. The workflow includes error recovery guidance (restart dashboard on failure, fix and re-validate). | 3 / 3 |
Progressive Disclosure | Content is well-structured with a clear overview, steps broken into logical phases, and a well-organized reference table at the bottom pointing to one-level-deep external files (custom_charts_guide.md, data_management.md, example_app.py) and related skills. No deeply nested references. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- mckinsey/vizro
- Commit
124060f
- 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.