agentleFS
Sign inStart free
MCamnerMCamner/mq-image-analyze/skills/screenshot-ui-review/SKILL.md

screenshot-ui-review

Skill1 starsChanged 22 days agoMITView on GitHub

Use when reviewing screenshots of apps, terminals, dashboards, websites, or GitHub pages for layout and usability.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for visual critique of UI screenshots.

    line 8
  2. Distinctive:

    Check spacing, contrast, alignment

    line 29
  3. Distinctive:

    Call-to-action clarity — obvious next step?

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Screenshot UI Review

Use this skill for visual critique of UI screenshots.

Evals

Should trigger

  • "review this app screenshot for usability"
  • "check this dashboard layout"
  • "is this terminal UI readable?"
  • "audit this GitHub page screenshot"

Should not trigger

  • "score artistic composition" → use image-quality-audit
  • "build a prompt from this image" → use reverse-prompt
  • "analyze a diagram's architecture" → use visual-architecture-analysis

Core workflow

  1. Detect UI regions (OCR, layout segmentation)
  2. Identify visual hierarchy
  3. Check spacing, contrast, alignment
  4. Flag accessibility concerns
  5. Return structured review

What to check

  • Visual hierarchy — is the most important element clear?
  • Spacing — consistent rhythm or crowded?
  • Contrast — readable text at all sizes?
  • Alignment — grid discipline?
  • Density — too much or too little information?
  • Readability — fonts, sizes, line lengths?
  • Call-to-action clarity — obvious next step?
  • Terminal / CLI polish when reviewing developer tools

Output

  • What works well
  • What is confusing or weak
  • High-impact fixes (ordered by priority)
  • Suggested next iteration direction

Avoid

  • Aesthetic opinions without reasoning
  • Prescribing specific design tools
  • Generating replacement UI without approval

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free