full-page-screenshot
Use when the user asks to capture a full-page screenshot, long screenshot, or complete page capture of a web page. Handles SPA scroll containers, lazy-loaded images, and very tall pages via Chrome DevTools Protocol with zero external dependencies.
Profile →npx skills add alirezarezvani/claude-skills --skill full-page-screenshot --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Full Page Screenshot Capture a full-page screenshot of any web page via Chrome DevTools Protocol. Produces a single PNG that includes all content — even portions that require scrolling. Zero external dependencies beyond Node.js 22+ and Chrome with remote debugging enabled. ## Prerequisites - **Node.js 22+** (uses built-in `WebSocket`) - **Chrome/Chromium** with remote debugging enabled Check environment readiness: ```bash node "${SKILL_DIR}/scripts/full-page-screenshot.mjs" --check ``` If Chrome check fails, instruct user to open `chrome://inspect/#remote-debugging` and enable **"Allow remote debugging for this browser instance"**. ## Workflow ### Option A: Screenshot an already-open tab (recommended for authenticated pages) 1. List available tabs: ```bash node "${SKILL_DIR}/scripts/full-page-screenshot.mjs" --list ``` 2. Identify the target by title/URL, then capture: ```bash node "${SKILL_DIR}/scripts/full-page-screenshot.mjs" <targetId> /tmp/screenshot.png --width 1200 --dpr 1 ``` ### Option B: Screenshot a URL (opens a background tab, captures, closes) ```bash node "${SKILL_DIR}/scripts/full-page-screenshot.mjs" --url "https://example.com" /tmp/screenshot.png --width 1200 --d
- Prerequisites
- Workflow
- Option A: Screenshot an already-open tab (recommended for authenticated pages)
- Option B: Screenshot a URL (opens a background tab, captures, closes)
- Parameters
- Verify Output
- Core Capabilities
- How It Works
- Anti-Patterns
- Troubleshooting
- Cross-References
node "${SKILL_DIR}/scripts/full-page-screenshot.mjs" --check
node "${SKILL_DIR}/scripts/full-page-screenshot.mjs" --list
node "${SKILL_DIR}/scripts/full-page-screenshot.mjs" <targetId> /tmp/screenshot.png --width 1200 --dpr 1
node "${SKILL_DIR}/scripts/full-page-screenshot.mjs" --url "https://example.com" /tmp/screenshot.png --width 1200 --dpr 1 --wait 15000
macOS
sips -g pixelWidth -g pixelHeight /tmp/screenshot.png
Linux
file /tmp/screenshot.pngWhat does the full-page-screenshot skill do?
Use when the user asks to capture a full-page screenshot, long screenshot, or complete page capture of a web page. Handles SPA scroll containers, lazy-loaded images, and very tall pages via Chrome DevTools Protocol with zero external dependencies.
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill full-page-screenshot --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.