Skip to content
Back to skills

Ui Screenshot

ASecurity

Capture verified desktop and mobile UI screenshots for review or a PR. Use when visual evidence of changed pages is needed.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 22, 2026
developmentgit

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 9, 2026

npx -y skills add jupes/agent-forge-harness --skill ui-screenshot --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ui Screenshot?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ui Screenshot
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jupes-ui-screenshot/badge)](https://www.skillsdirectory.com/skills/jupes-ui-screenshot)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ui-screenshot
description: Capture verified desktop and mobile UI screenshots for review or a PR. Use when visual evidence of changed pages is needed.
---

# Capture UI evidence

1. Resolve the target app, changed routes, and comparison base from the request and
   Git tracking configuration. Inspect its manifest for the actual server command.
2. Reuse a running app or start its documented development server with a bounded
   readiness check. Use the available browser tool or repository Playwright setup.
   Report unavailable tooling or startup failure instead of claiming captures.
3. Map the changed UI to representative states. Capture desktop and mobile sizes
   appropriate to the app (1280 and 375 CSS pixels are useful defaults). Exercise
   relevant loading, empty, error, and populated states when the change affects them.
4. Save under `.tmp/screenshots/` and inspect each image for loaded content, clipping,
   readable labels, and unintended private data. Record route, viewport, and state.
5. Link local captures for review. For an authorized PR update, use accessible image
   URLs only after a supported attachment/upload succeeds; local paths do not render
   for GitHub readers. If upload is unavailable, report that limitation.

Complete when captures exist, have been visually inspected, and the response
accurately distinguishes local evidence from images actually attached to a PR.
Stop only the development server this session started.

Files in this skill

  • SKILL.md1.1 KB
  • ui-screenshot.md1.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.