CtrlK
BlogDocsLog inGet started
Tessl Logo

claymorphism

Soft, rounded 3D-like shapes mimicking malleable clay with playful, puffy elements and colorful surfaces.

55

Quality

62%

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

Quality

Content

85%

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 design-system authoring guide with a clear numbered workflow and QA checkpoints. Its main weakness is actionability: it gives specific rules and tokens but no executable code or worked output example to model the expected guidance.

DimensionReasoningScore

Conciseness

The body is lean and list-driven with no over-explanation of concepts Claude already knows; every section (tokens, rules, workflow, output structure) earns its place and assumes Claude's competence, matching the lean/efficient anchor.

3 / 3

Actionability

Guidance is concrete and specific (concrete token values like #3B82F6, an enumerated spacing scale, required states, must/should constraint language), but it provides no executable code and no worked example of actual generated guidance, keeping it below the copy-paste-ready anchor.

2 / 3

Workflow Clarity

The "Guideline Authoring Workflow" is an explicit 6-step numbered sequence closed by a QA checklist (step 6) reinforced by the "Quality Gates" section, giving clear sequencing with an explicit validation checkpoint for a non-destructive authoring task.

3 / 3

Progressive Disclosure

No bundle files exist; the SKILL.md is a single self-contained, well-organized document with clear section headers and no nested references, which per the rubric satisfies progressive disclosure for skills needing no external references.

3 / 3

Total

11

/

12

Passed

Description

40%

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 captures the visual essence of claymorphism but reads as a style noun-phrase rather than a capability/trigger statement: it names no concrete actions and lacks any "Use when..." guidance. It is moderately distinct but generic enough to risk overlap with adjacent soft-UI trends.

Suggestions

Rewrite the description to lead with concrete actions, e.g. "Creates and applies claymorphism UI styling — soft rounded shadows, puffy surfaces, and clay-like depth — to components and design tokens."

Add an explicit trigger clause such as "Use when the user asks for claymorphism, soft/puffy 3D UI, or clay-style design system guidance."

Include natural user-facing terms ("claymorphism", "puffy UI", "soft 3D buttons", "clay cards") to improve trigger coverage and distinctiveness from neumorphism/glassmorphism.

DimensionReasoningScore

Specificity

The description ("Soft, rounded 3D-like shapes mimicking malleable clay with playful, puffy elements and colorful surfaces") names the style domain but contains no concrete action verbs (e.g., create, apply, generate); it is a noun-phrase descriptor rather than a capability statement, matching the vague/no-actions anchor.

1 / 3

Completeness

It states what the skill concerns (the claymorphism visual style) but provides no explicit "when to use" trigger guidance; per the rubric guideline, a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

It includes some relevant domain keywords ("3D-like", "malleable clay", "puffy elements") but lacks natural user trigger phrasing and common variations, and omits any "Use when..." clause, so it sits between the low and high anchors.

2 / 3

Distinctiveness Conflict Risk

Claymorphism is a recognizable niche, but the description relies on generic adjectives (soft, rounded, playful, colorful) that overlap with related soft-UI trends (neumorphism, glassmorphism), so it could still conflict with similar design skills.

2 / 3

Total

7

/

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.