screen-capture
Skill1 starsChanged 5 months agoMITView on GitHub
Take screenshots on Wayland/Hyprland with grim + slurp — full screen, a chosen monitor, an interactive region, or the active window — and save to a file or pipe to the clipboard. Use whenever an agent needs to see the screen, capture UI state, grab a region for analysis, or produce an image to reason over. The "eyes" for visual computer use.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- lotosbin/claude-skillstheir own version, first seen Dec 29, 2025
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- lotosbin/claude-skills★ 14same 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 repository24 other files it gives its agents.
- api-designSkill
- brainstormingSkill
- councilSkill
- dispatching-parallel-agentsSkill
- document-toolkitSkill
- executing-plansSkill
- gui-input-automationSkill
- humanizeSkill
- hyprland-controlSkill
- incremental-implementationSkill
- issue-to-prSkill
- litreviewSkill
- mcp-builderSkill
- rust-reviewSkill
- session-handoffSkill
- shadcn-auditSkill
- spec-to-issuesSkill
- subagent-driven-developmentSkill
- teachSkill
- unslopSkill
- using-git-worktreesSkill
- visual-computer-use-loopSkill
- writing-flowSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 58
After saving, Read the image file to analyze it — that's how the agent "sees" the result.
≈ “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
Screen Capture (Wayland / Hyprland)
grim captures; slurp selects a region interactively; hyprctl + jq give
geometry for non-interactive captures. Output goes to a file or to wl-copy.
Requires grim and slurp (both present on this machine). Wayland only — scrot
/maim won't work here.
Full screen
grim ~/screenshot.png # focused output (or all, depending on setup)
grim -o "$(hyprctl monitors -j | jq -r '.[] | select(.focused).name')" ~/focused-monitor.pngInteractive region (you draw the box)
grim -g "$(slurp)" ~/region.pngActive window — no interaction
geom=$(hyprctl activewindow -j | jq -r '"\(.at[0]),\(.at[1]) \(.size[0])x\(.size[1])"')
grim -g "$geom" ~/active-window.pngPick a specific window by class — no interaction
geom=$(hyprctl clients -j | jq -r '.[] | select(.class=="firefox") | "\(.at[0]),\(.at[1]) \(.size[0])x\(.size[1])"' | head -1)
grim -g "$geom" ~/firefox.pngTo the clipboard (no file)
grim - | wl-copy --type image/png # full screen → clipboard
grim -g "$(slurp)" - | wl-copy --type image/png # region → clipboardSmaller / compressed (good for feeding to a model)
grim -t jpeg -q 75 ~/shot.jpg # JPEG at quality 75
grim -t png -l 6 ~/shot.png # PNG compression levelReading it back
After saving, Read the image file to analyze it — that's how the agent "sees"
the result. Keep captures in /tmp or a scratch dir and clean up after.
Gotchas
- Scaling:
grimsaves at the output's physical pixel resolution. If a monitor hasscale ≠ 1(hyprctl monitors -j | jq '.[].scale'), image pixels = logical × scale. To turn a pixel you see in the screenshot into a cursor coordinate, divide byscale. This is the #1 mistake when clicking from a screenshot — see visual-computer-use-loop. - Multi-monitor: without
-o/-g,grimmay stitch all outputs; pass-ofor one monitor or-gfor an exact box. - Timing: capture after the UI has settled; add a brief wait after launching or focusing a window before grabbing it.
Pairs with
- hyprland-control — geometry of windows/monitors to capture.
- visual-computer-use-loop — capture → reason → act → re-capture.
- screen-recording — for motion instead of a still (separate skill).
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.

