Openwork Chrome Mcp Testing
- 2 installs
- 29 repo stars
- Updated March 27, 2026
- different-ai/openwork-hub
Verifies OpenWork UI flows end-to-end with Chrome MCP, capturing snapshots and console logs, and gates remote-behavior features on that check.
About
Requires Chrome MCP verification of OpenWork UI flows, especially any feature touching remote behavior, with snapshot and console-log evidence. A developer uses it as a non-negotiable gate before merging remote-behavior changes.
- Non-negotiable Chrome MCP gate for remote-behavior features
- Evidence capture via snapshot and console logs
Openwork Chrome Mcp Testing by the numbers
- 2 all-time installs (skills.sh)
- Ranked #1,693 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/different-ai/openwork-hub --skill openwork-chrome-mcp-testingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 29 |
| Last updated | March 27, 2026 |
| Repository | different-ai/openwork-hub ↗ |
What it does
Verifies OpenWork UI flows end-to-end with Chrome MCP, capturing snapshots and console logs, and gates remote-behavior features on that check.
Files
Quick Usage (Already Configured)
1) Start headless + web UI
Start the OpenWork dev stack via Docker and open the UI:
- Use
skills/openwork-docker-chrome-mcp/SKILL.mdstep 1. - Confirm the Web UI loads and a session/chat view is accessible.
2) Test the feature in the UI
- Navigate to the relevant screen.
- Perform the feature flow end-to-end.
- If the change touches remote behavior, verify the remote effect is visible in the UI.
3) Capture evidence
- Take a Chrome MCP snapshot.
- Pull console logs with Chrome MCP.
- Attach logs if something fails:
- capture Chrome console output via Chrome MCP
- optionally capture Docker logs for the dev stack
Required Gate (Non-Negotiable)
- Any feature that changes remote behavior MUST be validated through Chrome MCP.
- The feature is NOT done until the UI action succeeds in the browser via Chrome MCP.
- If Chrome MCP validation is skipped, the change is considered incomplete and must not be merged.
Common Gotchas
- If OpenCode Engine stays disconnected, ensure the OpenWork URL is clean and the client token is correct.
- If you see CORS errors, check OpenWork server CORS headers for custom OpenCode headers.
# No credentials required for this skill.
.env
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3kTesting & QAtesting