Chrome Validation

Goal: exercise a feature in a real Chrome session the way a user would, then report PASS, FAIL or BLOCKED with browser evidence.

Step 0 — MCP check

Confirm the Chrome DevTools MCP tools are available. Treat a configured-but-failing or unauthenticated server as unavailable.

If they're missing, abort — don't substitute other tools or write a report. Tell the user to install and complete the setup from https://github.com/ChromeDevTools/chrome-devtools-mcp/ (add the server to their MCP client config — npx -y chrome-devtools-mcp@latest — then restart the session) and re-run this skill once the tools appear.

Step 1 — Inputs

Ask for anything missing, in one batch:

• Feature: feature or user workflow to validate
• URL: starting URL, route, or local app URL
• Acceptance criteria: observable behaviors that must pass
• Viewport or device: optional; default to desktop and note what you used