Screenshot Analyzer

Name: Screenshot Analyzer
Author: blacktop

blacktop/dotfiles

2 installs
17 repo stars
Updated July 16, 2026
blacktop/dotfiles

Screenshot-analyzer is a skill that finds and analyzes screenshots for UI/UX review against a design checklist.

About

Screenshot-analyzer finds recent screenshots and analyzes them for UI/UX review. A developer uses it to inspect interface errors, review layout issues, or examine visual problems in a screen capture. It reads the image and evaluates it against a checklist covering visual hierarchy, layout and spacing, typography, color and contrast, interactive elements, and error states, then returns structured findings.

Finds and analyzes screenshots from ~/Downloads/Screenshots for UI/UX review
Applies a checklist covering visual hierarchy, layout, typography, and contrast
Outputs structured findings with strengths, issues, and priority recommendations

Screenshot Analyzer by the numbers

2 all-time installs (skills.sh)
Ranked #1,562 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
Data as of Jul 28, 2026 (Skillselion catalog sync)

At a glance

screenshot-analyzer capabilities & compatibility

Capabilities: ui review · screenshot analysis · design critique
Use cases: ui design · web design
Platforms: macOS

From the docs

What screenshot-analyzer says it does

Find and analyze screenshots from ~/Downloads/Screenshots/ for UI/UX review.

SKILL.md

review UI designs, inspect interface errors, analyze layout issues, or examine visual problems

SKILL.md

WCAG-compliant contrast ratios

SKILL.md

npx skills add https://github.com/blacktop/dotfiles --skill screenshot-analyzer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/blacktop/dotfiles/screenshot-analyzer.svg)](https://skillselion.com/skills/blacktop/dotfiles/screenshot-analyzer)

Installs	2
repo stars	★ 17
Last updated	July 16, 2026
Repository	blacktop/dotfiles ↗

What it does

Analyze a UI screenshot against a design checklist and return structured strengths, issues, and fixes.

Who is it for?

Reviewing UI designs, inspecting interface errors, and analyzing layout issues from screen captures.

When should I use this skill?

Asked to look at screenshots, review a UI design, or analyze visual problems.

What you get

A screenshot is reviewed against a UI/UX checklist and returned as structured findings and priority fixes.

By the numbers

6-category UI/UX review checklist

Files

SKILL.mdMarkdownGitHub ↗

Screenshot Analyzer

Find and analyze screenshots from ~/Downloads/Screenshots/ with focus on UI/UX review.

Workflow

1. Find Screenshots

List recent screenshots sorted by modification time:

ls -t ~/Downloads/Screenshots/*.png | head -5

Adjust -5 to show more/fewer files as needed.

2. Read and Analyze

Use the Read tool to view the screenshot image:

Read: ~/Downloads/Screenshots/<filename>.png

The Read tool renders images visually for analysis.

3. UI/UX Review Checklist

When analyzing, evaluate:

Visual Hierarchy

Clear focal points and content prioritization
Logical flow of information
Appropriate use of size, color, and spacing to guide attention

Layout & Spacing

Consistent margins and padding
Proper alignment of elements
Balanced whitespace usage

Typography

Readable font sizes and line heights
Appropriate font choices and hierarchy
Sufficient contrast for legibility

Color & Contrast

WCAG-compliant contrast ratios
Consistent color palette
Meaningful use of color (not just decorative)

Interactive Elements

Clear affordances for buttons/links
Visible focus states
Appropriate touch/click target sizes

Error States & Feedback

Clear error messaging
Helpful guidance for resolution
Appropriate visual indicators

Consistency

Consistent patterns across similar elements
Adherence to design system (if applicable)
Predictable interaction patterns

Output Format

Structure findings as:

## Screenshot Analysis: <filename>

### Summary
[1-2 sentence overview of what the screenshot shows]

### Findings

#### Strengths
- [Positive observation 1]
- [Positive observation 2]

#### Issues
- **[Issue Type]**: [Description] → [Suggested fix]
- **[Issue Type]**: [Description] → [Suggested fix]

### Priority Recommendations
1. [Most critical fix]
2. [Second priority]
3. [Third priority]