CtrlK
BlogDocsLog inGet started
Tessl Logo

minimal

Stripped-back design emphasizing whitespace, clean typography, and restrained color for maximum clarity and focus.

52

Quality

58%

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

Quality

Content

81%

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 well-structured, largely lean instruction skill with concrete design tokens, a clear sequenced authoring workflow, and a QA checklist. Its main weaknesses are an empty Brand section, some principle redundancy, and the absence of a worked output example.

DimensionReasoningScore

Conciseness

The body is mostly lean bullet directives that assume Claude's competence, but principles like accessibility priority and "opinionated, concise" recur across Rules, Expected Behavior, and Quality Gates, and the empty "## Brand" section adds a small inefficiency.

2.5 / 3

Actionability

Concrete tokens (hex colors, spacing scale 4/8/12/16/24/32, named fonts/weights), a defined output structure, and specific directives ("Use 'must' for non-negotiable rules") make the guidance actionable, but no worked example of generated output and the empty Brand section leave it just short of fully concrete.

2.5 / 3

Workflow Clarity

The Guideline Authoring Workflow is a clear 6-step numbered sequence terminating in an executable QA checklist, reinforced by the Quality Gates validation checks; this is guideline authoring rather than a destructive/batch operation, so no retry feedback loop is required.

3 / 3

Progressive Disclosure

The self-contained body is organized into clear, well-labeled sections with no nested references and no external files needed, but the empty "## Brand" header and minor cross-section redundancy keep it just below the cleanly-organized level-3 bar.

2.5 / 3

Total

10.5

/

12

Passed

Description

36%

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 characterizes a minimal design aesthetic but fails to state the skill's actual capability or when to invoke it, missing the natural "minimal design" trigger and any "Use when" guidance. It is distinguishable only loosely and reads as a style statement rather than a capability statement.

Suggestions

Lead with the skill's action, e.g. "Authors minimal design-system guidelines...", so the 'what' is explicit instead of an aesthetic description.

Append a "Use when..." clause naming natural triggers such as "minimal design", "minimalist UI", "clean/restrained design systems".

Replace the uncommon "stripped-back" phrasing with terms users actually say ("minimal", "minimalist", "clean") to improve trigger coverage.

DimensionReasoningScore

Specificity

The phrase "Stripped-back design emphasizing whitespace, clean typography, and restrained color" names a domain and concrete aesthetic properties but lists no capability actions (no verbs like generate, author, or apply), so it sits between the vague-no-action anchor (1) and the names-actions anchor (2).

1.5 / 3

Completeness

It conveys a topic (minimal design) but never states what the skill does (author design-system guidelines), and there is no "Use when..." trigger at all; the missing explicit when clause and weak what place it below the level-2 cap.

1.5 / 3

Trigger Term Quality

Terms like "whitespace", "clean typography", and "restrained color" are somewhat natural, but the most common trigger ("minimal design" / "minimalist") is absent from the description and "stripped-back" is uncommon phrasing, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The restrained/whitespace aesthetic niche is reasonably specific, but it could overlap with general design-system or branding skills and lacks explicit triggers that would prevent misfiring.

2 / 3

Total

7

/

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.