// 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.
Execute codeagent-wrapper for multi-backend AI code tasks. Supports Codex, Claude, Gemini, and OpenCode backends with agent presets, skill injection, file references (@syntax), worktree isolation, parallel execution, and structured output.
This skill should be used for multi-session autonomous agent work requiring progress checkpointing, failure recovery, and task dependency management. Triggers on '/harness' command, or when a task involves many subtasks needing progress persistence, sleep/resume cycles across context windows, recovery from mid-task failures with partial state, or distributed work across multiple agent sessions. Synthesized from Anthropic and OpenAI engineering practices for long-running agents.
This skill should be used for structured feature development with codebase understanding. Triggers on /do command. Provides a 5-phase workflow (Understand, Clarify, Design, Implement, Complete) using codeagent-wrapper to orchestrate code-explorer, code-architect, code-reviewer, and develop agents in parallel.
Use this skill when you see `/omo`. Multi-agent orchestration for "code analysis / bug investigation / fix planning / implementation". Choose the minimal agent set and order based on task type + risk; recipes below show common patterns.
Minimal SPARV workflow (Specify→Plan→Act→Review→Vault) with 10-point spec gate, unified journal, 2-action saves, 3-failure protocol, and EHRB risk detection.
Extreme lightweight end-to-end development workflow with requirements clarification, intelligent backend selection, parallel codeagent execution, and mandatory 90% test coverage
| 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. |
Minimal Chrome DevTools Protocol (CDP) helpers for browser automation without MCP server setup.
Install dependencies before first use:
npm install --prefix ~/.claude/skills/browser/browser ws
All scripts connect to Chrome on localhost:9222.
scripts/start.js # Fresh profile
scripts/start.js --profile # Use persistent profile (keeps cookies/auth)
scripts/nav.js https://example.com # Navigate current tab
scripts/nav.js https://example.com --new # Open in new tab
scripts/eval.js 'document.title'
scripts/eval.js '(() => { const x = 1; return x + 1; })()'
Use single expressions or IIFE for multiple statements.
scripts/screenshot.js
Returns { path, filename } of saved PNG in temp directory.
scripts/pick.js "Click the submit button"
Returns element metadata: tag, id, classes, text, href, selector, rect.
scripts/start.js --profile for authenticated sessionsscripts/nav.js <url>scripts/eval.js 'document.querySelector(...)'scripts/screenshot.js or scripts/pick.js--profile flag to preserve cookies and auth tokens