CtrlK
BlogDocsLog inGet started
Tessl Logo

cafe

Cozy cafe-inspired interface with warm tones, soft typography, and clean layouts for a relaxed browsing experience.

52

Quality

57%

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

Quality

Content

65%

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

The content is a tight, opinionated design-system specification that respects token budget well and provides concrete tokens and rules, but its authoring workflow stops short of explicit validation checkpoints and offers no progressively-disclosed reference files for deeper material.

Suggestions

Add an explicit QA/validation checkpoint in the workflow (e.g. "Validate each rule against a token or threshold; re-check before finalizing") to close the feedback loop.

Provide a concrete output template or example deliverable so the Required Output Structure is copy-paste ready rather than described.

Consider extracting the full color/typography/spacing token tables into a referenced TOKENS.md for one-level-deep progressive disclosure.

DimensionReasoningScore

Conciseness

The body is a lean, well-organized specification that assumes Claude's competence: it lists token values, rules, and structure as compact bullets without explaining what a design system or accessibility is, so every token earns its place.

3 / 3

Actionability

It gives concrete token values (#5D4432, spacing scale 2/4/8...) and explicit do/don't rules, but the "Expected Behavior" and workflow steps are directive prose rather than copy-paste-ready, executable output templates, so guidance is strong but not fully concrete.

2 / 3

Workflow Clarity

The "Guideline Authoring Workflow" is a clear six-step sequence with a Required Output Structure, but it lacks an explicit validation/feedback checkpoint (e.g. verify rules against tokens before finalizing), so checkpoints are present but implicit.

2 / 3

Progressive Disclosure

The skill is a single self-contained SKILL.md with no references/, scripts/, or assets/ directories and no offloaded detail, which is appropriate for its size; however, it does not split the larger token/reference material into one-level-deep referenced files, so organization could be slightly stronger.

2 / 3

Total

9

/

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 paints a clear visual identity but is written as a style statement rather than a skill description: it omits concrete authoring actions and any explicit "Use when..." trigger guidance, leaving the when-to-invoke signal only implied.

Suggestions

Reframe as third-person actions, e.g. "Authors cafe-inspired design-system guidelines with warm tones, soft typography, and clean layouts."

Add an explicit trigger clause, e.g. "Use when creating or extending a cafe/restaurant design system, warm-tone theme, or cozy brand palette."

Name the concrete deliverables (design tokens, component rules, accessibility criteria, QA checklist) so the capability is unambiguous.

DimensionReasoningScore

Specificity

The phrase "Cozy cafe-inspired interface with warm tones, soft typography, and clean layouts" names a visual domain and several attributes, but it lists no concrete authoring actions (e.g. generating tokens, component rules, or QA checklists) that the skill actually performs.

2 / 3

Completeness

It states what the skill produces (a cafe-styled interface) but never provides an explicit "Use when..." trigger clause, so the "when" half is only implied; per the rubric a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

"cafe-inspired", "warm tones", "soft typography", and "clean layouts" are reasonable keywords a designer might say, but it lacks common variations like "design system", "theme", or "brand palette" that users would naturally request.

2 / 3

Distinctiveness Conflict Risk

It is anchored to a fairly specific cafe aesthetic, which helps distinguish it, but the description could still overlap with other generic design-system or theming skills since it never names the deliverable (design-system guidelines).

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.