Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →code-yeongyu/dev-browser
Browser automation with persistent page state.
Passed 15 of 18 test cases with the skill, and 5 of 18 without it.
and 13 more in the full report
13 fixed5 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
After calling `page.goto('https://example.com')` in a dev-browser script, what helper function from the dev-browser client module should be used to wait for page load completion?
| Checked | Without skill | With skill |
|---|---|---|
| Imports and calls `waitForPageLoad(page)` from `@/client.js`. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
getAISnapshot() to discover elements and selectSnapshotRef() to interact with themInstallation: See references/installation.md for detailed setup instructions including Windows support.
Two modes available. Ask the user if unclear which to use.
Launches a new Chromium browser for fresh automation sessions.
./skills/dev-browser/server.sh &
Add --headless flag if user requests it. Wait for the Ready message before running scripts.
Connects to user's existing Chrome browser. Use this when:
Important: The core flow is still the same. You create named pages inside of their browser.
Start the relay server:
cd skills/dev-browser && npm i && npm run start-extension &
test cases passed, vs 5 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.