CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-design-system

UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.

Quality

76%

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 ./.claude/skills/ui-design-system/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A concise, well-structured overview that documents its single bundle script accurately and executable-ly. The weakness is scope mismatch: four of the five claimed core capabilities (component architecture, responsive calculations, accessibility, handoff documentation) have no actionable guidance or workflow, leaving the reader knowing only how to run the token generator.

Suggestions

Add a worked example invocation with real values (e.g., python scripts/design_token_generator.py "#0066CC" modern css) plus a brief sample of the output structure so the common case is copy-paste ready.

Provide concrete guidance, a mini-workflow, or a pointer for the other claimed capabilities (component system architecture, responsive calculations, accessibility compliance, developer handoff), or narrow the Core Capabilities list to what the skill actually instructs.

Add next-step/validation checkpoints after token generation, such as reviewing the generated palette for contrast compliance or confirming the export format matches the project's stack.

DimensionReasoningScore

Conciseness

Lean ~28-line body with no explanations of concepts Claude already knows; however the 'Professional toolkit for creating and maintaining scalable design systems.' tagline and the Features bullets duplicating Core Capabilities are minor padding that could be trimmed, so it sits at anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

The one documented command — 'python scripts/design_token_generator.py [brand_color] [style] [format]' with enumerated styles (modern, classic, playful) and formats (json, css, scss) — is genuinely executable, but only one of the five claimed core capabilities has any executable guidance, and there is no worked example with real values or sample output, making the gaps more than minor (anchor 3 rather than 4).

3 / 5

Workflow Clarity

The single documented action (invoking the token generator) is unambiguous, but no sequence is given for the broader claimed workflow (gathering brand input, generating, reviewing, exporting), no example run is shown, and no validation or next-step checkpoints exist; the simple-skill exception does not apply cleanly because the body claims multiple capabilities beyond the one script, placing this at anchor 3.

3 / 5

Progressive Disclosure

The body is under 50 lines, well-organized into 'Core Capabilities' and 'Key Scripts' sections, and references exactly the one real bundle file (scripts/design_token_generator.py) with a correct relative path and accurate CLI documentation verified against the script — matching the rubric's guidance that a short, well-sectioned skill with no need for external references scores 5.

5 / 5

Total

15

/

20

Passed

Description

75%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 solid description that names four concrete capabilities and includes an explicit 'Use for...' clause with task-based triggers. Its main limitations are missing common synonyms (e.g., 'style guide', 'brand colors') and a 'when' clause that largely restates the 'what' rather than adding distinct trigger phrases.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — 'design token generation, component documentation, responsive design calculations, and developer handoff tools' — mirroring the anchor-4 pattern of several specific actions with minor gaps; not a 5 because coverage is not comprehensive and 'developer handoff tools' is slightly generic.

4 / 5

Completeness

Has a clear 'what' (token generation, component documentation, responsive calculations, handoff tools) and an explicit 'Use for creating design systems, maintaining visual consistency...' clause, so both are present; the 'when' largely mirrors the 'what' and lacks concrete user-mention triggers, keeping it below anchor 5.

4 / 5

Trigger Term Quality

Includes natural phrases users would say — 'design system', 'design tokens', 'visual consistency', 'design-dev collaboration' — giving good keyword coverage, but common variations like 'style guide', 'brand colors/palette', or 'UI kit' are missing, so it falls short of the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

'UI design system' is a clear niche with distinct triggers (tokens, visual consistency, design-dev handoff); only minor overlap risk with closely related frontend/CSS styling skills, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

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

maslennikov-ig/claude-code-orchestrator-kit

Path

.claude/skills/ui-design-system/SKILL.md

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.