This skill is an empty placeholder containing only a TODO comment and no actual instructions. It provides zero value in its current state — no actionable guidance, no workflow, no examples, and no references to supporting materials.

Suggestions

Add concrete instructions describing what 'compiling a design system from code' means — e.g., which files to scan, what tokens/components to extract, and what output format to produce.

Include executable code examples or commands showing how to parse design tokens from source files (e.g., extracting colors, typography, spacing from CSS/JS/TS files).

Define a clear multi-step workflow: 1) discover source files, 2) extract design tokens, 3) validate extracted data, 4) generate the compiled design system output.

If the skill involves multiple output formats or advanced features, create supporting reference files and link to them from the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The content is essentially empty — a TODO placeholder with no actual instructions. While it's not verbose, it provides zero useful content, so it cannot be considered 'lean and efficient' in any meaningful sense.	1 / 3
Actionability	There is no concrete guidance, no code, no commands, and no examples. The entire body is a TODO placeholder with no actionable content whatsoever.	1 / 3
Workflow Clarity	No workflow, steps, or process is described. There is nothing to evaluate for sequencing or validation checkpoints.	1 / 3
Progressive Disclosure	No structure, no references, no organization. The skill is a single TODO line with no content to disclose progressively.	1 / 3
	Total	4 / 12 Passed

Description

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too terse and vague to be effective for skill selection. It lacks concrete actions, explicit trigger conditions, and natural keyword coverage. Without a 'Use when...' clause and specific capability listing, Claude would struggle to reliably choose this skill over others.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks to generate a design system, extract design tokens, or document UI components from a codebase.'

List specific concrete actions such as 'Extracts color tokens, typography scales, spacing values, and component patterns from source code to produce a structured design system.'

Include natural trigger terms users would say, such as 'style guide', 'design tokens', 'theme', 'UI components', 'component library'.

Dimension	Reasoning	Score
Specificity	The description uses vague language — 'compiles design system from code' names a domain loosely but does not list any concrete actions (e.g., extracting tokens, generating component docs, building style guides).	1 / 3
Completeness	The description weakly addresses 'what' and completely omits 'when' — there is no 'Use when...' clause or any explicit trigger guidance.	1 / 3
Trigger Term Quality	'Design system' and 'code' are somewhat relevant keywords a user might mention, but common variations like 'style guide', 'tokens', 'components', 'theme', or 'UI library' are missing.	2 / 3
Distinctiveness Conflict Risk	'Design system from code' is somewhat specific to a niche, but the vagueness means it could overlap with general code analysis, documentation generation, or UI-related skills.	2 / 3
	Total	6 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

about 1 month ago

Table of Contents

Discovery Implementation Validation