CtrlK
BlogDocsLog inGet started
Tessl Logo

dashboard-redesign

Redesign a dashboard, KPI view, operational console, or analytical workspace around real decisions and data meaning. Trigger on "redesign this dashboard", "redesign this report", "clean up this analytics view", "improve these KPIs", or "fix this reporting view". Use ux-ui-audit for diagnosis without redesign and design-system-review for library-wide component issues. Do not invent metrics or thresholds.

78

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 exceptionally well-crafted instruction-only skill: lean body, concrete templates with examples, explicit per-phase validation checkpoints, and clean one-level-deep reference structure. It respects Claude's competence while remaining highly actionable.

DimensionReasoningScore

Conciseness

Dense, procedural guidance with no padding or basic-concept explanation (it never explains what a dashboard or KPI is); every section and checkpoint earns its place relative to the genuinely complex task.

5 / 5

Actionability

Provides copy-paste-ready templates (the decision matrix 'Decision | Signal | Comparison | Grain | Freshness | Action | Failure cost' and component spec 'Purpose | Content | Representation | Interaction | States | Responsive rule | Accessibility') with worked synthetic examples; code absence is appropriate for this instruction-only skill.

5 / 5

Workflow Clarity

Seven clearly sequenced phases each ending in an explicit Checkpoint, with feedback loops such as 're-check until every unresolved semantic question is explicitly marked' and a closing quality-bar checklist.

5 / 5

Progressive Disclosure

Overview SKILL.md points to four well-signaled, one-level-deep references (dashboard-models, visualization-and-metrics, interaction-accessibility-qa, worked-example), all of which exist as real files with no nested references.

5 / 5

Total

20

/

20

Passed

Description

95%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: third-person, explicit trigger phrases, and proactive disambiguation from sibling skills. The only minor weakness is specificity, where a single primary verb (redesign) carries the load rather than several distinct production actions.

DimensionReasoningScore

Specificity

Names the domain (dashboard/KPI/console/workspace) and concrete actions ('Redesign... around real decisions and data meaning') plus routing and a guardrail, but relies on a single primary production verb rather than multiple distinct actions.

4 / 5

Completeness

Explicitly answers both what ('Redesign a dashboard... around real decisions and data meaning') and when (concrete 'Trigger on' phrases), matching the anchor for clear what-and-when with concrete triggers.

5 / 5

Trigger Term Quality

'Trigger on "redesign this dashboard", "redesign this report", "clean up this analytics view", "improve these KPIs", "fix this reporting view"' provides five natural user phrases with synonyms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche in dashboard redesign, and it actively reduces conflict by routing adjacent needs to sibling skills ('Use ux-ui-audit for diagnosis without redesign and design-system-review for library-wide component issues').

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
aditya-ariosity/ux-ui-skills
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.