/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

BOOST

stellarlinkco@stellarlinkco

GitHub

From plugin

stellarlinkco-myclaude

2.8k11 skills19 agents13 commands2 hooks

Install

$ npx -y skills add stellarlinkco/myclaude --skill browser --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/browser

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

browser.SKILL.md

name: browser
description: 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:

npm install --prefix ~/.claude/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

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