- name
|
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/open-design --skill critique -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/open-design --skill critique -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/open-design --skill critique -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/open-design --skill critique -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/nexu-io/open-design/tree/HEAD/design-templates/critiqueFrom the publisher
Produce a single-file HTML "design review report" that scores any artifact across 5 dimensions and proposes actionable fixes. Inspired by the huashu-design expert-critique flow.
A single self-contained <artifact type="text/html"> review report
including:
Each dimension is independent — a deck can be 9/10 on Innovation but 4/10 on Hierarchy and the report should say so plainly. Don't average away interesting failures.
Does the artifact pick a clear direction and stick to it through every micro-decision (chrome / kicker / spacing / accent)?
Evidence to look for:
0–4 Three styles fighting each other. 5–6 One direction but half the elements drift. 7–8 Coherent, occasional drift on edge pages. 9–10 Every element argues for the same thesis.
Can a stranger figure out what to read first, second, third — without being told?
Evidence to look for:
0–4 Everything shouts. 5–6 Hierarchy works on hero pages but breaks on body. 7–8 Clear tiers, occasional collision. 9–10 Eye moves with zero friction.
The 90/10 stuff — alignment, leading, kerning at large sizes, image framing, foot/chrome polish, edge-case spacing.
Evidence to look for:
grid-2-7-5?frame-img + caption proportions consistent across pages?<br> causing 1-character lines?0–4 Visible tape and string. 5–6 Most pages clean, 1–2 ragged. 7–8 Polished, expert eye finds 2–3 misses. 9–10 Magazine-grade — the kind of detail that makes printed-by-hand typographers nod.
Does the artifact work for its intended use? Click targets, nav, readability at presentation distance, copy-paste-ability for code blocks, mobile fallback if relevant.
Evidence to look for:
0–4 Visually fine but doesn't accomplish its job. 5–6 Core flow works, edge cases broken. 7–8 Robust through normal use. 9–10 Defensively engineered — handles iframe / fullscreen / paste / print without flinching.
Does this push past the median? Is there one element that makes people lean in?
Evidence to look for:
0–4 Generic AI-slop median. 5–6 Competent and unmemorable. 7–8 One memorable moment, the rest solid. 9–10 Multiple moves you'd steal — but each one obviously serves the thesis.
Three modes:
<artifact>.If multiple HTML files exist, ask which one (don't review all).
Skim the entire <style>, then read 6–8 representative content
blocks. Do not score from frontmatter alone. The score depends on
executed design, not declared intent.
For each of the 5 dimensions, write the score and a 30–80 word evidence paragraph that names specific elements. Use line numbers, class names, page numbers.
Example:
Dimension: Detail execution
Score: 6 / 10
Evidence: Stat-cards on page 3 align cleanly (grid-6, 3×2), but on
page 8 the right column foot sits 2vh higher than the left because
.callout has 3vh top margin while the figure doesn't. Image captions
use mono on page 5 but sans on page 7 — pick one.
Aggregate the 5 evidence paragraphs into:
display:flex for grid on page 4 to
fix the column drift").Build a single file:
Use the active DESIGN.md tokens if one exists; otherwise default to a neutral light theme (off-white background, near-black text, one accent for radar fill).
<artifact identifier="critique-<artifact-slug>" type="text/html" title="Critique · <Artifact Title>">
<!doctype html>
<html>...</html>
</artifact>
One sentence before the artifact ("Reviewed X across 5 dimensions, see
report below.") and stop after </artifact> — do not paraphrase
the report in chat; the user will read the artifact.
© 2026 Skills Rack.
---name: critiquedescription: |---# design-templates/critique/SKILL.mdFAQ
Download design-templates/critique/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/nexu-io/open-design.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.