CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.23x
Quality

87%

Does it follow best practices?

Impact

96%

1.23x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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, highly actionable multi-step workflow with explicit validation gates and clean one-level-deep progressive disclosure. Its only weakness is mild redundancy from the duplicate reference table and some interaction detail that re-states what sibling skills already cover.

Suggestions

Remove or trim the trailing 'Reference Files' table, since every link it lists is already given inline at the relevant step — this would remove pure duplication.

Shorten the Step 2 'Source → Control → Target' and 'When NOT to use advanced interactions' paragraphs to a one-line pointer, as the wiring-vizro-actions skill already carries the full detail.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concepts Claude already knows, but the trailing Reference Files table re-lists links already given inline and the Source→Control→Target / 'when NOT to use' detail repeats material deferred to the wiring-vizro-actions skill, so it could be tightened.

2 / 3

Actionability

Gives concrete, copy-ready instructions — copy a named template from assets/ to spec/, delete a named section when filters suffice, specific validation checklist items, and exact skill-load directives — leaving no ambiguity about what to do at each step.

3 / 3

Workflow Clarity

The 3 steps are explicitly ordered, each gated by a 'REQUIRED OUTPUT: spec/...' artifact and a 'Validation Checklist' run 'BEFORE proceeding', with partial-context routing and a 'do not skip steps' rule — clear sequence with explicit checkpoints.

3 / 3

Progressive Disclosure

The body is an overview that pushes detail one level deep into real, clearly-signaled files (references/information_architecture.md, common_mistakes.md, wireframe_templates.md and assets/1-3), with a reference table mapping each file to when to load it — easy navigation, no nested-reference chains.

3 / 3

Total

11

/

12

Passed

Description

90%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, well-scoped description with explicit 'what' and 'when' triggers and a clear hand-off to a sibling skill. It is slightly short of maximal specificity only because it describes one governing behavior rather than enumerating several concrete actions.

DimensionReasoningScore

Specificity

Names the dashboard/Vizro domain and a concrete behavior ("Enforces a 3-step workflow (requirements, layout, visualization)"), but does not list multiple distinct concrete actions in the manner of the score-3 anchor; it stays at the 'domain and some actions' level.

2 / 3

Completeness

It explicitly answers both what ("Enforces a 3-step workflow (requirements, layout, visualization) before implementation") and when ("Use this skill first when the user wants to design or plan a dashboard" / "Activate when the user asks to create, design, or plan a dashboard").

3 / 3

Trigger Term Quality

Covers natural phrasings a user would actually say — "design or plan a dashboard", "create, design, or plan a dashboard", plus the specific "Vizro dashboards" — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche (dashboard design/planning for Vizro) and explicitly routes implementation away to "the dashboard-build skill after completing Steps 1-3", making conflict with sibling skills unlikely.

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.

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.