Browser Access
Routes browser tasks to the right MCP (Claude in Chrome or Chrome DevTools) and handles logins without touching passwords
Free
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsBrowser Access
Example session with this skill installed
Open my local dev server at localhost:3000, check if the login button is visible, and if so, record a GIF of the loading state when I click it.
- Read your context and instructions
- Compiled the browser access
I will now inspect your local development server at `localhost:3000` using the Claude in Chrome MCP to verify the UI and record the interaction. 1. **Tab Context**: Checked existing tabs and created a new tab for localhost:3000. 2. **UI Verification**: Located the login button in the DOM and confirmed visibility via screenshot. 3. **Interaction**: Triggered the `gif_creator` tool while initiating the click event. ## Browser Inspection Results | Component | Status | Observation | | :--- | :--- | :--- | | **URL** | `http://localhost:3000` | Page loaded successfully. | | **Login Button** | Visible | Selector `button[type="submit"]` found in header. | | **Console Logs** | Clean | No errors detected during initial load. | | **GIF Recording** | Complete | Recorded 3.5 seconds of the transition to the dashboard. | The login button is present. I have recorded the loading state GIF as requested. The recording shows the spinner appearing for 400ms before the navigation occurs. **Next steps** - Review the captured GIF in the output directory to verify the spinner animation. - Let me know if you want to run a Lighthouse audit on this page to check performance scores. - I can also inspect the network requests if the loading state takes longer than expected.
Connects securely to your tools. The creator never sees your data.
About this skill
## What it does Browser Access tells your agent which browser MCP to use for a task, and what to do when it fails. - **Default to Claude in Chrome** for opening pages, clicking, filling forms, screenshots, reading DOM/console/network, and anything behind a login. It attaches to your real Chrome profile, so existing sessions just work. - **Fall back to Chrome DevTools MCP** only for the instrumentation it uniquely provides (e.g. performance traces), or when Claude in Chrome is unavailable. - **Login stays with you.** When a page shows a login screen or an MCP returns 401/403, the agent asks you to sign in in the browser and only verifies the result. It never types your password. - **Troubleshooting playbook** for disconnected extensions, missing site permissions, and DevTools ports that are not running. ## Who it's for Developers who use Claude Code (or another SKILL.md-compatible agent) for UI verification, visual checks, network debugging, or dev-server inspection, and are tired of the agent picking the wrong browser tool or getting stuck on auth. ## Requirements - Claude in Chrome extension and/or Chrome DevTools MCP configured in your agent. - No API keys or credentials needed.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 5 days ago
- Free to download with an account
Requires