CtrlK
BlogDocsLog inGet started
Tessl Logo

design-critique

Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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, lean instruction-only skill: a sequenced critique pass with concrete checks, explicit pre-critique checkpoints, and a ready-to-use output template. It respects Claude's intelligence while remaining highly actionable.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — it never explains what design or critique is, and aphoristic lines like 'Critique is not redesign; recommend, do not rebuild' earn their place as guidance rather than padding.

3 / 3

Actionability

Concrete checks dominate the pass ('Touch targets at least 44x44 px', 'WCAG AA at minimum; AAA where reasonable', 'Validation runs at the right time (on blur...)') and the output section gives a copy-paste-ready severity-grouped template.

3 / 3

Workflow Clarity

The pass is explicitly sequenced 'in order' (steps 1-9) with an upfront context-gathering checkpoint ('If any of these is missing, ask'), and the task is non-destructive so the destructive-operation feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the skill is self-contained with well-organized sections (When to use, When not to use, Pre-critique context, The pass, Output format, Anti-patterns) and no nested references.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and occupies a clear, non-conflicting niche, but it omits explicit 'Use when...' trigger guidance and leans on design jargon over natural user phrasings. Adding a trigger clause and common terms like 'feedback' or 'review this screen' would raise trigger quality and completeness.

Suggestions

Append a 'Use when...' clause (e.g., 'Use when giving feedback on a screen, mock, or live UI before ship') so completeness reaches the explicit-trigger bar.

Swap or supplement jargon like 'affordance' with natural phrasings a user would say ('what looks clickable', 'feedback on my design', 'review this screen').

Keep the concrete dimension list, but pair each with a plain-language synonym to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete critique dimensions — 'user job clarity, hierarchy, affordance, error states, accessibility, and consistency' plus 'what to change, in what order, and why' — matching the anchor that lists several specific concrete actions.

3 / 3

Completeness

It clearly answers 'what' (a structured design critique across named dimensions) but lacks any 'Use when...' trigger clause, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

'critique' is a natural user term, but 'affordance' and 'hierarchy' are design jargon, and common phrasings a user would actually say ('feedback on my design', 'review this screen/UI') are missing.

2 / 3

Distinctiveness Conflict Risk

'Product design critique' is a clear niche distinct from code review or data skills, and its named dimensions make it unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
paperclipai/paperclip
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.