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.

79

Quality

100%

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%

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

A compact, well-structured instruction skill: concrete layout and chart guidance, a clear sequenced workflow with a validation self-check, and a precise output contract. It respects the token budget while remaining fully actionable.

DimensionReasoningScore

Conciseness

Lean and efficient: concrete constraints ('220–260px', '6–8 nav links', '~10 lines of polyline') with no padding or re-explanation of concepts Claude already knows. Not a 2 because nothing is superfluous or in need of tightening.

3 / 3

Actionability

Gives executable specifics — CSS Grid + Flexbox, semantic tags, data-od-id slug, inline-SVG chart construction, and a complete artifact template — rather than vague direction. Not a 2 because the guidance is concrete and copy-paste oriented, including the output contract.

3 / 3

Workflow Clarity

A clearly sequenced 6-step workflow ending in a Self-check section that acts as an explicit validation checklist (tokens, accent usage, sticky bars). The self-check provides the verification checkpoint the top anchor expects.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent); the body is self-contained and organized into clear Workflow and Output-contract sections, which per the rubric's simple-skill note earns a 3 without external file references.

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 tight, third-person description that states concrete deliverable regions and gives an explicit, natural-language trigger clause. It fully answers both what the skill produces and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete deliverable structures — 'single HTML file', 'Fixed left sidebar', 'top bar with user/search', 'main grid of KPI cards and one or two charts' — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (an admin/analytics dashboard with named regions) and when (an explicit 'Use when...' clause), matching the top anchor.

3 / 3

Trigger Term Quality

The 'Use when the brief asks for a "dashboard", "admin", "analytics", or "control panel" screen' clause covers natural terms a user would actually say. Not scored below because it lacks only minor colloquial variants; not scored above the ceiling.

3 / 3

Distinctiveness Conflict Risk

Scoped to a single-screen admin/analytics dashboard with distinct triggers and third-person voice, making it unlikely to fire for the wrong skill. Not a 2 because the niche and triggers are clearly delimited.

3 / 3

Total

12

/

12

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.

Validation15 / 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.