browse
Skill0 starsChanged 5 months agoMITView on GitHub
Read and interact with Chrome browser tabs using DOM-based reading (not screenshots). Opens URLs, reads page content via accessibility tree and text extraction, finds elements, fills forms, and executes JavaScript. Use whenever you need to view or interact with a web page.
53 other projects use a version of this.
Adopted by
Most recently taken up by
- lohi-ai/babysittheir own version, first seen Nov 8, 2026
- MildlyMeticulous/shortlisttheir own version, first seen Nov 8, 2026
- timurgaleev/vibestacktheir own version, first seen Nov 8, 2026
- WordPress/gutenbergtheir own version, first seen Nov 1, 2026
- AhmedMerza/claude-skillstheir own version, first seen Nov 1, 2026
- AhmedMerza/agent-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use setup-gbrain, open-gstack-browser and 10 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.
ShreyRaviSkillsetup-gbrain
Set up gbrain for this coding agent: install the CLI, initialize a local PGLite or Supabase brain, register MCP, capture per-remote trust policy. One command from zero to "gbrain is running, and this agent can call it." Use when: "setup gbrain", "connect gbrain", "start gbrain", "install gbrain", "configure gbrain for this machine". (gstack)
Also in 9 projects that use this
seek888Skillopen-gstack-browser
Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".
Also in 11 projects that use this
Saqlain-811Skillios-sync
Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)
Also in 6 projects that use this
ayudaySkillsetup-deploy
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".
Also in 19 projects that use this
- ShreyRaviSkill
landing-report
Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Also in 9 projects that use this
- Saqlain-811Skill
ios-clean
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Also in 5 projects that use this
- +3 more from ShreyRavi
- +1 more from Saqlain-811
Other versions53 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 53
- garrytan/gstack★ 141ksame name
- WordPress/gutenberg★ 12ksame name
- SeifBenayed/cloclo★ 114same name
- mr-daedalium/ostack-saas★ 108same name
- no-session/pstack★ 96same name
- lucas-flatwhite/gstack-ko★ 45same name
- shipshitdev/skills★ 39same name
- WillNigri/Agentic-Tool-Optimization★ 34same name
- Scino/fstack★ 18same name
- ulpi-io/browse★ 15same name
43 more not listed
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.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- discoverSkill
- onboardSkill
- rememberSkill
- scaffold-clientSkill
- scaffold-projectSkill
- scaffold-taskSkill
- scaffold-viewerSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read and interact with Chrome browser pages using DOM-based tools.
- Very specific: line 16
Always start by calling mcp__claude-in-chrome__tabs_context_mcp to see existing browser tabs.
- Distinctive: line 23
If the user provided a URL argument, open it now.
- Very specific: line 30
Use read_page first. Fall back to get_page_text if you need cleaner prose (e.g., reading an article or documentation page).
- Very specific: line 45
Use mcp__claude-in-chrome__gif_creator to record multi-step browser interactions as a GIF for the user to review.
- Distinctive: line 53
Bail out after 2-3 failures: If browser tools fail or return errors after 2-3 attempts, stop and ask the user for guidance.
- Very specific: line 55
Never reuse tab IDs from a previous session: Always call tabs_context_mcp to get fresh tab IDs if there's any doubt.
“Common” is measured: kept by at least 6 in 10 of the 45 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
Browse
Read and interact with Chrome browser pages using DOM-based tools.
Workflow
1. Get tab context
Always start by calling mcp__claude-in-chrome__tabs_context_mcp to see existing browser tabs.
2. Open a page
- New tab:
mcp__claude-in-chrome__tabs_create_mcpwith the target URL - Existing tab:
mcp__claude-in-chrome__navigateto change the URL of a known tab
If the user provided a URL argument, open it now.
3. Read page content
- Primary:
mcp__claude-in-chrome__read_page-- returns the accessibility tree of DOM elements (structured, interactive elements visible) - Text extraction:
mcp__claude-in-chrome__get_page_text-- returns extracted text content, prioritizes article/main content
Use read_page first. Fall back to get_page_text if you need cleaner prose (e.g., reading an article or documentation page).
4. Find and interact with elements
- Find elements:
mcp__claude-in-chrome__find-- use natural language queries to locate elements (e.g., "login button", "email input field") - Fill forms:
mcp__claude-in-chrome__form_input-- use element reference IDs returned byfindto fill inputs, click buttons, select options - Run JavaScript:
mcp__claude-in-chrome__javascript_tool-- execute custom DOM queries or page manipulation when the other tools are insufficient
5. Debug
- Console logs:
mcp__claude-in-chrome__read_console_messages-- read browser console output (usepatternparameter to filter) - Network requests:
mcp__claude-in-chrome__read_network_requests-- inspect network traffic for API calls, errors, etc.
6. Record interactions (optional)
Use mcp__claude-in-chrome__gif_creator to record multi-step browser interactions as a GIF for the user to review.
Critical Rules
- NEVER use
mcp__claude-in-chrome__computerfor reading pages. Always useread_pageandget_page_textfor DOM-based content extraction. Thecomputertool uses screenshots which are slower, less structured, and more token-expensive. - Never trigger JavaScript alerts, confirms, or prompts. These browser dialogs block all further browser events and prevent the extension from receiving commands. Use
console.log+read_console_messagesfor debugging instead. - Bail out after 2-3 failures. If browser tools fail or return errors after 2-3 attempts, stop and ask the user for guidance. Do not loop or retry indefinitely. Explain what you tried and what went wrong.
- Never reuse tab IDs from a previous session. Always call
tabs_context_mcpto get fresh tab IDs if there's any doubt.
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.