CtrlK
BlogDocsLog inGet started
Tessl Logo

design-critique

Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 compact, well-structured instruction skill that pairs a concrete critique framework with a ready-to-use output template and clear sequencing. The main limitation is the abstract, guidance-heavy style leaves a few minor actionability and conciseness gaps rather than being fully crisp.

Suggestions

Replace the abstract connector-instruction lines ("If a Figma URL is provided, pull the design from Figma...") with a concrete, ordered input-handling step so the workflow is unambiguous.

Tighten the "How to Give Feedback" and "Tips" sections, which partly restate the framework already implied by the critique dimensions.

Resolve the malformed "If **~~design tool** is connected" markers, which read as broken placeholder syntax and undercut actionability.

DimensionReasoningScore

Conciseness

The body is well-organized with lean section headers and a tight critique framework, with only minor instances of guidance that could be trimmed, fitting the efficient-but-slightly-tightenable anchor.

4 / 5

Actionability

It provides a concrete multi-dimension critique framework and a copy-paste-ready output template with specific examples (e.g. "The CTA competes with the navigation"), giving mostly executable guidance with minor gaps typical of an instruction skill.

4 / 5

Workflow Clarity

The flow is clearly sequenced (gather design/context/focus, run the five critique dimensions, produce the structured output) with most checkpoints implied; it is a non-destructive single-purpose skill so no explicit validation loop is required.

4 / 5

Progressive Disclosure

The skill is compact with well-organized sections and no need for external references, meeting the simple-skill exception that allows a top progressive-disclosure score on structure alone.

5 / 5

Total

17

/

20

Passed

Description

90%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 strong on triggers, completeness, and distinctiveness, explicitly pairing what the skill does with concrete when-to-use phrases. Its only weakness is the somewhat abstract central action verb, which keeps specificity at the midpoint.

DimensionReasoningScore

Specificity

The description names the domain and the feedback dimensions ("usability, hierarchy, and consistency") but the core action "Get structured design feedback" is abstract without more concrete verbs, matching the anchor for naming a domain with limited concrete actions.

3 / 5

Completeness

It explicitly answers both what ("structured design feedback on usability, hierarchy, and consistency") and when ("Trigger with... or when sharing a Figma link or screenshot") with concrete trigger phrases, satisfying the top anchor.

5 / 5

Trigger Term Quality

It supplies comprehensive natural trigger phrases ("review this design", "critique this mockup", "what do you think of this screen?") plus Figma link/screenshot and stage cues, covering the synonyms users would actually say.

5 / 5

Distinctiveness Conflict Risk

It carves a clear design-critique niche with distinct triggers (mockup/Figma/screenshot feedback) and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository
anthropics/knowledge-work-plugins
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.