CtrlK
BlogDocsLog inGet started
Tessl Logo

dashboard

Admin / analytics dashboard in a single HTML file. Fixed left sidebar, top bar with user/search, main grid of KPI cards and one or two charts. Use when the brief asks for a "dashboard", "admin", "analytics", or "control panel" screen.

72

Quality

88%

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

The canonical home for this skill is dashboard in nexu-io/open-design

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 exemplary single-file skill body: terse, concrete, and immediately executable, with a well-sequenced workflow and a built-in self-check. The only weakness is that the self-check checklist has no explicit error-recovery loop, which caps workflow clarity at 4.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — e.g. 'Charts: inline SVG only, no JS libraries. A line chart is ~10 lines of <polyline> with a subtle area fill.' It assumes Claude's competence (no explanation of what CSS Grid or semantic HTML are) and every instruction earns its place, matching the top anchor.

5 / 5

Actionability

Fully concrete, executable guidance: pixel ranges ('Left sidebar (220–260px)'), counts ('6–8 nav links', '3–4 KPI cards'), a copy-paste-ready <artifact> output block, and a specific self-check checklist. For an instruction-only skill this matches the top anchor.

5 / 5

Workflow Clarity

A clear 6-step sequence (Read DESIGN.md → Classify → Lay out → Write → Charts → Self-check) with a terminal validation checklist ('Every color comes from DESIGN.md tokens', 'Accent used at most twice'). It lacks an explicit fix-and-retry feedback loop around the self-check, so it fits the 'most checkpoints, minor validation gaps' anchor rather than 5.

4 / 5

Progressive Disclosure

The body is under 50 lines, organized into clear sections (## Workflow, ## Output contract), and appropriately references injected context (the active DESIGN.md) rather than inlining it. No bundle files exist or are needed, so per the simple-skill guideline the well-organized single file matches the top anchor.

5 / 5

Total

19

/

20

Passed

Description

83%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: concrete structural detail of the deliverable, an explicit 'Use when' clause with natural trigger phrases, and a distinctive niche. Only minor gaps — slightly incomplete coverage of the output and a few missing trigger variations — keep it from full marks.

DimensionReasoningScore

Specificity

Names the domain and several concrete deliverable elements ('Fixed left sidebar', 'top bar with user/search', 'main grid of KPI cards and one or two charts'), matching the several-specific-actions anchor; not 5 because it omits coverage the body provides (secondary table row, design-system integration).

4 / 5

Completeness

Explicitly answers both what ('Admin / analytics dashboard in a single HTML file. Fixed left sidebar, top bar...') and when ('Use when the brief asks for a "dashboard", "admin", "analytics", or "control panel" screen') with concrete trigger phrases — a direct match for the top anchor.

5 / 5

Trigger Term Quality

Natural user terms ('dashboard', 'admin', 'analytics', 'control panel') appear in the description and are reinforced by a dedicated triggers list including 'admin panel' and Chinese variants; a few plausible phrasings ('reporting screen', 'KPI overview') are missing, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche (single-file admin/analytics dashboard UI) with distinct triggers and minimal conflict risk; 'analytics' alone carries minor overlap risk with generic data-analysis requests, matching the mostly-distinct anchor rather than 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.