How do I install the Browser skill?

Run npx skillmds@latest add ahang1598/browser in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Browser safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Browser?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Browser free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Browser?

ahang1598 (@ahang1598) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Browser by ahang1598 — Agent Skill

Name: Browser
Rating: 4.2 (5 reviews)
Author: ahang1598

Browser

This skill should be used for browser automation tasks using Chrome DevTools Protocol (CDP). Triggers when users need to launch Chrome with remote debugging, navigate pages, execute JavaScript in browser context, capture screenshots, or interactively select DOM elements. No MCP server required.

ahang1598 Updated Sep 9, 2026 9 repo stars

File contents

Browser Automation

Minimal Chrome DevTools Protocol (CDP) helpers for browser automation without MCP server setup.

Setup

Install dependencies before first use:

npm install --prefix ~/.codebuddy/skills/browser/browser ws

Scripts

All scripts connect to Chrome on localhost:9222.

start.js - Launch Chrome

scripts/start.js              # Fresh profile
scripts/start.js --profile    # Use persistent profile (keeps cookies/auth)

nav.js - Navigate

scripts/nav.js https://example.com        # Navigate current tab
scripts/nav.js https://example.com --new  # Open in new tab

eval.js - Execute JavaScript

scripts/eval.js 'document.title'
scripts/eval.js '(() => { const x = 1; return x + 1; })()'

Use single expressions or IIFE for multiple statements.

screenshot.js - Capture Screenshot

scripts/screenshot.js

Returns { path, filename } of saved PNG in temp directory.

pick.js - Visual Element Picker

scripts/pick.js "Click the submit button"

Returns element metadata: tag, id, classes, text, href, selector, rect.

Workflow

Launch Chrome: scripts/start.js --profile for authenticated sessions
Navigate: scripts/nav.js <url>
Inspect: scripts/eval.js 'document.querySelector(...)'
Capture: scripts/screenshot.js or scripts/pick.js
Return gathered data

Key Points

All operations run locally - credentials never leave the machine
Use --profile flag to preserve cookies and auth tokens
Scripts return structured JSON for agent consumption

---name: browserdescription: This skill should be used for browser automation tasks using Chrome DevTools Protocol (CDP). Triggers when users need to launch Chrome with remote debugging, navigate pages, execute JavaScript in browser context, capture screenshots, or interactively select DOM elements. No MCP server required.--- # Browser Automation Minimal Chrome DevTools Protocol (CDP) helpers for browser automation without MCP server setup. ## Setup Install dependencies before first use: ```bash npm install --prefix ~/.codebuddy/skills/browser/browser ws ``` ## Scripts All scripts connect to Chrome on `localhost:9222`. ### start.js - Launch Chrome ```bash scripts/start.js # Fresh profile scripts/start.js --profile # Use persistent profile (keeps cookies/auth) ``` ### nav.js - Navigate ```bash scripts/nav.js https://example.com # Navigate current tab scripts/nav.js https://example.com --new # Open in new tab ``` ### eval.js - Execute JavaScript ```bash scripts/eval.js 'document.title' scripts/eval.js '(() => { const x = 1; return x + 1; })()' ``` Use single expressions or IIFE for multiple statements. ### screenshot.js - Capture Screenshot ```bash scripts/screenshot.js ``` Returns `{ path, filename }` of saved PNG in temp directory. ### pick.js - Visual Element Picker ```bash scripts/pick.js "Click the submit button" ``` Returns element metadata: tag, id, classes, text, href, selector, rect. ## Workflow 1. Launch Chrome: `scripts/start.js --profile` for authenticated sessions 2. Navigate: `scripts/nav.js <url>` 3. Inspect: `scripts/eval.js 'document.querySelector(...)'` 4. Capture: `scripts/screenshot.js` or `scripts/pick.js` 5. Return gathered data ## Key Points - All operations run locally - credentials never leave the machine - Use `--profile` flag to preserve cookies and auth tokens - Scripts return structured JSON for agent consumption

Frequently asked questions