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

79%

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 ./cli/assets/skills/design-system/SKILL.md

Quality

Content

75%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 well-organized, actionable skill body that pairs executable commands with clear reference routing. The main weaknesses are an implicit validation feedback loop and a heavy inline Slide System section that could be partly offloaded to a reference.

Suggestions

Make the slide-generation feedback loop explicit: after 'Validate with slide-token-validator.py', add 'If errors: fix tokens/markup and re-validate; only proceed when validation passes.'

Move the bulk of the Slide System detail (CSV schemas, Chart.js integration) into a references/slide-system.md file and keep SKILL.md as a pointed overview.

Resolve the Templates table: either add the missing templates/ directory with design-tokens-starter.json, or remove the dangling entry.

Dimension	Reasoning	Score
Conciseness	The body is dense and table/code-driven with little concept restating, but the Slide System section inlines substantial detail (CSV listings, Chart.js snippet, token-compliance CSS) that leans slightly past lean; minor trimming would reach a 5.	4 / 5
Actionability	Provides copy-paste commands ('node scripts/generate-tokens.cjs --config tokens.json -o tokens.css', 'python scripts/search-slides.py "investor pitch" --context --position 2 --total 9') and executable HTML/CSS examples, with minor gaps such as the unstated direct usage of generate-slide.py and the missing templates path.	4 / 5
Workflow Clarity	The 'Contextual Decision Flow' gives a clear numbered 1–5 sequence with a validation step ('Validate with slide-token-validator.py'), but the validate→fix→retry feedback loop is only implicit rather than spelled out, keeping it just below a 5.	4 / 5
Progressive Disclosure	Structure is good: a References table signals all seven real reference files one level deep, and a Scripts table maps bundled scripts; however the large inline Slide System section and a Templates entry (design-tokens-starter.json) with no corresponding bundle folder represent minor organization gaps.	4 / 5
	Total	16 / 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, mostly third-person description that names concrete capabilities and an explicit use clause. Its main gap is the 'when' trigger phrasing, which is explicit but not as user-utterance-oriented as the top anchor.

Suggestions

Add concrete user-utterance triggers to the 'when' clause, e.g. 'Use when the user asks for design tokens, a token system, brand-compliant slides, or a Tailwind theme.'

Include natural synonyms/extensions (e.g. 'design tokens, CSS variables, .css token files') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Token architecture, component specifications, and slide generation' plus 'Three-layer tokens... CSS variables, spacing/typography scales, component specs, strategic slide creation' — giving comprehensive coverage of actions.	5 / 5
Completeness	Both 'what' (token architecture, component specs, slide generation) and 'when' ('Use for design tokens...') are present and explicit, but the 'when' lacks the 'when the user mentions X' concrete trigger phrasing that would warrant a 5.	4 / 5
Trigger Term Quality	'Use for design tokens, systematic design, brand-compliant presentations' offers good natural keyword coverage, but misses common synonyms and concrete file-extension triggers, so it stops short of a 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — design tokens, systematic design, brand-compliant presentations — with distinct triggers and minimal overlap with unrelated skills.	5 / 5
	Total	18 / 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: 6 missing, 2 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: nextlevelbuilder/ui-ux-pro-max-skill
Path: cli/assets/skills/design-system/SKILL.md
Commit: 09170ee

Reviewed: 2 hours 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.