screenshot
Skill15 starsChanged 5 months agoMITView on GitHub
Render a local web page / built site and capture full-page screenshots (desktop + mobile) using the pre-installed Chromium. Use when asked to screenshot, render, or "see how it looks" for the vigiles landing site (site/), the audit report (report/), or any local HTML/dev server. Handles the scroll-reveal gotcha (below-the-fold cards captured blank) automatically.
- Installs packages
52 other projects use a version of this.
Adopted by
Most recently taken up by
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- 5uck1ess/devkittheir own version, first seen Nov 15, 2026
- bordenet/superpowers-plustheir own version, first seen Nov 13, 2026
- GuppyTheCat/skillstheir own version, first seen Nov 8, 2026
- its-ash/skillstheir own version, first seen Nov 1, 2026
- rondomondo/agent-skills-toolboxtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use spreadsheet, obsidian-vault and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JetBrainsSkillspreadsheet
Use when tasks involve creating, editing, analyzing, or formatting spreadsheets (`.xlsx`, `.csv`, `.tsv`) with formula-aware workflows, cached recalculation, and visual review.
Also in 3 projects that use this
simo97Skillobsidian-vault
Also in 4 projects that use this
JetBrainsSkillslides
Create and edit presentation slide decks (`.pptx`) with PptxGenJS and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.
Also in 5 projects that use this
simo97Skilledit-article
The user will invoke this skill to help them edit an article.
Also in 3 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 3 projects that use this
LesaniSkillwriting-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
Also in 3 projects that use this
Other versions52 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 52
- openai/skills★ 27ksame name
- openstatusHQ/openstatus★ 9.3ksame name
- iPlug2/iPlug2★ 2.4ksame name
- OpenEnroth/OpenEnroth★ 890same name
- RandallLiuXin/GodotMaker★ 555same name
- JetBrains/skills★ 386same name
- mycelium-io/mycelium★ 128same name
- app-dev-panel/app-dev-panel★ 91same name
- z91772524-ai/pojia-next-mac★ 39same name
- Agent-Deployment-Co/argus★ 33same name
42 more not listed
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.
- CLAUDE.mdCLAUDE.md
- examples/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- add-a-linterSkill
- audience-checkSkill
- audit-feedback-loopSkill
- code-qualitySkill
- deep-researchSkill
- dogfood-cliSkill
- enforce-rules-formatSkill
- generate-logoSkill
- hexagonal-architectureSkill
- landing-siteSkill
- pr-to-lint-ruleSkill
- review-docsSkill
- ship-a-featureSkill
- verify-docs-findableSkill
- pr-to-lint-ruleSkill
- adopt-specSkill
- debug-my-harnessSkill
- edit-specSkill
- linter-docsSkill
- strengthenSkill
- test-harnessSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 48 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
If cards are blank, this is why.
“Common” is measured: kept by at least 6 in 10 of the 48 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
screenshot — render a local page and capture it
Contributor dev skill. Drives the container's pre-installed Chromium (no playwright install,
no browser download) via playwright-core to full-page-screenshot a locally-served page. Built
from the hard-won gotchas of doing this by hand (see below).
When to use
- "screenshot the landing page / site", "how does the report look", "render
site/and show me". - Verifying a UI change in
site/(the landing) orreport/(the audit report) before committing.
Procedure
- Build the target (if it's a Vite app, you need
dist/):- Landing:
cd site && npm install && npm run build→site/dist/ - Report: it builds with the root
npm run build→dist/audit-report.template.html
- Landing:
- Serve it on a port (relative asset refs need the dir as web root):
cd site/dist && python3 -m http.server 8899 >/tmp/httpd.log 2>&1 & sleep 1 && curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8899/ # expect 200 - Ensure the driver (no browser download — uses
PLAYWRIGHT_BROWSERS_PATH):node -e "require.resolve('playwright-core')" 2>/dev/null || npm install --no-save playwright-core - Shoot with the bundled script → writes
<outDir>/<name>-desktop.png+-mobile.png:
Override viewports withnode .claude/skills/screenshot/scripts/shot.mjs http://localhost:8899/ "$SCRATCHPAD" landingSHOT_WIDTHS="1440x900,768x1024,390x844". - Look before sending:
Readthe desktop PNG to sanity-check it rendered, THENSendUserFile(display: render) so the user sees it. Send to the scratchpad dir, not the repo.
Gotchas this skill encodes (don't relearn them)
- Scroll-reveal = blank cards. Sections that fade in on scroll (
opacity-0+ IntersectionObserver) are captured INVISIBLE by a naivefullPagescreenshot — the hero renders, everything below the fold is blank. The script scrolls top→bottom to trigger the reveals, then returns to top before shooting. If cards are blank, this is why. - Chromium is pre-installed at
/opt/pw-browsers/chromium-*/chrome-linux/chrome; pass it asexecutablePath+--no-sandbox. NEVER runplaywright install(blocked; wastes time). - CJS-from-ESM import:
playwright-core's entry is CJS, and a script run from the scratchpad can't resolve the repo'snode_modulesby a bare import — usecreateRequire(cwd + '/package.json')(the script does this). - Mobile uploads sometimes 400 on
SendUserFile— retry once, or send desktop alone.
Not shipped
This is a .claude/ contributor skill (this repo's own harness), not a published consumer 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.

