preview-shots
Skill1 starsChanged 15 days agoMITView on GitHub
Open image shots (screenshots, snapshot baselines, montages, renders) in ONE macOS Preview window so the user can eyeball them. Use when the user asks to open / show / pull up / review shots in Preview or Finder, or right after producing visual artifacts the user should look at before signing off.
4 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- dzhng/jevgrepedited, first seen Nov 7, 2026
- dzhng/skillsedited, first seen Nov 4, 2026
- dzhng/duet-agentedited, first seen Oct 30, 2026
- dzhng/yapedited, first seen Oct 15, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- dzhng/jevgrep★ 3.2k98% same
- dzhng/skills★ 1.5k98% same
- dzhng/yap★ 11298% same
- dzhng/duet-agent★ 5598% same
Wrote their own version · 0
None found.
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 repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- a11ySkill
- agents-mdSkill
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- askSkill
- audit-agentsSkill
- audit-choicesSkill
- audit-performanceSkill
- audit-testsSkill
- auto-researchSkill
- close-specSkill
- code-reviewSkill
- compare-screenshotsSkill
- debugSkill
- design-mdSkill
- design-with-imagesSkill
- document-codebaseSkill
- eli5Skill
- eval-skillsSkill
- explore-unknownsSkill
- handoff-specSkill
- implementSkill
- learnSkill
- marketing-pagesSkill
- memorySkill
- okf-contextSkill
- quick-planSkill
- ratchet-filesSkill
- refactor-cleanSkill
- rememberSkill
- repoagent-doc-generationSkill
- retroSkill
- reviewSkill
- rtkSkill
- screenshot-critiqueSkill
- specifySkill
- spec-planSkill
- spec-tasksSkill
- statusSkill
- system-designSkill
- verifySkill
- write-docsSkill
- write-skillsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 1 is common, 0 are distinctive, and 2 are very specific to this project.
1
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 8
Put the review-worthy images in front of the user in a single Preview window they can flip through.
- Very specific: line 23
One set at a time — never pile up windows: Before opening a new set, close any open ones: osascript -e 'tell application "Preview" to close …
- Very specific: line 25
Close on unattended proceed: When you opened shots for a non-blocking review and then move on without the user's response, close Preview …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Preview Shots
Put the review-worthy images in front of the user in a single Preview window they can flip through.
Workflow
- Curate the set — the images that answer "is this right?": the just-changed or just-blessed baselines, the integrated result, and the reference image when there's something to compare against. Don't dump every PNG in the folder; pick the smallest set that lets the user judge the change. If the user named specific shots, open exactly those.
- One window — open them with a single
buddhi / OS image viewer or Antigravity artifact preview (Windows: Start-Process, macOS: open -a Preview, Linux: xdg-open) <path> <path> ...call. Oneopeninvocation lands all the files in one window with a thumbnail sidebar; separate calls spawn separate windows. - Caption them — list one line per shot (what it is) so the user knows what they're flipping through.
Rules
- macOS only (
open); pass absolute or repo-root-relative paths. - Order the files most-important-first; the first one is what Preview shows on open.
- Review saved PNG/GIF artifacts, not live Chrome. Exact regression capture should run headless by default; only open Chrome when the user explicitly asks for a live browser or when reproducing a headful-only bug.
- One set at a time — never pile up windows. Before opening a new set, close
any open ones:
osascript -e 'tell application "Preview" to close every window'. - Close on unattended proceed. When you opened shots for a non-blocking review
and then move on without the user's response, close Preview afterward:
osascript -e 'quit app "Preview"'. An overnight autonomous run must never wake the user to a wall of Preview windows — at most one set open, and none once you've proceeded past the checkpoint.
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.