AI SummaryThis skill enables AI assistants to control a live Chrome browser session for web automation tasks like navigation, interaction, data extraction, and screenshots directly within Factory CLI workflows. Developers and AI agents benefit from live browser control for testing, scraping, and task automation without leaving the coding environment.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "browser" skill in my project. Please run this command in my terminal: # Install skill into the correct directory (2 files) mkdir -p .claude/skills/browser && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/browser/SKILL.md "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/tools/browser/SKILL.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/browser/metadata.json "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/tools/browser/metadata.json" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Control a Chrome session via Stagehand to browse, act, extract, and screenshot on demand inside the Factory CLI.
Skill: Browser
Use this skill when you need live browser automation during a Factory session—opening sites, clicking through flows, gathering structured data, or capturing screenshots.
Inputs
• Target URL or task description (natural language) • Optional structured extraction schema (JSON field → type)
Behavior
• Ensure Chrome is running via Stagehand with the local profile stored in .chrome-profile. • Support these commands: • navigate <url>: open a page and capture a screenshot. • act "<instruction>": perform natural-language actions. • extract "<instruction>" '{"field":"type"}': return structured data. • observe "<goal>": list suggested steps the agent can take. • screenshot: capture the current viewport. • close: shut down the session when finished. • Save screenshots to agent/browser_screenshots and report the file path in the response. • When tasks finish, summarize what happened plus any follow-up steps for the user.
Verification
• If a navigation/action fails, include the error message and prompt the user for next steps. • Before ending the session, ensure close has been run so Chrome processes don’t linger.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster