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.

Quality

85%

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

Quality

Content

100%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 an exemplary instruction-only skill: lean, highly actionable, with a clearly sequenced critique pass, an explicit context-gathering gate, and a concrete output template. No bundle files exist but none are needed for this self-contained skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized, assumes Claude's competence (e.g. cites "WCAG AA" without explaining what WCAG is), and every line earns its place; no padded concept explanations.	5 / 5
Actionability	Concrete, specific guidance throughout — e.g. "Touch targets at least 44×44 px", "Buttons are verbs that name the outcome ('Save changes' beats 'Submit')", and a copy-paste-ready output format template; fully actionable for an instruction-only skill.	5 / 5
Workflow Clarity	Clear ordered sequence ("The pass (in order)" steps 1–9), an explicit pre-critique validation gate ("If any of these is missing, ask"), and a defined output format — matching the checklist-plus-checkpoint anchor.	5 / 5
Progressive Disclosure	Self-contained single-purpose skill with clear section headers (When to use, When not to use, Pre-critique context, The pass, Output format, Anti-patterns), no nested references, and no need for external bundle files.	5 / 5
	Total	20 / 20 Passed

Description

71%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 specific and distinct, listing concrete critique dimensions and a clear outcome framing. Its main weakness is the absence of any explicit "use when..." trigger guidance, which limits completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when a designer or engineer asks for feedback on a screen, mock, or flow, or before instrumenting a suspected drop-off point."

Include a few natural synonyms ("UX review", "feedback on a screen") to broaden trigger coverage.

Clarify the boundary versus redesign (e.g. "for critique, not redesign") in the description itself to further reduce conflict risk.

Dimension	Reasoning	Score
Specificity	Names multiple concrete critique dimensions — "user job clarity, hierarchy, affordance, error states, accessibility, and consistency" — plus the framing "what to change, in what order, and why," giving comprehensive coverage of capabilities.	5 / 5
Completeness	Clearly answers "what" (structured critique across named dimensions) but provides no "when to use" clause or equivalent explicit trigger guidance; per the guidelines this caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ("design critique", "product design", implied "feedback"), but lacks synonyms like "UX review" or "feedback on a screen" and has no explicit trigger phrasing.	4 / 5
Distinctiveness Conflict Risk	"Product design critique" carves a clear niche distinct from general code review or redesign skills, with only minor overlap risk against broad "design" or "review" skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: paperclipai/paperclip
Path: packages/skills-catalog/catalog/optional/product/design-critique/SKILL.md
Commit: 890ab9a

Reviewed: about 16 hours 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.