Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
Control the user's real browser via Real Browser MCP. Use when asked to interact with web pages, test UIs, fill forms, or read page content.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Control Firefox browser from the command line. Use for web automation, scraping, testing, or any browser interaction tasks.
Control a real, local web browser to search, navigate, and extract information.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Use this skill to control the cmux terminal app from Claude Code. Trigger on "cmux", "open browser pane", "split pane", "browser split", "open in browser", "cmux browser", "cmux notify", "cmux split", "새 pane 열어", "브라우저 열어", "알림 보내", "사이드바", "workspace 만들어", "pane 분할", "browser automation", "cmux에서", "cmux로", "cmux 사용해서". Also trigger when the user wants to open a URL alongside their terminal, send notifications when a task completes, manage terminal panes programmatically, automate browser interactions from the CLI, or set sidebar status/progress for build scripts. Do NOT trigger for general tmux commands — cmux is a different app. If cmux is not detected (no socket, no CLI), inform the user and skip.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
MANDATORY browser verification after code changes. Activates when: implementing features, fixing bugs, modifying UI components, changing API endpoints, updating styles, refactoring code, or completing ANY task that changes application behavior. After writing or editing code files, you MUST verify changes through the browser-devtools MCP server and submit a verdict (pass or fail) before reporting task completion. If verification fails, submit the fail verdict before fixing. --- # IronBee Browser Verification ## Rule No task is complete until changes are verified in the browser — visually AND functionally. After verification, you MUST submit a verdict (pass or fail) before doing anything else. If verification fails, submit the fail verdict first, then fix. ## MCP Server Verification is performed using the **browser-devtools** MCP server (`browser-devtools-mcp` package). All browser interactions must go through this server's tools. ## Application Lifecycle
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.