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.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

72%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 content is a well-organized, lean design-direction spec with concrete guidance and clean structure. Its main weakness is the empty '## Workflow' section, which adds no value and slightly undermines workflow clarity.

Suggestions

Remove or fill the empty '## Workflow' section; either delete the header or provide a brief sequenced flow (e.g., establish shell contrast -> build molded surfaces -> layer tactile depth -> apply restrained accent).

Tighten redundancy between Visual target, Implementation guidance, and Recommended patterns so each section earns its tokens distinctly.

Consider a short verification cue (e.g., 'Check that text-to-shell contrast and accent restraint still hold after applying depth effects') to add a light checkpoint without overstructuring a simple skill.

Dimension	Reasoning	Score
Conciseness	The body is efficient, well-structured, and avoids explaining concepts Claude already knows, with only minor redundancy where the dark-shell-on-lighter-background idea recurs across Visual target, Implementation guidance, and Recommended patterns.	4 / 5
Actionability	For an instruction-only design-direction skill the guidance is concrete and specific (one-pixel wrappers, top-edge highlights, inset shadow stacks, accent dots, orbit widgets), with only minor gaps versus copy-paste-ready executable instruction.	4 / 5
Workflow Clarity	The '## Workflow' section is an empty placeholder with no sequence, and while this is a simple single-purpose skill, the blank header leaves the process implicit and slightly confusing rather than unambiguous.	3 / 5
Progressive Disclosure	The body is a self-contained, under-50-line skill with no need for external references and clearly organized section headers, meeting the rubric's simple-skill exception for a top progressive-disclosure score.	5 / 5
	Total	16 / 20 Passed

Description

46%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 is a clear, concise statement of the design direction but functions only as a 'what', omitting any 'Use when...' trigger guidance. It uses design jargon rather than natural user trigger phrases, which limits trigger-term quality and completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers, e.g., 'Use when the user wants a premium, tactile, high-contrast dark UI direction rather than flat minimal cards.'

Reframe the description in third-person action voice with concrete verbs (e.g., 'Builds/Generates a high-contrast skeuomorphic design system...') instead of the imperative 'Create'.

Include natural trigger synonyms users would actually say (e.g., 'dark UI', 'tactile interface', 'skeuomorphic', 'premium dashboard look') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete output qualities ("molded dark surfaces, crisp light separation, tactile inset depth, and restrained signal accents"), but only one actual action verb ("Create"), so it does not list multiple specific actions like the score-5 anchor.	3 / 5
Completeness	It states clearly what the skill produces, but provides no "when" guidance; per the rubric, a missing 'Use when...' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Terms like "skeuomorphic," "high-contrast," and "molded dark surfaces" are design jargon rather than natural phrases a user would say, and there is no "Use when..." trigger language supplying common user phrasings.	2 / 5
Distinctiveness Conflict Risk	The niche is fairly specific and explicitly contrasted against neumorphism and glossy skeuomorphism, leaving only minor overlap risk with adjacent design-system skills, though the lack of explicit triggers keeps it below 5.	4 / 5
	Total	12 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: agent-skills/web-design/high-contrast-skeuomorphic-clean/SKILL.md
Commit: 4c716b5

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.