CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-review

Reviews layout density, theme adherence, typography, spacing, search-chrome placement, accessibility modes, and visual consistency. Use during visual layout or CSS adjustments.

Quality

85%

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

86%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 compact checklist skill: lean, assumes competence, and grounds its guidance in concrete commands, pixel widths, and named files. The only notable gaps are a handful of judgment-only checklist items lacking verification specifics and the absence of error-recovery steps in the review protocol.

DimensionReasoningScore

Conciseness

The ~35-line body is a lean checklist with zero explanation of concepts Claude already knows; every line is a directive (e.g., "hidden chrome → `0rem` content reserve", "not flashy marketing chrome") and no padding was found to trim.

5 / 5

Actionability

Concrete, executable guidance is present: `npm run ensure`, confirming `/api/local-project-id`, screenshot breakpoints at phone (~390) and desktop (~1280), named doc files to read, and the exact "Review record" comment to post. A few checklist items ("visual consistency", "theme adherence") remain judgment directives without how-to-check specifics, keeping it below fully copy-paste-ready.

4 / 5

Workflow Clarity

A clear temporally-sequenced protocol with explicit checkpoints: "before starting" (read AGENTS.md and codex-review-protocol), "before browser work" (run `npm run ensure`, confirm project id), and "after a completed PR review" (post the record comment). No error-recovery loops are specified for when a check fails, so it does not reach the top anchor; this is a non-destructive review skill, so the destructive-cap rule does not apply.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files, the body is well-organized into Protocol and Checklist sections and delegates detail one level deep to clearly signaled paths (docs/search-chrome-behaviour.md, docs/wiring-conventions.md, the Cursor agent for the journey protocol), satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

80%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 strong description: specific, comprehensive on capabilities, third-person, and equipped with an explicit use-when clause. Its main gaps are a thin trigger-phrase list (missing UI/styling/design synonyms) and a when-clause that could be more concrete about the situations that call for this skill.

DimensionReasoningScore

Specificity

The description enumerates seven concrete review areas — "layout density, theme adherence, typography, spacing, search-chrome placement, accessibility modes, and visual consistency" — which is comprehensive coverage of the design-review domain, matching the single-verb-plus-enumeration structure of the top-tier examples.

5 / 5

Completeness

Both parts are present: a clear "what" (the enumerated review areas) and an explicit when-clause "Use during visual layout or CSS adjustments". The when-clause is brief and could name more concrete trigger situations (e.g., reviewing UI or styling changes), so it does not reach the fully explicit anchor.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "layout", "typography", "spacing", "theme", "accessibility", "CSS", "visual" are phrases users would actually say. A few common synonyms like "UI", "styling", "design", or "colors" are missing, keeping it below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

"search-chrome placement" and "accessibility modes" carve a recognizable niche with distinct triggers, but broad terms like "visual consistency", "typography", and "spacing" create minor overlap risk with generic frontend/design skills.

4 / 5

Total

17

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.cursor/skills/design-review/SKILL.md

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.