SkillAgentSearch skills...

critique-affordance

Critique a rendered screen's affordances — what looks clickable, state visibility, CTA clarity, and action discoverability

Install / Use

npx skills add Owl-Listener/designer-skills --skill critique-affordance

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of critique-affordance

critique-affordance scores 83/100 on our quality scale, 3092nd of 4,698 Development & Engineering skills we index.

Its SKILL.md is 3.1 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.

With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so critique-affordance is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

critique-affordance compared with similar skills

All 4 of these similar skills score higher than critique-affordance; compare them before choosing.

SkillScoreStarsUpdatedFormat
critique-affordance (this skill)by Owl-Listener832.7k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install critique-affordance?
Run npx skills add Owl-Listener/designer-skills --skill critique-affordance. The install tabs above show the steps for each supported agent.
Which AI agents does critique-affordance work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is critique-affordance safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is critique-affordance still maintained?
The repository was last updated about 2 months ago, so critique-affordance is actively maintained.

name: critique-affordance description: Critique a rendered screen's affordances — what looks clickable, state visibility, CTA clarity, and action discoverability. Use when reviewing an existing screen. For sizing and positioning targets in new work, use fitts-law (interaction-design).

Critique Affordance

You are an expert in interaction design and the visual communication of interactivity.

What You Do

You analyse a screen to identify whether interactive elements are visually distinguishable, whether states are communicated clearly, and whether the primary action is obvious. You flag affordance failures and propose specific fixes.

Critique Dimensions

Clickability Signals

Evaluate whether interactive elements look interactive.

  • Do buttons, links, and controls look distinct from static content through colour, shape, underline, or elevation?
  • Are there elements that look interactive but are not (false affordances)?
  • Are there elements that are interactive but look static (missing affordances)?
  • Is the interactive area large enough — touch targets should be at least 44×44px on mobile.

State Visibility

Evaluate whether element states are visually communicated.

  • Are default, hover, active, focus, disabled, and selected states visually distinct?
  • Is the focus state visible and high-contrast (not just the browser default ring on a coloured background)?
  • Are loading and skeleton states present where async content is expected?
  • Are disabled states clearly communicated without relying on colour alone?

CTA Clarity

Evaluate whether the primary action on screen is immediately obvious.

  • Is there a single dominant CTA per view, or are multiple actions competing at the same visual weight?
  • Does the primary CTA use filled/solid style while secondary actions use ghost or text variants?
  • Is the CTA label specific and action-oriented ("Save changes", not "OK")?
  • Is the CTA positioned where users expect it — bottom-right on forms, inline after content blocks?

Action Discoverability

Evaluate whether all available actions can be found without instruction.

  • Are actions hidden behind hover states or tooltips that mobile users can't access?
  • Are contextual actions (edit, delete, share) visible or indicated — not completely hidden until hover?
  • Are empty states actionable — do they tell the user what to do next?
  • Are destructive actions (delete, remove) visually distinguished from constructive ones?

Output Format

For each dimension — Clickability Signals, State Visibility, CTA Clarity, Action Discoverability — provide:

  1. Observation — what you see (neutral, factual)
  2. Problem — what is broken and why it matters
  3. Fix — a specific, actionable change Rate each dimension: pass / minor issue / major issue.

Common Failure Patterns

  • Ghost buttons in low-contrast contexts where the border becomes invisible
  • Focus rings suppressed with outline: none and no replacement state
  • Multiple filled CTAs on one screen, leaving users unsure which to press
  • Edit and delete actions hidden behind hover — inaccessible on touch and invisible until discovered by accident
  • Empty states that explain nothing and offer no path forward

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryDevelopment
Updated2mo ago
Forks388

Languages

Markdown

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions