CtrlK
BlogDocsLog inGet started
Tessl Logo

minimalist-ui

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

60

Quality

68%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/minimalist-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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 highly actionable, concrete design protocol with exact values and a clear execution sequence. Its main gap is the absence of explicit validation checkpoints in the workflow, though the skill's generative nature makes that gap moderate.

Suggestions

Add a verification checkpoint to the Execution Protocol (e.g., 'Audit the output against the Banned Elements list before finalizing') to close the workflow-validation gap.

Trim the occasional editorializing prose (e.g., 'The goal is quiet sophistication, not spectacle') to tighten conciseness further.

Consider extracting the long color and component specification tables into a referenced file once the skill grows, to preserve progressive disclosure.

DimensionReasoningScore

Conciseness

Dense and assumes Claude's competence without explaining basic concepts; every section delivers concrete directives, with only minor editorializing prose that does not materially pad the content.

3 / 3

Actionability

Provides exact, copy-paste-ready specifics: full font-family stacks, precise hex codes, and concrete CSS/Tailwind values like 'translateY(12px)' and 'cubic-bezier(0.16, 1, 0.3, 1)'.

3 / 3

Workflow Clarity

Section 8 offers a clear numbered 7-step sequence, but it lacks explicit validation or verification checkpoints for confirming the output meets the design constraints.

2 / 3

Progressive Disclosure

A single, well-organized SKILL.md with eight clearly delineated sections and no need for external bundle references; organization is clean and navigable.

3 / 3

Total

11

/

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 conveys a clear, specific design aesthetic but is framed as a style statement rather than a capability with explicit usage triggers. It lacks a 'Use when...' clause, capping completeness, and uses somewhat specialist vocabulary.

Suggestions

Add an explicit trigger clause such as 'Use when building minimalist editorial web interfaces or when the user requests clean, high-contrast UI designs.'

Reframe with concrete action verbs (e.g., 'Generates editorial-style web interfaces using...') instead of a pure style description.

Include more natural user-facing trigger terms (e.g., 'minimalist UI', 'clean website design', 'editorial layout') alongside the specialist design vocabulary.

DimensionReasoningScore

Specificity

Names concrete visual attributes ('Warm monochrome palette, typographic contrast, flat bento grids, muted pastels') but describes style qualities rather than explicit concrete actions the skill performs.

2 / 3

Completeness

Clearly states what the skill produces but provides no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes some relevant terms ('editorial-style interfaces', 'bento grids', 'gradients') but leans toward specialist design jargon rather than natural phrasing a user would commonly say.

2 / 3

Distinctiveness Conflict Risk

Targets a specific editorial-minimalism niche but could overlap with general UI/design skills and lacks distinct trigger phrasing.

2 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Leonxlnx/taste-skill
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.