CtrlK
BlogDocsLog inGet started
Tessl Logo

component-design

Apply a coherent visual system, responsive behavior, interaction states, and accessibility to Kun components.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/component-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

The body is a tight, well-structured overview with a sequenced workflow, explicit validation step, and a completion-gates checklist; its main limitation is that the guidance, while specific, stops short of copy-paste-ready examples or an explicit error-recovery loop.

DimensionReasoningScore

Conciseness

The body is a lean ~34 lines with no padding and no explanation of concepts Claude already knows; every section (Tool routing, Workflow, Completion gates, Boundaries, Delivery) earns its place, matching the 'lean and efficient; every token earns its place' anchor rather than the slightly-padded score-4 anchor.

5 / 5

Actionability

It gives concrete, specific guidance — naming exact tokens ('type, spacing, color, radius, and motion'), exact states ('hover, focus, active, disabled, loading, empty, success, and error'), and a concrete tool-routing table — so it is mostly actionable with only minor gaps; it stops short of fully copy-paste-ready examples, so not score 5.

4 / 5

Workflow Clarity

The five-step workflow is clearly sequenced and includes an explicit validation step ('Validate contrast, semantics, motion, and responsiveness') plus a 'Completion gates' checklist, fitting the 'clear sequence with most checkpoints present' anchor; it lacks an explicit error-recovery feedback loop, so it does not reach score 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files requiring external references, and is organized into clearly labeled sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery); per the simple-skills scoring note this qualifies for a 5 with well-organized sections.

5 / 5

Total

18

/

20

Passed

Description

53%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.

The description clearly states what the skill does and targets a specific niche, but it lacks any explicit 'Use when...' trigger guidance and relies on a single generic verb ('Apply'), which caps both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when styling or building Kun components, or when the user asks to make a component responsive, accessible, or visually consistent.'

Replace or supplement the generic 'Apply' with concrete actions users would recognize ('Style', 'Theme', 'Add interaction states to', 'Audit accessibility of').

Include natural synonyms users actually say (design system, theming, component styling) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Quotes 'Apply a coherent visual system, responsive behavior, interaction states, and accessibility to Kun components' — it names the domain plus four specific facets, but the only action verb is the generic 'Apply', so it sits at the 'names domain and 1-2 concrete actions' level rather than listing multiple distinct concrete actions like the score-5 anchor.

3 / 5

Completeness

It clearly answers 'what' (apply visual system / responsive / states / accessibility to Kun components) but provides no 'Use when...' or equivalent explicit trigger guidance for 'when'; per the judging guidelines a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'visual system', 'responsive behavior', 'interaction states', 'accessibility', and 'Kun components' are relevant, but common natural phrasings a user would actually say ('design system', 'style this component', 'make it responsive') and synonyms are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The 'Kun components' niche plus the four named design facets make it mostly distinct with only minor overlap risk against closely related general design/styling skills, fitting the 'mostly distinct; minor overlap risk' anchor rather than the broader score-3 anchor.

4 / 5

Total

13

/

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
KunAgent/Kun
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.