More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Page Shots: Every Page at Desktop and Phone Width

    1

    A full-page screenshot of a long page at phone width is a 360 px strip nobody can read.

    Free

    Security scanned
    Page Shots: Every Page at Desktop and Phone Width

    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

    PageWidthProblemWhere to start
    /wide.htmlphonepage 708 px on a 360 px screendiv.hero-table is 700 px wide; let it wrap or scroll inside its own box
    /missing.htmlboth404the home page links to a page that does not exist; remove the link or add the page
    /bothbroken image/nope.png is missing
    /about/bothscript error on loadthe 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

    Generated

    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

    1. 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.
    2. 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 --hide so they do not appear mid-page.
    3. 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).
    4. Clicks first if needed: a pages.json can list click steps (open the menu, open a tab) for states a plain load does not show.
    5. 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.

    Source: https://github.com/Stophyuk/solutionzip-skills

    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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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

    Node.js 18+
    playwright
    Node.js

    Permissions

    Browser
    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed16 days ago

    What's inside

    Frequently Asked Questions

    A 4,000 px phone page shrunk to fit a review window is unreadable. One screen per image keeps text at real size, and the phone screens are also paired two side by side so a long page reads like a spread.

    No. It only loads pages. Optional click steps in pages.json are for opening menus or tabs; the skill tells the agent not to touch login, payment or submit buttons.

    Yes, any address the browser can open, including localhost. Shooting the dev server also keeps test visits out of your live analytics.

    New in Testing & Debugging