page-shot
From the author
Open the page linked in an issue in a headless browser.
Install
npx skills add Goldziher/ai-rulez --skill page-shot -a claude-code
Installs to .claude/skills/page-shot/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 78
Security85
Provenance67
Maintenance100
Licence100
Adoption38
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- browsenota-america/forgecat-agent-profilesDrive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack)Browser★ 93
- frontend-slidesnotque/vexjoy-agentBrowser-based HTML presentation generation.Documents★ 443
- browsercode-yeongyu/oh-my-openagentDrives a real browser through the omowright library from the js eval kernel: sites the user is already signed into, forms and clicks, JS-rendered pages, screenshots, web QA, extension popups, a human handoff for login, CAPTCHA or OTP, and a browser you own for scraping, bot-scored targets, network capture and QA traces. Use for any interactive browser task; not for a plain search or an unblocked static fetch.Browser★ 70.3K
- scrapenota-america/forgecat-agent-profilesPull data from a web page through the Aside browser — your real, already signed-in sessions. (gstack)Browser★ 93
- web-scraperskrun-dev/skrunBrowse websites and extract structured information. Use when the user needs data from a web page.Browser★ 210
- playwright-browserAndyShiu/claude-skill-playwright-browserHeadless, reproducible browser automation with Playwright for any project — screenshots of web pages or local dev servers (desktop/tablet/mobile, full page or one element, single page or every page/menu of an app in one batch), frontend audits (console errors, failed requests, broken images/links, responsive overflow, axe accessibility, LCP/CLS performance), before/after visual comparison, scripted E2E flows (log in, click, fill, page through, assert), and logged-in pages via saved sessions. Use this whenever the user wants to screenshot or visually check a site, find frontend bugs, see how a page looks on mobile, compare the UI before and after a CSS/code change, reproduce a bug from an issue or ticket and capture evidence images for it, verify a UI flow works, or run/write a browser test — even if they never say "Playwright" or "browser". If Claude in Chrome could also do the job, briefly ask which to use (with a recommendation) instead of silently picking.Testing★ 51
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in