dashboard-design
Use this skill first when the user wants to design or plan a dashboard, especially Vizro dashboards. Enforces a 3-step workflow (requirements, layout, visualization) before implementation. Activate when the user asks to create, design, or plan a dashboard. For implementation, use the dashboard-build skill after completing Steps 1-3.
91
87%
Does it follow best practices?
Impact
99%
1.83xAverage 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 solid description that clearly communicates when to activate (dashboard design/planning) and distinguishes itself from the companion build skill. The 3-step workflow and Vizro mention add distinctiveness. The main weakness is that the specific actions within each step are not elaborated, and the description uses second-person framing ('Use this skill') which is directed at Claude rather than describing capabilities in third person, though this is a minor stylistic issue.
Suggestions
Expand the specificity of the 3-step workflow by briefly describing what each step produces (e.g., 'Gathers requirements via structured questions, designs page layouts with component placement, and selects appropriate chart types').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (dashboard design/planning) and mentions a 3-step workflow with step names (requirements, layout, visualization), but doesn't describe concrete actions in detail—e.g., what 'requirements' gathering entails or what layout planning produces. | 2 / 3 |
Completeness | Clearly answers both 'what' (enforces a 3-step workflow for dashboard design/planning) and 'when' ('Activate when the user asks to create, design, or plan a dashboard'), with explicit trigger guidance and even a handoff note to the build skill. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'design', 'plan', 'dashboard', 'Vizro', 'create'. These are terms users would naturally say when requesting dashboard planning help. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly distinguished from implementation/build skills by explicitly scoping to the planning phase and referencing the separate 'dashboard-build' skill for implementation. The Vizro mention and 3-step workflow make it highly distinct. | 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 well-structured planning skill with excellent workflow clarity, strong actionability through concrete YAML spec templates and validation checklists, and good progressive disclosure via clearly signaled references. Its main weakness is moderate verbosity—some sections could be tightened without losing clarity, particularly the interaction style guidance and navigation architecture diagram.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic concepts Claude already knows, but some sections are verbose—e.g., the design principles list and the navigation architecture tier diagram add moderate bulk. The interaction style paragraph could be tightened. Overall reasonable but not maximally lean. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready YAML templates for each step's output, specific validation checklists, clear decision trees for handling partial context, and explicit numbered options for user interaction. The guidance is specific and executable rather than abstract. | 3 / 3 |
Workflow Clarity | The 3-step workflow is clearly sequenced with explicit dependencies, each step has a required output file that must be saved before proceeding, and validation checklists serve as checkpoints. The partial-context handling provides clear branching logic. The 'do not skip steps' constraint and progress tracker add further rigor. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to external files (information_architecture.md, wireframe_templates.md, common_mistakes.md) and other skills (designing-vizro-layouts, selecting-vizro-charts). The reference table at the end provides excellent navigation with 'When to Load' guidance. | 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
e630476
- 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.