メニュー
Automated browser testing, interaction automation, and form testing. Use when the user needs to test web pages, automate browser interactions, fill forms, test validation, run multi-step wizards, or test login/signup flows.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | browser-testing |
| description | Automated browser testing, interaction automation, and form testing. Use when the user needs to test web pages, automate browser interactions, fill forms, test validation, run multi-step wizards, or test login/signup flows. |
| allowed-tools | Bash(browser-devtools-cli:*) |
Automated browser testing, interaction automation, and form testing using Browser DevTools CLI.
This skill activates when:
browser-devtools-cli navigation go-to --url "https://example.com"
browser-devtools-cli navigation go-back-or-forward --direction back
browser-devtools-cli navigation go-back-or-forward --direction forward
browser-devtools-cli navigation reload
All accept CSS selector or ref (e1, @e1) from ARIA snapshot.
browser-devtools-cli interaction click --selector "#button"
browser-devtools-cli interaction click --selector "e1" # ref from a11y take-aria-snapshot
browser-devtools-cli interaction fill --selector "#input" --value "text"
browser-devtools-cli interaction select --selector "#dropdown" --value "option"
browser-devtools-cli interaction hover --selector "#element"
browser-devtools-cli interaction press-key --key "Enter"
browser-devtools-cli interaction scroll --mode bottom
browser-devtools-cli interaction drag --source-selector "#drag" --target-selector "#drop"
browser-devtools-cli content take-screenshot --name "screenshot"
browser-devtools-cli content get-as-html
browser-devtools-cli content get-as-text
browser-devtools-cli content save-as-pdf --name "page"
browser-devtools-cli sync wait-for-network-idle
browser-devtools-cli stub mock-http-response --pattern "**/api/**" --response '{"status":200}'
browser-devtools-cli stub intercept-http-request --pattern "**/api/**" --modifications '{"headers":{}}'
browser-devtools-cli stub list
browser-devtools-cli stub clear
a11y take-aria-snapshot to get refs (e1, e2) for stable element targeting--selector "e1" for refs or CSS selector)# Fill text input
browser-devtools-cli interaction fill \
--selector "#email" \
--value "test@example.com"
# Fill password
browser-devtools-cli interaction fill \
--selector "#password" \
--value "SecurePass123"
# Click submit
browser-devtools-cli interaction click \
--selector "button[type=submit]"
browser-devtools-cli interaction select \
--selector "#country" \
--value "US"
# Check checkbox
browser-devtools-cli interaction click \
--selector "#terms-checkbox"
# Select radio option
browser-devtools-cli interaction click \
--selector "input[name=plan][value=premium]"
SESSION="--session-id wizard-test"
# Step 1: Personal Info
browser-devtools-cli $SESSION interaction fill --selector "#name" --value "John Doe"
browser-devtools-cli $SESSION interaction fill --selector "#email" --value "john@example.com"
browser-devtools-cli $SESSION interaction click --selector "#next-step"
# Wait for step 2
browser-devtools-cli $SESSION sync wait-for-network-idle
# Step 2: Address
browser-devtools-cli $SESSION interaction fill --selector "#address" --value "123 Main St"
browser-devtools-cli $SESSION interaction select --selector "#state" --value "CA"
browser-devtools-cli $SESSION interaction click --selector "#next-step"
# Step 3: Confirm
browser-devtools-cli $SESSION sync wait-for-network-idle
browser-devtools-cli $SESSION interaction click --selector "#submit"
# Submit empty form
browser-devtools-cli interaction click --selector "button[type=submit]"
# Check for error messages
browser-devtools-cli content get-as-text --selector ".error-message"
# Invalid email
browser-devtools-cli interaction fill --selector "#email" --value "not-an-email"
browser-devtools-cli interaction click --selector "button[type=submit]"
# Check validation error
browser-devtools-cli content get-as-html --selector ".email-error"
SESSION="--session-id my-test"
# Navigate
browser-devtools-cli $SESSION navigation go-to --url "https://example.com"
# Interact
browser-devtools-cli $SESSION interaction click --selector ".login-btn"
browser-devtools-cli $SESSION interaction fill --selector "#email" --value "test@example.com"
# Verify
browser-devtools-cli $SESSION content take-screenshot --name "after-login"
# Cleanup
browser-devtools-cli session delete my-test
interaction fill which clears first)run execute --code "..." with callTool() reduces round-trips (see browser-devtools-cli execute reference).Test API integrations by mocking responses, intercepting requests, and monitoring network traffic. Use when the user wants to mock backend APIs, simulate errors, test offline behavior, intercept requests, or add authentication headers.
Automates browser interactions using Playwright for web testing, debugging, and automation. Use when the user needs to navigate websites, take screenshots, fill forms, click elements, extract page content (HTML/text), audit accessibility (ARIA/AX tree), measure Web Vitals performance, monitor console logs and HTTP requests, mock API responses, execute JavaScript in browser, inspect React components, compare UI with Figma designs, or perform non-blocking debugging with tracepoints, logpoints, and exception monitoring.
Debug web and Node.js applications using console inspection, network analysis, and non-blocking code debugging. Use when the user reports bugs, wants to debug JavaScript (browser or backend), inspect network requests, troubleshoot page/API issues, trace function calls, or monitor exceptions.
CLI for debugging Node.js backend processes with non-blocking inspection. Use when the user needs to connect to Node.js processes (by PID, name, Docker, or port), set tracepoints/logpoints/exceptionpoints, capture call stacks and local variables, or inspect console logs. Requires daemon; connect before other debug commands.
Monitor and debug web and Node.js applications using OpenTelemetry, console logs, network requests, and distributed tracing. Use when the user asks about distributed tracing, correlating frontend/backend requests, OpenTelemetry, Jaeger, or monitoring application behavior.
Analyze web and backend performance using Web Vitals, network timing, and Node.js metrics. Use when the user asks about page performance, load times, Core Web Vitals (LCP, CLS, INP), slow pages, backend bottlenecks, or SEO performance factors.