Critique
Use when: give structured, specific design critique with actionable fixes, not vague feedback.From its SKILL.md
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill critiqueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 217 tokens by cl100k_base, as published. Nobody here has run it
Goal: turn a visual impression into concrete, prioritized fixes.
Use for:
- reviewing a UI, component, or screen
- explaining why a design feels off
- prioritizing polish work with limited time
Workflow:
- State the intent and audience of the design.
- Evaluate by dimension: hierarchy, spacing, type, color, motion.
- For each issue, name the element and the specific problem.
- Explain the principle being violated.
- Propose a concrete fix, not a vague direction.
- Rank issues by impact on clarity and usability.
Dimensions:
- hierarchy: is the most important thing the most prominent
- spacing: consistent rhythm, grouped by relationship
- typography: scale, weight, and line length
- color and contrast: meaning and accessibility
- motion: purposeful, not decorative
Rules:
- be specific to the element, not the whole screen
- tie every critique to a principle and a fix
- prioritize; do not dump an unranked list
- separate subjective taste from objective usability
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.