CtrlK
BlogDocsLog inGet started
Tessl Logo

design-system

Govern and validate design-system changes. Use when tokens, typography, spacing, iconography, themes, or style aliases need repository-grounded evidence.

64

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

Quality

Content

71%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 well-structured, token-efficient, and uses progressive disclosure effectively with verified reference files. Its main gap is actionability: the workflow and validation guidance is abstract and lacks the specific commands or examples needed to execute design-system checks.

Suggestions

Add concrete validation commands (e.g. the actual repo design-system check script or test invocation) to the Validation section instead of the generic "run the smallest command or test".

Furnish at least one executable example in the Workflow or Examples section, such as a token-layer lookup command or a sample contract.yaml snippet showing a token resolution.

Consolidate overlapping guidance across Philosophy, Avoid, and Anti-Patterns to remove redundancy and tighten the token budget further.

DimensionReasoningScore

Conciseness

The body is a lean bullet-list of directives with no padding or explanation of concepts Claude already knows, though Philosophy and Anti-Patterns overlap somewhat with Avoid/Constraints and could be trimmed.

4 / 5

Actionability

Guidance is directional and concrete in places ("Start with 2-3 focused surfaces", "identify the layer") but lacks specific commands or code, and Validation only says "run the smallest command" without naming the actual checks.

3 / 5

Workflow Clarity

The Workflow section gives a clear sequenced set of steps and the Validation section supplies a fail-fast checkpoint with a feedback loop, though checkpoints live in a separate section rather than inline in the sequence.

4 / 5

Progressive Disclosure

A dedicated Progressive Disclosure section points to real one-level-deep references (references/contract.yaml, evals.yaml, task-profile.json, all present) plus clearly signaled deferred-context paths, giving easy navigation from an overview.

5 / 5

Total

16

/

20

Passed

Description

82%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 cleanly answers both what and when with domain-specific trigger terms and minimal conflict risk. Its only weakness is that the stated actions ("govern", "validate") are somewhat abstract rather than a comprehensive set of concrete operations.

DimensionReasoningScore

Specificity

"Govern and validate design-system changes" names the domain plus two actions, but "govern" and "validate" are high-level rather than a comprehensive list of concrete operations, matching the anchor that names the domain with 1-2 concrete actions.

3 / 5

Completeness

It explicitly states what ("Govern and validate design-system changes") and when ("Use when tokens, typography, spacing, iconography, themes, or style aliases need repository-grounded evidence") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"tokens, typography, spacing, iconography, themes, or style aliases" are natural terms users say with good synonym coverage, though there are no file-extension style triggers typical of a 5.

4 / 5

Distinctiveness Conflict Risk

The design-system niche with specific token/theme/alias triggers is clearly distinct from other skills and unlikely to fire for the wrong skill, matching the clear-niche anchor.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
jscraik/Agent-Skills
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.