CtrlK
BlogDocsLog inGet started
Tessl Logo

high-contrast-skeuomorphic-clean

Create a high-contrast clean skeuomorphic design system with molded dark surfaces, crisp light separation, tactile inset depth, and restrained signal accents.

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 ./agent-skills/web-design/high-contrast-skeuomorphic-clean/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-organized, concise set of design-direction guidance that would be hard to misread stylistically, but it contains no concrete implementation artifacts and its 'Workflow' section is empty. It reads as a style brief rather than an executable skill, and the structural flaws (empty header, verbatim duplication of the description) undermine an otherwise clean layout.

Suggestions

Remove the empty '## Workflow' header or replace it with an actual ordered application sequence (e.g. page shell, then cards, then controls, then micro-visualizations).

Add at least one concrete artifact — example CSS/Tailwind tokens, shadow stack values, or a reference color/accent recipe — so the tactile guidance becomes executable rather than purely descriptive.

Drop the 'Use When' section that duplicates the frontmatter description verbatim and fold any trigger conditions into a properly worded usage section.

DimensionReasoningScore

Conciseness

The body is lean and directive with no explanations of known concepts ('one-pixel wrappers, top-edge highlights, dark-to-darker fills'), but the 'Use When' section repeats the frontmatter description verbatim and the '## Workflow' header is empty, which are minor wasted tokens.

4 / 5

Actionability

The guidance gives concrete visual recipes ('inset shadow stacks, soft outer shadow falloff', 'masked reveals, gentle object lift') but never provides any tangible artifact — no color values, shadow/CSS snippets, or example implementation — so it stays at the qualities level rather than being fully executable guidance.

3 / 5

Workflow Clarity

The '## Workflow' section is literally empty, so the only sequencing is the implicit Scope-to-Avoid flow with no explicit steps or checkpoints; the sequence is present but implicit, matching the anchor for 'steps listed but validation gaps / checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The ~50-line body has well-organized sections and no bundle files or references (none exist in the bundle), which nearly matches the simple-skill ideal, but the empty '## Workflow' header and the duplicated 'Use When' content leave minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

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

The description gives a clear and fairly concrete picture of the design direction, but it states only what the skill produces with a single action and never says when to use it. Adding a 'Use when...' trigger clause and natural synonyms would substantially raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for a skeuomorphic, tactile, or high-contrast design system, dark premium UI, or realistic depth instead of flat minimal styling.'

Add natural synonyms and user phrasings such as 'tactile UI', 'realistic depth', 'bevels', or 'dark premium interface' so the skill matches how users actually describe the style.

Turn the attribute list into 2-3 concrete actions (e.g. 'Build dark molded shells, style cards and controls with inset depth, and apply a restrained accent signal') to improve specificity.

DimensionReasoningScore

Specificity

The description names the domain ('skeuomorphic design system') and one action ('Create') with concrete visual qualities ('molded dark surfaces', 'tactile inset depth', 'restrained signal accents'), but lists only a single action rather than several concrete capabilities, matching the 'domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

The 'what' is clear (create a high-contrast skeuomorphic design system with specific visual traits), but there is no 'Use when...' clause or equivalent trigger guidance, which the judging guidelines cap at 3.

3 / 5

Trigger Term Quality

'skeuomorphic', 'high-contrast', and 'design system' are natural designer phrases, but common variations users might say ('tactile', 'realistic UI', 'depth', 'neumorphism') are absent, matching 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

'Skeuomorphic design system' is a clear niche with distinct triggers, with only minor overlap risk against general design-system or brand-styling skills, matching 'mostly distinct; minor overlap risk'.

4 / 5

Total

13

/

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
MengTo/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.