browser-tools
Skill0 starsChanged 4 months agoMITView on GitHub
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
11 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- nurmdrafi/pi-nativetheir own version, first seen Oct 25, 2026
- cadecode/agent-skillsedited, first seen Oct 20, 2026
- fabioc-aloha/Alex_ACT_Editiontheir own version, first seen Oct 13, 2026
- Melv1C/skillstheir own version, first seen Oct 13, 2026
- SeanPedersen/agent-skillsedited, first seen Sep 26, 2026
- VodouAI/OStheir own version, first seen Jul 19, 2026
Used with
Projects with it also use web-search, systematic-debugging and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillweb-search
Also in 3 projects that use this
OpenAISkillsystematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 4 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- badlogic/pi-skills★ 2.5k86% same
- brettatoms/agent-skills★ 379% same
- SeanPedersen/agent-skills★ 384% same
- cadecode/agent-skills★ 154% same
- massielvasquez193-dot/Claude-skill★ 084% same
- wernerbatt-klz/claude-skills★ 048% same
Wrote their own version · 5
- nurmdrafi/pi-native★ 4same name
- b1tank/skills★ 1same name
- Melv1C/skills★ 1same name
- VodouAI/OS★ 1same name
- fabioc-aloha/Alex_ACT_Edition★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
All following commands shall be assumed to be launched inside {baseDir}/browser-tools, where the {baseDir} is the root of the skills …
- Distinctive: line 14
If any of the following scripts fail with the message like this:
- Distinctive: line 70
When you need specific selectors but the page structure is complex or ambiguous
- Distinctive: line 92
When user needs to visually see or interact with a page
- Distinctive: line 179
If DOM updates after actions, add a small delay with bash:
- Distinctive: line 187
Always start by understanding the page structure:
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Browser Tools
Chrome DevTools Protocol tools for agent-assisted web automation. These tools connect to Chrome running on :9222 with remote debugging enabled.
All following commands shall be assumed to be launched inside {baseDir}/browser-tools, where the {baseDir} is the root of the skills directory.
Installing chrome
If any of the following scripts fail with the message like this:
No compatible Chrome for Testing installation foundYou should first install compatible Chrome via the following command:
pnpx @puppeteer/browsers install chromeStart Chrome
pnpm run browser-start # Fresh profile
pnpm run browser-start --profile # Copy user's profile (cookies, logins)Launch Chrome with remote debugging on :9222. Use --profile to preserve user's authentication state.
Navigate
pnpm run browser-nav https://example.com
pnpm run browser-nav https://example.com --newNavigate to URLs. Use --new flag to open in a new tab instead of reusing current tab.
Evaluate JavaScript
pnpm run browser-eval 'document.title'
pnpm run browser-eval 'document.querySelectorAll("a").length'Execute JavaScript in the active tab. Code runs in async context. Use this to extract data, inspect page state, or perform DOM operations programmatically.
Screenshot
pnpm run browser-screenshotCapture current viewport and return temporary file path. Use this to visually inspect page state or verify UI changes.
Pick Elements
pnpm run browser-pick "Click the submit button"IMPORTANT: Use this tool when the user wants to select specific DOM elements on the page. This launches an interactive picker that lets the user click elements to select them. The user can select multiple elements (Cmd/Ctrl+Click) and press Enter when done. The tool returns CSS selectors for the selected elements.
Common use cases:
- User says "I want to click that button" → Use this tool to let them select it
- User says "extract data from these items" → Use this tool to let them select the elements
- When you need specific selectors but the page structure is complex or ambiguous
Cookies
pnpm run browser-cookiesDisplay all cookies for the current tab including domain, path, httpOnly, and secure flags. Use this to debug authentication issues or inspect session state.
Extract Page Content
pnpm run browser-content https://example.comNavigate to a URL and extract readable content as markdown. Uses Mozilla Readability for article extraction and Turndown for HTML-to-markdown conversion. Works on pages with JavaScript content (waits for page to load).
When to Use
- Testing frontend code in a real browser
- Interacting with pages that require JavaScript
- When user needs to visually see or interact with a page
- Debugging authentication or session issues
- Scraping dynamic content that requires JS execution
Efficiency Guide
DOM Inspection Over Screenshots
Don't take screenshots to see page state. Do parse the DOM directly:
// Get page structure
document.body.innerHTML.slice(0, 5000)
// Find interactive elements
Array.from(document.querySelectorAll('button, input, [role="button"]')).map(e => ({
id: e.id,
text: e.textContent.trim(),
class: e.className
}))Complex Scripts in Single Calls
Wrap everything in an IIFE to run multi-statement code:
(function() {
// Multiple operations
const data = document.querySelector('#target').textContent;
const buttons = document.querySelectorAll('button');
// Interactions
buttons[0].click();
// Return results
return JSON.stringify({ data, buttonCount: buttons.length });
})()Batch Interactions
Don't make separate calls for each click. Do batch them:
(function() {
const actions = ["btn1", "btn2", "btn3"];
actions.forEach(id => document.getElementById(id).click());
return "Done";
})()Typing/Input Sequences
(function() {
const text = "HELLO";
for (const char of text) {
document.getElementById("key-" + char).click();
}
document.getElementById("submit").click();
return "Submitted: " + text;
})()Reading App/Game State
Extract structured state in one call:
(function() {
const state = {
score: document.querySelector('.score')?.textContent,
status: document.querySelector('.status')?.className,
items: Array.from(document.querySelectorAll('.item')).map(el => ({
text: el.textContent,
active: el.classList.contains('active')
}))
};
return JSON.stringify(state, null, 2);
})()Waiting for Updates
If DOM updates after actions, add a small delay with bash:
sleep 0.5 && pnpm run browser-eval '...'Investigate Before Interacting
Always start by understanding the page structure:
(function() {
return {
title: document.title,
forms: document.forms.length,
buttons: document.querySelectorAll('button').length,
inputs: document.querySelectorAll('input').length,
mainContent: document.body.innerHTML.slice(0, 3000)
};
})()Then target specific elements based on what you find.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

