CtrlK
BlogDocsLog inGet started
Tessl Logo

sleek

Modern minimalist aesthetic with clean lines, intentional color palette, subtle interactions, and consistent spacing.

40

Quality

40%

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

Quality

Content

72%

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-organized, token-efficient instruction set with concrete design tokens and a clear authoring workflow, but it would be more actionable with a worked example and more robust with an explicit validation feedback loop.

DimensionReasoningScore

Conciseness

The body is a lean bullet-list with no padding or explanations of concepts Claude already knows; every section earns its place, though 'Rules', 'Expected Behavior', 'Quality Gates', and 'Example Constraint Language' overlap slightly.

3 / 3

Actionability

It gives concrete tokens (hex values, font weights, 8pt grid), an explicit output structure, and a list of required states, but provides no worked example of a finished guideline to model output against, leaving the guidance somewhat incomplete.

2 / 3

Workflow Clarity

The six-step 'Guideline Authoring Workflow' is clearly sequenced and backed by 'Quality Gates', but there is no explicit validate→fix→retry feedback loop and the checkpoints are implicit rather than enforced per step.

2 / 3

Progressive Disclosure

Content is self-contained in one well-sectioned file with no nested or multi-level references; for a compact single-file skill this organization is appropriate and easy to navigate.

3 / 3

Total

10

/

12

Passed

Description

7%

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 portrays the visual aesthetic rather than the skill's function and lacks any usage trigger, so it reads as brand copy rather than a skill description. It fails to tell a user or Claude what the skill does or when to reach for it.

Suggestions

Rewrite in third-person action voice stating what the skill does, e.g. 'Authors implementation-ready Sleek design-system guidelines defining tokens, components, states, and accessibility acceptance criteria.'

Append a 'Use when...' clause with natural triggers: 'Use when the user asks for Sleek design-system guidelines, brand/UI styling rules, component specs, or design-token documentation.'

Replace abstract aesthetic adjectives with concrete capability nouns ('design tokens', 'component states', 'QA checklists') so the description doubles as a distinctiveness signal.

DimensionReasoningScore

Specificity

The description is an adjective-laden noun phrase ('Modern minimalist aesthetic with clean lines, intentional color palette, subtle interactions, and consistent spacing') describing an aesthetic, not concrete actions the skill performs; it names no capabilities.

1 / 3

Completeness

It answers neither what the skill does (it authors design-system guidelines, unstated) nor when to use it; there is no 'Use when...' clause, so both what and when are effectively missing.

1 / 3

Trigger Term Quality

It contains design jargon ('intentional color palette', 'subtle interactions') rather than natural terms a user would say to invoke this skill, omitting 'design system', 'brand guidelines', 'UI guidelines', or 'design tokens'.

1 / 3

Distinctiveness Conflict Risk

The minimalist-aesthetic framing is somewhat specific to a design direction, but the generic phrasing could overlap with other UI/brand/design skills and does not name the 'Sleek' niche explicitly.

2 / 3

Total

5

/

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.