- Home
- Skills
- Testing & Debugging
- Page Shots: Every Page at Desktop and Phone Width
More screenshots
Works with the AI Agents you already use
Page Shots: Every Page at Desktop and Phone Width
A full-page screenshot of a long page at phone width is a 360 px strip nobody can read.
Free
Page Shots: Every Page at Desktop and Phone Width
Example session with this skill installed
전 페이지 캡처해줘: http://localhost:8765 — 폰에서 깨지는 데 찾아줘. (Screenshot every page and find what breaks on a phone.)
- Read your context and instructions
- Compiled the page shots
- Generated the UI component
Summary
Ran on a small local test site with problems planted on purpose. 4 pages found from the home page links, 8 page-width runs. 3 failures, 4 warnings.
Pages
No sitemap.xml, so pages came from the home page links: /, /about/, /wide.html, /missing.html. The fixed bottom bar was hidden with --hide ".bar".
Run (real output)
$ node shots.mjs http://localhost:8765 --hide ".bar"
페이지 4개 (home page links)
home d 2817px · 4장
home m 2817px · 4장
about d 800px · 1장
about m 780px · 1장
wide-html d 800px · 1장
wide-html m 1534px · 2장 · 실패 1
missing-html d 800px · 1장 · 실패 1
missing-html m 2124px · 3장 · 실패 1
✗ /wide.html (m) 가로로 밀림: 페이지 708px > 화면 360px (가장 튀어나온 것 <div class="hero-table"> 708px)
✗ /missing.html (d) HTTP 404
✗ /missing.html (m) HTTP 404
4페이지 · 실패 3 · 경고 4 → shots/index.html
(d = desktop 1366, m = phone 360, 장 = images, 실패 = fail, 가로로 밀림 = scrolls sideways, 경고 = warnings.)
Warnings from report.json
/(both widths): an image did not load:/nope.png/about/(both widths): script error:boom
Fix list
| Page | Width | Problem | Where to start |
|---|---|---|---|
| /wide.html | phone | page 708 px on a 360 px screen | div.hero-table is 700 px wide; let it wrap or scroll inside its own box |
| /missing.html | both | 404 | the home page links to a page that does not exist; remove the link or add the page |
| / | both | broken image | /nope.png is missing |
| /about/ | both | script error on load | the inline script throws boom |
All images are in shots/; open shots/index.html to scroll through every page and width. After fixing, run the same command again to compare.
wide.html
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
A full-page screenshot of a long page at phone width is a 360 px strip nobody can read. This skill cuts each page into one screen per image, pairs the phone screens two by two, and puts everything on one index.html, so you can review a whole site in a few minutes before a release or a handover.
What it does
- Finds the pages from
/sitemap.xml(one level of sitemap index), or the links on the home page (same site only). Up to 30 by default, or pass paths yourself. - Shoots each page at 1366x800 and 360x780 (2x), reduced motion, after waiting for fonts and scrolling once so lazy images load. Fixed bars (cookie banners, chat buttons) can be hidden with
--hideso they do not appear mid-page. - Checks every page and width and writes
report.json:- Fail: HTTP 400+, page did not open, page wider than the phone screen (it names the element sticking out furthest, with its tag, class and right edge).
- Warn: images that never loaded, JavaScript errors, non-UTF-8 documents (Korean or other non-Latin text can turn into mojibake).
- Clicks first if needed: a
pages.jsoncan list click steps (open the menu, open a tab) for states a plain load does not show. - You get the failures first, then the agent opens the images and reports what a machine cannot see: headings breaking badly, buttons overlapping, text too small.
Rules it follows
- Does not submit forms or touch login, payment or submit buttons.
- Keeps page counts small on sites that are not yours, and does not republish their screenshots.
- Reports only what needs fixing.
Instructions are in Korean; works on sites in any language.
Pages behind a login are not reached unless you give a logged-in-free preview address. Pages are found from sitemap.xml or the home page links, not by a deep crawl. A page longer than 14 screens is cut at 14 images (--chunks to change). Checks catch layout overflow and loading errors, not visual taste; that part is the agent reading the images. Instructions are in Korean.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 16 days ago
- Free with an Agensi account
Requires