skills.rest
different-ai
different-aiOFFICIAL
Explore all skills by this author →
𝕏@benjaminshafiiGitHub

openwork-chrome-mcp-testing

Validate OpenWork UI flows with Chrome MCP snapshots and logs.

63|8|Updated Jan 24, 2026
Search Tags:#automation#verification#ui-testing#headless#openwork#chrome-mcp#remote-behavior
One-click install
npx skills add https://github.com/different-ai/openwork-enterprise --skill openwork-chrome-mcp-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openwork-chrome-mcp-testing
Source: https://github.com/different-ai/openwork-enterprise/tree/main/.opencode/skills/openwork-chrome-mcp-testing
Command: npx skills add https://github.com/different-ai/openwork-enterprise --skill openwork-chrome-mcp-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chrome MCP-based verification ensures UI flows and remote behaviors are validated before changes are merged, reducing risk of remote-behavior bugs.

Core Features & Use Cases

  • Triggers when user mentions:
    • "test with chrome mcp"
    • "ui verification"
    • "remote behavior test"
  • Validate remote behavior in the UI by capturing MCP snapshots and logs.
  • Provide evidence and gate results for code reviews.

Quick Start

Start headless + web UI with openwork-testability, connect the UI to headless, verify Remote and OpenCode Engine status, perform the feature test in the UI, and capture a Chrome MCP snapshot and logs as evidence.

Frequently Asked Questions about openwork-chrome-mcp-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify remote behavior and UI changes with Chrome MCP?▼

You verify remote behavior by running UI verification tests that capture Chrome MCP snapshots and logs. This end-to-end process validates UI flows before code merges, providing evidence and gate results for reviews.

How do I capture UI testing snapshots and logs in headless mode?▼

To capture UI testing snapshots and logs in headless mode, start the openwork-testability web UI, connect it to headless, and perform feature tests. The system records Chrome MCP snapshots and logs as verification evidence.

Do I need the OpenCode testability ecosystem to run Chrome MCP tests?▼

Yes, you need the OpenCode or OpenWork testability ecosystem to run Chrome MCP tests. This environment provides the required headless mode and UI setup necessary to execute tests and produce snapshots and logs.

What is Chrome MCP UI verification used for?▼

Chrome MCP UI verification is used to validate UI flows and remote behaviors before changes are merged. It captures snapshots and logs to provide concrete evidence and gate results for code reviews.

What are the prerequisites for starting a remote behavior test?▼

Prerequisites for a remote behavior test include Chrome MCP, headless mode, and the OpenWork testability ecosystem. You must start headless, connect the UI, and verify the OpenCode Engine status before testing.

When should I use headless UI verification instead of manual testing?▼

You should use headless UI verification when features touch remote behavior and UI changes. It automates evidence capture and provides gate results for code reviews, which manual testing cannot easily replicate.

Related Skills

Explore More Software Engineering Skills→
different-aidifferent-ai
63

openwork-testability

Coordinate headless UI testing for OpenWork messaging and session flows.

Official
Intermediate
JordiNodeJSJordiNodeJS

webapp-testing

Automate UI/UX testing of web apps using Chrome DevTools MCP.

Community
Advanced
different-aidifferent-ai
63

mcp-arch

Document MCP wiring between OpenWork, OpenCode, and the OpenWork server.

Official
Intermediate
mattphanmmattphanm

browser-test

Automates browser UI tests for web applications using Chrome MCP tools and Codex.

Community
Advanced