design-system

Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/design-system/SKILL.md

Quality

Content

63%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 action-oriented, well-commanded skill body that would benefit from trimming redundancy and tightening its file structure. The main weaknesses are inlined content that belongs in references and a number of referenced paths that are absent from the actual bundle.

Suggestions

Move the detailed Slide System section into a reference file (e.g. references/slide-system.md) and keep SKILL.md as an overview with a pointer, improving progressive disclosure.

Reconcile referenced paths: either add the missing assets/, data/, docs/, and templates/ files or remove/qualify the references so navigation matches the real bundle.

Add an explicit 'if validation fails, fix and re-run' loop after the slide-token-validator.py step and drop the redundant Best Practices restatement of rules already stated above.

Dimension	Reasoning	Score
Conciseness	Mostly dense and useful (tables, commands, code), but the Best Practices section restates the Token Compliance and Slide Requirements rules, and the Duarte sparkline aside explains a concept Claude already knows.	3 / 5
Actionability	Provides concrete runnable commands ('node scripts/generate-tokens.cjs ...', 'python scripts/search-slides.py ...') and complete Chart.js/CSS examples; minor gaps such as the abstract decision-flow steps keep it just short of fully copy-paste ready.	4 / 5
Workflow Clarity	The Contextual Decision Flow is a clear 5-step sequence ending in a validation step (slide-token-validator.py), but it lacks an explicit validate->fix->retry feedback loop.	4 / 5
Progressive Disclosure	The References and Scripts tables cleanly signal the real bundle files, but the large Slide System section is inlined rather than split into a reference, and many referenced paths (assets/, data/*.csv, docs/, templates/) do not exist in the bundle.	3 / 5
	Total	14 / 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, capability-dense description with an explicit trigger clause and clear niche. It is held at 4 rather than 5 because the 'when' guidance omits concrete user-mention phrasing and a few natural synonyms are missing.

Suggestions

Add user-mention triggers, e.g. 'Use when the user asks for design tokens, a token architecture, theme variables, or brand-compliant slides.'

Include common synonyms like 'theme', 'design system', and 'CSS variables / custom properties' to broaden trigger coverage.

Lead with action verbs (e.g. 'Generates', 'Validates', 'Defines') instead of noun phrases to sharpen specificity.

Dimension	Reasoning	Score
Specificity	Names several concrete capabilities ('Token architecture, component specifications, and slide generation', 'Three-layer tokens', 'CSS variables', 'spacing/typography scales') rather than vague abstractions, though they are noun phrases rather than crisp actions.	4 / 5
Completeness	Clearly states what the skill does and provides an explicit 'Use for ...' trigger clause, but the 'when' lacks the 'when the user mentions ...' phrasing that would lift it to the top anchor.	4 / 5
Trigger Term Quality	Includes natural user-facing terms like 'design tokens', 'systematic design', and 'brand-compliant presentations'; misses common synonyms such as 'theme' or 'design system' itself.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear design-systems-plus-slides niche with distinct triggers; only minor overlap risk with a generic ui-styling or presentation skill.	4 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 5 missing, 2 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: nextlevelbuilder/ui-ux-pro-max-skill
Path: .claude/skills/design-system/SKILL.md
Commit: f232671

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.