Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows browser

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.

185 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

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.

When to use it

The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Browser Automation; Setup; Scripts; start.js - Launch Chrome; nav.js - Navigate; eval.js - Execute JavaScript. It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: besides SKILL.md, the body references scripts/start.js, scripts/nav.js, scripts/eval.js, scripts/screenshot.js, scripts/pick.js. Those resources load on demand.

Browser AutomationSetupScriptsstart.js - Launch Chromenav.js - Navigateeval.js - Execute JavaScriptscreenshot.js - Capture Screenshotpick.js - Visual Element PickerWorkflowKey Points

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
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.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 5
  • scripts/start.js
  • scripts/nav.js
  • scripts/eval.js
  • scripts/screenshot.js
  • scripts/pick.js

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "browser" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-7b9d1a082553dba3-Browser.html
Save it as .cursor/skills/browser/SKILL.md or .claude/skills/browser/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/stellarlinkco/myclaude instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/stellarlinkco/myclaude' --list

npx skills add 'https://github.com/stellarlinkco/myclaude' --skill 'browser'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- 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: ```bash npm install --prefix ~/.claude/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 ` 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

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…