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.

66

Quality

80%

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 ./packages/skills-catalog/catalog/optional/product/design-critique/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary instruction-only skill body: lean, directive, and free of padding, with a concrete ordered pass, measurable thresholds, and a copy-paste output template. The only meaningful improvement would be a lightweight self-check on the generated output before presenting it.

DimensionReasoningScore

Conciseness

Every line is a directive or a template; the body never explains concepts Claude already knows (it cites 'WCAG AA at minimum' without defining it, and 'Save changes beats Submit' teaches the rule in six tokens). There is no padded section to trim — anchor 5.

5 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: an ordered 9-step pass with concrete, checkable criteria ('within 3 seconds', 'on blur, not on every keystroke', '44x44 px'), plus a copy-paste output template with severity groups and a mandatory 'strengths to keep' section. Per the rubric's scoring notes, absence of code is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

The sequence is explicit (pre-critique context -> ordered pass -> formatted output) with a real validation gate ('If any of these is missing, ask. Critique without these is opinion'). It falls short of anchor 5 only because there is no post-output verification step (e.g., confirming each finding pairs exactly one issue with one fix) — a minor validation gap, matching anchor 4.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed: the entire body is core operating procedure that must be held in context during a live critique pass. Sections are cleanly labeled and easy to navigate, and nothing that belongs in a separate reference file is inlined — anchor 5 for a self-contained, well-sectioned skill.

5 / 5

Total

19

/

20

Passed

Description

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

A specific, well-scoped description that clearly names what the skill does and its critique dimensions, with no fluff. Its main weakness is the missing 'Use when...' trigger clause, which both caps completeness and leaves natural trigger phrases ('design feedback', 'review my mock') unsurfaced.

Suggestions

Append an explicit trigger clause, e.g. 'Use when someone asks for feedback on a screen, mock, flow, or live UI, or wants a pre-ship design review.'

Include natural user phrasings as trigger terms — 'design feedback', 'design review', 'critique my mock/screen' — alongside the current dimension keywords.

Mention the concrete output (a severity-grouped, prioritized list of fixes) so the deliverable is explicit in the description.

DimensionReasoningScore

Specificity

Names the domain ('structured product design critique') plus six concrete capability areas ('user job clarity, hierarchy, affordance, error states, accessibility, and consistency') and an explicit output focus ('what to change, in what order, and why'), all in third-person voice. It falls short of anchor 5 only because it omits the artifact types it operates on (screens, mocks, flows) and the severity-grouped output format.

4 / 5

Completeness

The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or any equivalent explicit trigger guidance — the rubric explicitly caps completeness at 3 in that case. It is not a 2 because the 'what' half is specific and multi-faceted, not vague.

3 / 5

Trigger Term Quality

'Product design critique' plus 'accessibility', 'hierarchy', and 'error states' give good keyword coverage of natural designer vocabulary. A few natural terms users would say are missing ('design feedback', 'review my screen/mock', 'design review', 'UI'), so it fits anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The named critique dimensions (affordance, hierarchy, accessibility) establish a clear design-critique niche that is mostly distinct. Minor overlap risk remains with closely related skills such as general code review or design-system/brand-styling skills, matching anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

15

/

20

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.

Validation — 15 / 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.