screenshot-capture
Skill24 starsChanged 27 days agoMITView on GitHub
Capture real, safe screenshots of a running project with Playwright for the README. Use when a repo needs screenshots or a demo GIF.
- Installs packages
3 other projects use a version of this.
Adopted by
Most recently taken up by
- OneByJorah/VirtOfficeword for word, first seen Nov 1, 2026
- taskmasterpeace/ship-packtheir own version, first seen Jun 18, 2026
- paolomoz/skillstheir own version, first seen Feb 3, 2026
Other versions3 projects use a version of this.
Word for word · 1
- OneByJorah/VirtOffice★ 24100% same
Edited · 0
None found.
Wrote their own version · 2
- paolomoz/skills★ 4same name
- taskmasterpeace/ship-pack★ 0same 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dockerizeSkill
- pr-workflowSkill
- readme-writerSkill
- release-checklistSkill
- repo-polishSkill
- security-scrubSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Start the stack: docker compose up -d --build.
- Very specific: line 22
Stop the stack: docker compose down -v.
≈ “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-capture
Rules
- Screenshots must be real: taken from the running app, never mockups.
- Demo data only. Run with
DEMO_MODE=trueand seeded fake data. Never real hostnames, IPs, usernames, emails, school, or client names. - The capture script scans page text for private IPs, tailnet IPs, emails, and forbidden words, and refuses to save on a match. Add project-specific patterns with
SCRUB_PATTERNS.
Steps
- Start the stack:
docker compose up -d --build. Wait for/healthz. - Edit the
PAGESlist inscripts/screenshots.mjs: one entry per meaningful screen (dashboard, main workflow, settings). npm install --no-save playwright && npx playwright install chromiumnode scripts/screenshots.mjs(setRECORD=1for a shortdemo.gif, needs ffmpeg).- Open the images and look at each one. Check for real data, empty states, and error messages.
- Optimize PNGs:
optipng -o2 docs/screenshots/*.png. - Stop the stack:
docker compose down -v.
Output
docs/screenshots/<name>.png at 1440x900 @2x, dark color scheme, matching the J1 design language. Reference them in the README with alt text.
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.

