CtrlK
BlogDocsLog inGet started
Tessl Logo

clean

Simplicity-focused design with ample whitespace, legible typography, and a limited color palette to reduce visual clutter.

63

Quality

75%

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/clean/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, well-structured, and actionable guideline-authoring skill: concrete tokens and scales, enumerated component states, a numbered workflow, and a QA checklist, all without over-explaining concepts Claude already knows. It is self-contained and appropriately organized for a skill of this scope.

DimensionReasoningScore

Conciseness

The body is terse and list-driven with no padding of concepts Claude already knows (it never explains what typography, WCAG, or color tokens are); the only minor redundancy is the Brand line restating the frontmatter, so it earns the lean-and-efficient anchor rather than the padded anchor 2.

3 / 3

Actionability

Guidance is concrete and specific — real token values (#3B82F6), a typography scale (12/14/16/20/24/32), an 8pt spacing grid, enumerated required states, a defined output structure, and explicit constraint language ("Use 'must' for non-negotiable rules"); per the rubric's instruction-only note, the absence of code is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

The six-step Guideline Authoring Workflow gives a clear sequence (intent → tokens → anatomy → accessibility → anti-patterns → QA checklist) with the QA checklist serving as the explicit verification checkpoint; the task is not destructive/batch so the missing-validation cap does not apply.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the skill is a single self-contained file organized into well-labeled sections, matching the rubric's simple-skills allowance that well-organized content with no external references scores 3.

3 / 3

Total

12

/

12

Passed

Description

50%

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 articulates a clear aesthetic (simplicity, whitespace, legible typography, limited palette) but frames it as a style statement rather than a capability, with no "when to use" trigger guidance. It is specific enough to avoid being generic yet stops short of actionable, trigger-rich language.

Suggestions

Reword to lead with concrete actions the skill performs, e.g. "Authors implementation-ready design-system guidelines for a clean, minimal aesthetic using semantic tokens and accessibility standards."

Add an explicit trigger clause such as "Use when creating or reviewing design-system guidelines for clean, minimal UIs, or when the user mentions whitespace, limited color palettes, or minimal design."

Include natural trigger terms users would say ("clean design", "minimal UI", "design system", "design tokens") to improve discoverability and reduce overlap with other design skills.

DimensionReasoningScore

Specificity

It names concrete design attributes ("ample whitespace, legible typography, and a limited color palette") but describes a visual style rather than concrete actions the skill performs, so it falls short of the multi-action anchor 3 yet is not vague like the anchor-1 example.

2 / 3

Completeness

It conveys a partial "what" (the clean aesthetic) but offers no "Use when..." clause or explicit trigger guidance, so per the rubric's cap rule completeness cannot exceed 2.

2 / 3

Trigger Term Quality

Relevant descriptive keywords appear (whitespace, typography, color palette), but these are style attributes rather than natural phrases a user would utter to invoke the skill (e.g. "clean design" or "minimal UI"), matching the "some relevant keywords but missing common variations" anchor.

2 / 3

Distinctiveness Conflict Risk

The clean/minimal aesthetic niche is somewhat specific but lacks distinct triggers and could overlap with other design-style skills, fitting the "somewhat specific but could still overlap" anchor.

2 / 3

Total

8

/

12

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
bergside/awesome-design-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.