CtrlK
BlogDocsLog inGet started
Tessl Logo

critique

Run a 5-dimension expert design review on any HTML artifact in the project — Philosophy / Visual hierarchy / Detail / Functionality / Innovation, each scored 0–10. Outputs a single self-contained HTML report with a radar chart, evidence-backed scores, and three lists: Keep / Fix / Quick-wins. Use when the brief asks for a "design review", "design critique", "5 维度评审", "design audit", or "what's wrong with my design".

74

Quality

93%

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

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.

A well-structured, actionable skill body with strong sequencing and clear output contract. The only slack is minor verbosity in the dimension evidence lists and the absence of an explicit error-recovery loop.

Suggestions

Trim the rhetorical flourishes and a few redundant evidence-list bullets in the dimension sections to tighten conciseness toward a 5.

Add an explicit validation feedback loop (e.g. 'if a score cannot be justified with a cited element, re-read the block before scoring') to strengthen workflow_clarity.

Consider collapsing the 'Scoring discipline' and 'Hard rules' sections, which overlap on anti-grade-inflation guidance, to reduce repetition.

DimensionReasoningScore

Conciseness

Lean and assumes competence — no padding about basic HTML or design concepts — with a few dimension evidence-list bullets and rhetorical flourishes that could be trimmed without loss.

4 / 5

Actionability

Fully executable guidance: numeric score bands, per-dimension evidence cues, a worked evidence paragraph with class names and line numbers, and a copy-ready <artifact> output contract.

5 / 5

Workflow Clarity

Five clearly sequenced steps with scoring discipline and hard-rules checkpoints, but no explicit validate→fix→retry feedback loop; this is an analysis skill so the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist and none are referenced; the body is organized into well-signaled sections (When to use, What you produce, dimensions, Workflow, Output contract, Hard rules) appropriate for a self-contained single-file skill.

5 / 5

Total

18

/

20

Passed

Description

100%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 model description: it states concrete capabilities, gives an explicit 'Use when' clause with natural trigger phrases, and carves out a distinct niche. Third-person voice is used throughout with no inflation.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions — 'scores 0–10', 'radar chart', 'evidence-backed scores', and three named lists (Keep / Fix / Quick-wins) — giving comprehensive coverage rather than minor gaps.

5 / 5

Completeness

Explicitly answers both what (5-dimension review producing a self-contained HTML report with radar chart and three lists) and when (a 'Use when...' clause listing concrete trigger phrases).

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say — 'design review', 'design critique', 'design audit', '5 维度评审', 'what's wrong with my design' — with synonyms and a bilingual variant.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — a 5-dimension HTML design critique producing a radar-chart report — with distinctive triggers and minimal overlap risk with other skills.

5 / 5

Total

20

/

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.

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
nexu-io/open-design
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.