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.

55

Quality

61%

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

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-structured, token-efficient design-direction guide with clear scope, visual targets, and tuning knobs. Its main weaknesses are the empty Workflow section and the absence of concrete executable tokens (colors, measurements, CSS) that would make the direction directly implementable.

Suggestions

Fill the empty '## Workflow' section with a short sequenced application process (e.g. define tokens → build shell → assemble cards/controls → apply accents → review contrast), or remove the header if no workflow is intended.

Add concrete executable specifics: example shadow stacks, border-radius ranges, accent-color usage limits, or a small CSS/token snippet so the direction is copy-paste ready.

Optionally move the detailed pattern catalog into a referenced file (e.g. PATTERNS.md) once the skill grows, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Lean bullet-form prescriptive guidance with no concept padding or explanation of things Claude already knows; every section earns its place. Not score 2 because there is no unnecessary explanation, only purposeful reframing of the aesthetic per section.

3 / 3

Actionability

Gives concrete qualitative direction ('one-pixel wrappers', 'top-edge highlights', 'dark-to-darker fills', 'inset shadow stacks') but no executable tokens — no hex colors, radii, shadow parameters, CSS, or code — so it is not copy-paste ready. Not score 1 because the guidance is specific rather than vague.

2 / 3

Workflow Clarity

Content is organized into clear thematic sections (Scope, Visual target, Implementation guidance, Recommended patterns, Tuning knobs, Avoid), but the '## Workflow' header is empty and there is no sequenced application process. Not score 3 because no explicit workflow or checkpoints exist; not score 1 because the sections themselves are clear and coherent.

2 / 3

Progressive Disclosure

The body is under 50 lines, single-purpose, and has no need for external references; it is well-organized into clearly labeled sections, satisfying the rubric's simple-skill allowance for a top score with no bundle files.

3 / 3

Total

10

/

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 vivid, specific aesthetic direction but functions as a vision statement rather than a trigger-rich skill description. It lacks an explicit 'Use when…' clause, which limits completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a tactile, premium skeuomorphic or neumorphic UI direction with dark molded surfaces.'

Enumerate concrete actions beyond 'Create' (e.g. 'Define surface tokens, assemble card/control modules, apply inset depth and signal accents') to raise specificity.

Include common user terms such as 'neumorphism', 'dark mode UI', and 'tactile design' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names a concrete domain and several visual attributes ('molded dark surfaces, crisp light separation, tactile inset depth, and restrained signal accents'), but offers only one action ('Create') with modifiers rather than multiple distinct actions like the score-3 anchor.

2 / 3

Completeness

Clearly answers 'what' (create a design system with these traits) but provides no explicit 'when' trigger guidance; per the rubric a missing 'Use when…' clause caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant niche keywords ('skeuomorphic', 'high-contrast', 'tactile', 'design system') but lacks an explicit 'Use when…' trigger clause and omits common variations such as 'neumorphism', so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The skeuomorphic niche is fairly specific, but the broad 'design system' framing combined with no explicit trigger disambiguation leaves moderate overlap risk with sibling design-direction skills.

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