browsing
Use when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content extraction via use_browser MCP tool
Install
git clone https://github.com/obra/superpowers-chrome /tmp/superpowers-chrome && ln -s /tmp/superpowers-chrome/skills/browsing ~/.claude/skills/browsing
From README
Browsing with Chrome Direct Overview Control Chrome via DevTools Protocol using the usebrowser MCP tool. Single unified interface with auto-starting Chrome. Announce: "I'm using the browsing skill to control Chrome." When to Use Use this when: Controlling authenticated sessions Managing multiple tabs in running browser Playwright MCP unavailable or excessive Use Playwright MCP when: Need fresh browser instances Generating screenshots/PDFs Prefer higher-level abstractions Auto-Capture Every DOM action (navigate, click, type, select, eval, keyboardpress, hover, dragdrop, doubleclick, rightclick, fileupload) automatically saves: {prefix}.png — viewport screenshot {prefix}.md — page content as structured markdown {prefix}.html — full rendered DOM {prefix}-console.txt — browser console messages Files are saved to the session directory with sequential prefixes (001-navigate, 002-click, etc.). You must check these before using extract or screenshot actions.
More skills
systematic-debugging
Used when encountering any bug, test failure, or unexpected behavior, before proposing fixes
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying...
dispatching-parallel-agents
Used when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
