browser-screenshot
Take focused, region-specific screenshots from web pages. Navigates to the right page based on user context (URL, search query, social media post), locates the target region via DOM selectors, and crops to a clean, focused screenshot.
Security Assessment
Detected risks:
About browser-screenshot
A pipeline for capturing focused, region-specific screenshots from web pages rather than noisy full-page dumps. The workflow moves through four stages: research the best page to capture, navigate to it in Chrome, locate the target region via a CSS selector, and capture a cropped screenshot of just that region. A hard rule forbids emitting an uncropped full-viewport or full-page screenshot as a final result, since navigation bars, sidebars, and ads make such images unsuitable as article illustrations. The prerequisite is the agent-browser tool with Chrome running under remote debugging.
A research-first principle drives the early steps: the browser is treated as a capture tool, not a browsing tool. Text-based tools (WebSearch and WebFetch) are used first to find candidate pages, read their content, and decide which are worth screenshotting, eliminating poor candidates cheaply before any browser navigation. The skill also defines when to skip straight to Chrome instead — when the target platform gates content behind a login wall (Reddit, LinkedIn, X/Twitter), when the user names a platform with a clear search need, or when WebFetch returns blocked or incomplete content such as a 403 or CAPTCHA. Guidance on what makes a good source emphasizes content over chrome: blog post sections with a heading and a paragraph or two, a single chart, a HuggingFace model-card header, or a key quote, while avoiding busy landing pages dominated by buttons and forms.
Operationally it always starts by listing existing browser tabs to reuse logged-in sessions, then navigates by input type — direct URL, search query, or a constructed platform search URL (patterns are given for Reddit, X/Twitter, LinkedIn, Hacker News, GitHub, and YouTube). After navigation it waits for the page to settle with networkidle, noting that some sites never reach that state and a fixed wait is a safe fallback. The critical region-location step centers on discovering a precise DOM selector that wraps exactly the content to capture, beginning with an annotated screenshot to understand page layout.
FAQ
What does this skill require to run?
agent-browser must be installed and Chrome must have remote debugging enabled. The doc points to references/agent-browser-setup.md if the setup is unclear.
Will it ever return a full-page screenshot?
No. A hard rule forbids outputting an uncropped full-viewport or full-page screenshot as a final result; every screenshot must be cropped to a focused region.
When should I use browser-first instead of researching with WebSearch first?
Go straight to Chrome when the platform requires login (Reddit, LinkedIn, X/Twitter), when the user names a platform with a clear search need, or when WebFetch returns blocked or incomplete content like a 403 or CAPTCHA.
How does it find the exact area to capture?
It discovers a CSS selector that precisely wraps the target content, typically starting with an annotated screenshot to understand the page layout before selecting the region.
Does it support social platforms like Reddit and X?
Yes. It includes platform-specific search URL patterns for Reddit, X/Twitter, LinkedIn, Hacker News, GitHub, and YouTube, and reuses existing logged-in Chrome tabs for gated content.
Install browser-screenshot
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
zc277584121/marketing-skills