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.

99

1.23x
Quality

Does it follow best practices?

Impact

96%

1.23x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A well-structured, multi-step design skill: concise overview with concrete REQUIRED OUTPUT actions, explicit validation checkpoints between steps, and clean one-level-deep progressive disclosure into real bundle files and sibling skills.

DimensionReasoningScore

Conciseness

Lean, instruction-dense body with checklists and decision tables; no padding with concepts Claude already knows and every section earns its place.

3 / 3

Actionability

Highly actionable for an instruction-only skill: REQUIRED OUTPUT directives (copy template from assets/X to spec/X, fill placeholders, save before proceeding), explicit checklists, and a data-shape→pattern decision flow.

3 / 3

Workflow Clarity

Steps 1–3 are explicitly sequenced ("each step depends on the prior") with a tracked progress block and a Validation Checklist gating each transition, plus partial-context routing rules.

3 / 3

Progressive Disclosure

Overview body points one level deep to verified bundle files (assets/*.md templates, references/*.md deep dives) and to sibling skills, with a closing Reference Files table for easy navigation.

3 / 3

Total

12

/

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 description that states concrete capabilities, gives explicit natural-language triggers for both what and when, and carves out a distinct niche by explicitly distinguishing the design/planning phase from the dashboard-build implementation skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions/components — "Enforces a 3-step workflow (requirements, layout, visualization)" — naming the specific sub-steps rather than vague language.

3 / 3

Completeness

Explicitly answers what ("Enforces a 3-step workflow...") 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

Natural user phrasing is well covered ("design or plan a dashboard", "create, design, or plan a dashboard", "Vizro dashboards") — terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Clear niche (Vizro dashboard design/planning) and it explicitly disambiguates from the dashboard-build skill ("For implementation, use the dashboard-build skill after completing Steps 1-3"), minimizing conflict.

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.