Install
$ agentstack add skill-flurdy-agent-skills-browser-screenshot ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Browser Screenshot
Capture screenshots of the web application for visual verification during UI/CSS iteration.
Setup
- Install playwright in the project (if not already):
npm install playwright
npx playwright install chromium
- Symlink the screenshot script into the project's
scripts/directory:
SKILLS_DIR="${SKILLS_DIR:-${CODEX_HOME:-$HOME/.codex}/skills}"
if [[ ! -d "$SKILLS_DIR" ]]; then
SKILLS_DIR="${CLAUDE_HOME:-$HOME/.claude}/skills"
fi
ln -sfn "$SKILLS_DIR/browser-screenshot/scripts/screenshot.sh" scripts/screenshot
Usage
/browser-screenshot
/browser-screenshot http://localhost:3000
/browser-screenshot http://localhost:3000 mobile
Instructions
- Determine the URL to screenshot:
- If
$ARGUMENTScontains a URL, use it - Otherwise use the
SCREENSHOT_URLenv var if set - Default:
http://localhost:3000
- Determine the viewport:
- If
$ARGUMENTScontainsmobile, use mobile viewport (375x812) - If
$ARGUMENTScontainstablet, use tablet viewport (768x1024) - If
$ARGUMENTScontains a custom size like1024x768, use those dimensions - Default: desktop viewport (1280x900)
- If
$ARGUMENTScontainsboth, take two screenshots (desktop and mobile) - Keep both dimensions under 2000px to avoid image limit errors
- Run the screenshot script via the project symlink:
scripts/screenshot
If the symlink doesn't exist yet, create it first (see Setup above).
Screenshots are saved to /tmp/claude-screenshots/screenshot-.png by default (e.g. screenshot-desktop.png, screenshot-mobile.png). Each run overwrites the previous screenshot for that viewport.
- Read the screenshot using the available image-reading tool to view the captured image. This is the critical step because the model can inspect the captured UI directly.
- Analyze the screenshot and report what you see, especially:
- Layout issues (overlapping elements, alignment problems)
- Spacing/margin problems
- Color or styling discrepancies
- Responsive behavior (if both viewports captured)
- If the user asked you to fix a specific CSS issue, compare what you see against their description and suggest or apply fixes.
Notes
- The script uses
waitUntil: 'networkidle'with a 15s timeout — if the page loads async content, the screenshot will wait for it. - Screenshots capture the viewport only (not full-page scroll) to stay within the 2000px image dimension limit.
- For rapid iteration: make the CSS change, then run
/browser-screenshotto verify, repeat.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: flurdy
- Source: flurdy/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.