screenshot-annotator
Skill4 starsChanged 5 months agoMITView on GitHub
Capture, annotate, and share screenshots with AI-powered descriptions using Peekaboo.
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ncklrs/claude-chrome-user-testingtheir own version, first seen Jan 7, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ncklrs/claude-chrome-user-testing★ 20same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- bet-journalSkill
- clv-journalSkill
- crypto-priceSkill
- data-vizSkill
- devin-integrationSkill
- dfs-optimizerSkill
- git-helperSkill
- judge-auditSkill
- kelly-criterionSkill
- market-sentimentSkill
- nft-trackerSkill
- portfolio-rebalancerSkill
- security-scannerSkill
- sports-oddsSkill
- streak-trackerSkill
- weather-forecastSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Create step-by-step visual guides
- Very specific: line 137
Always use peekaboo see --annotate before clicking to identify element IDs
- Very specific: line 138
Use --analyze with specific prompts for better AI descriptions
- Very specific: line 140
Check permissions with peekaboo permissions if captures fail
≈ “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.
Files
Screenshot Annotator
Capture screenshots with automatic UI element annotation and AI-powered descriptions. Built on top of Peekaboo for macOS UI automation.
Features
- Capture full screen, specific windows, or regions
- Automatically annotate UI elements with clickable IDs
- Generate AI descriptions of what's on screen
- Save annotated screenshots with metadata
- Compare before/after screenshots
- Create step-by-step visual guides
Requirements
- macOS with Screen Recording permissions
- Peekaboo CLI installed (
brew install openclaw/tap/peekaboo)
Quick Start
Capture and annotate current screen
peekaboo see --annotate --path /tmp/annotated-screen.pngCapture specific app window
peekaboo see --app "Safari" --annotate --path /tmp/safari-annotated.pngCapture with AI analysis
peekaboo see --annotate --analyze "Describe the main UI elements and their purpose" --path /tmp/analyzed.pngCommon Workflows
Document a bug
# 1. Capture the problematic state
peekaboo see --app "MyApp" --annotate --path /tmp/bug-screenshot.png
# 2. Get element IDs for the bug report
peekaboo list windows --app "MyApp" --json
# 3. Describe what's wrong
peekaboo see --app "MyApp" --analyze "Identify any UI issues or anomalies"Create a tutorial
# Step 1: Capture initial state
peekaboo see --app "Finder" --annotate --path /tmp/step1.png
# Step 2: Click on target element
peekaboo click --on B3 --app "Finder"
# Step 3: Capture result
peekaboo see --app "Finder" --annotate --path /tmp/step2.pngCompare UI states
# Before
peekaboo see --app "Settings" --path /tmp/before.png
# Make changes...
# After
peekaboo see --app "Settings" --path /tmp/after.png
# Analyze differences
peekaboo see --app "Settings" --analyze "Compare this to the previous state and describe changes"Advanced Usage
Capture specific region
peekaboo image --mode region --region 100,100,800,600 --path /tmp/region.pngCapture with retina resolution
peekaboo image --mode screen --retina --path /tmp/retina-screen.pngCapture menu bar
peekaboo menubar list --json
peekaboo see --mode menubar --annotate --path /tmp/menubar.pngBatch capture all windows
for app in "Safari" "Finder" "Terminal"; do
peekaboo see --app "$app" --annotate --path "/tmp/${app}-annotated.png"
doneOutput Formats
Screenshots are saved as PNG by default. Use --format jpg for JPEG output.
The --json flag outputs metadata including:
- Window dimensions and position
- Annotated element IDs and locations
- Timestamp and app info
Tips
- Always use
peekaboo see --annotatebefore clicking to identify element IDs - Use
--analyzewith specific prompts for better AI descriptions - Combine with
peekaboo clickandpeekaboo typefor automated workflows - Check permissions with
peekaboo permissionsif captures fail
Author
Created by Ian Alloway - Data Scientist specializing in AI/ML.
License
MIT License
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
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.

