CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

minimalist-ui

Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.

60

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

Quality

Content

82%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.

An excellent, highly concrete design spec that assumes Claude's competence and delivers copy-usable values for every decision (typography, color, motion, components). Its main weaknesses are the redundant overview section, the absence of any verification step in the execution protocol, and no worked example to anchor the aesthetic.

Suggestions

Delete or shrink Section 1 ('Protocol Overview') — it restates the frontmatter description — and trim rhetorical sentences to their prescriptive core.

Add a compact worked example (one hero section or bento card with the specified fonts, colors, and motion) so the rules can be seen applied end-to-end.

Consider moving the full component and palette specifications into a references file, keeping SKILL.md as the overview and typography/motion directives.

DimensionReasoningScore

Conciseness

The body is a dense prescriptive spec with no concept explanations and every token carrying a concrete value, but Section 1 ('Protocol Overview') largely restates the description, and a few rhetorical flourishes ('Motion should feel invisible — present but never distracting') could be trimmed.

4 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: exact font stacks, hex pairs for accent and text colors, 'border: 1px solid #EAEAEA', 'cubic-bezier(0.16, 1, 0.3, 1)' over 600ms, Tailwind classes like 'py-24' and 'max-w-4xl', a usable picsum placeholder pattern, and a mandatory prefers-reduced-motion gate.

5 / 5

Workflow Clarity

Section 8 gives a clear ordered 7-step sequence (macro-whitespace → width constraint → typography/colors → borders → scroll animations → depth), but there are no validation or review checkpoints; the design-generation context means the destructive-operations cap does not apply.

4 / 5

Progressive Disclosure

A single, well-organized file with 8 clearly numbered sections and no bundle files, so navigation is easy; at ~82 lines it exceeds the under-50-line simple-skill exception, and detailed palette/component specs could plausibly be split into reference files.

4 / 5

Total

17

/

20

Passed

Description

58%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 clear, compact statement of the design aesthetic with concrete attributes, but it answers only 'what' and never 'when'. Adding an explicit 'Use when...' clause and everyday trigger terms (UI design, landing page, website) would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing or building web interfaces, landing pages, or UI components that should look clean and minimal.'

Include natural everyday phrasings users actually say — 'UI design', 'web design', 'landing page', 'minimalist website' — alongside the current design vocabulary.

State what artifacts the skill applies to (HTML, React, Tailwind, Vue) so the 'what' covers the deliverable, not just the style.

DimensionReasoningScore

Specificity

The description lists several concrete design attributes — 'Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows' — but presents traits rather than actions and omits what artifacts it applies to, so it falls short of comprehensive 5-level coverage.

4 / 5

Completeness

The 'what' is clear (clean editorial-style interfaces with a defined aesthetic), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It includes some genuinely natural design keywords ('editorial-style', 'bento grids', 'muted pastels') but misses the most common user phrasings such as 'UI design', 'web design', 'landing page', or 'minimalist website', so coverage stops at relevant-but-incomplete.

3 / 5

Distinctiveness Conflict Risk

The niche aesthetic and vocabulary ('warm monochrome', 'bento grids', 'editorial') are fairly distinct from generic skills, with only minor overlap risk against other frontend/design skills since no usage boundary is drawn.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Leonxlnx/taste-skill

Path

skills/minimalist-skill/SKILL.md

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.