dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
Profile →npx skills add code-yeongyu/oh-my-openagent --skill dev-browser --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Dev Browser Skill Browser automation that maintains page state across script executions. Write small, focused scripts to accomplish tasks incrementally. Once you've proven out part of a workflow and there is repeated work to be done, you can write a script to do the repeated work in a single execution. ## Choosing Your Approach - **Local/source-available sites**: Read the source code first to write selectors directly - **Unknown page layouts**: Use `getAISnapshot()` to discover elements and `selectSnapshotRef()` to interact with them - **Visual feedback**: Take screenshots to see what the user sees ## Setup > **Installation**: See [references/installation.md](references/installation.md) for detailed setup instructions including Windows support. Two modes available. Ask the user if unclear which to use. ### Standalone Mode (Default) Launches a new Chromium browser for fresh automation sessions. ```bash ./skills/dev-browser/server.sh & ``` Add `--headless` flag if user requests it. **Wait for the `Ready` message before running scripts.** ### Extension Mode Connects to user's existing Chrome browser. Use this when: - The user is already logged into sites and wants you to do things b
- Choosing Your Approach
- Setup
- Standalone Mode (Default)
- Extension Mode
- Writing Scripts
- Key Principles
- Workflow Loop
- No TypeScript in Browser Context
- Scraping Data
- Client API
- Waiting
- Inspecting Page State
- Screenshots
- ARIA Snapshot (Element Discovery)
cd skills/dev-browser && npm i && npm run start-extension & cd skills/dev-browser && npx tsx <<'EOF'
What does the dev-browser skill do?
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
How do I install it?
Run `npx skills add code-yeongyu/oh-my-openagent --skill dev-browser --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From code-yeongyu/oh-my-openagent, a repository with 67,209 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.