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

openwork-docker-chrome-mcp

Start the OpenWork Docker stack and verify UI via Chrome DevTools Protocol.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of starting the OpenWork development environment using Docker and verifying user-facing changes through automated browser interactions.

Core Features & Use Cases

  • Dev Stack Management: Easily spin up the complete OpenWork development environment with a single command.
  • UI Verification: Automate testing of real user flows within the application using Chrome's DevTools Protocol (MCP).
  • Use Case: After making a change to the chat interface, use this Skill to start the Docker stack, open the Web UI in Chrome, send a test message, and capture a screenshot of the response to confirm the fix.

Quick Start

Run the packaging/docker/dev-up.sh script from the OpenWork repo root to start the dev stack.

Frequently Asked Questions about openwork-docker-chrome-mcp

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

FAQPage Schema
How do I start a local development stack with Docker for UI testing?▼

You can start a local development stack for UI testing by running the `packaging/docker/dev-up.sh` script from the repository root, which uses Docker Compose to spin up the complete environment.

Can I automate Chrome browser interactions to test user interface flows?▼

Yes, you can automate Chrome browser interactions to test user interface flows by utilizing Chrome's DevTools Protocol to simulate real user actions, send test messages, and capture screenshots for validation.

What prerequisites do I need to validate UI changes in a Docker development environment?▼

To validate UI changes in a Docker development environment, you need Docker and the Chrome browser installed and accessible on your machine to support the stack and automated testing protocol.

What is the best way to verify a chat interface fix in a reproducible development environment?▼

The best way to verify a chat interface fix is to start your Docker stack, open the Web UI in Chrome, send a test message, and capture a screenshot of the response to confirm the change.

Does this Docker dev stack approach work for end-to-end testing of remote behavior?▼

Yes, this Docker dev stack approach works for end-to-end testing of remote behavior by providing a reproducible local environment that accurately validates user-facing functionalities via automated browser interactions.

Why use Docker Compose for local testing instead of running the application directly?▼

Using Docker Compose for local testing provides a reproducible development environment that eliminates configuration inconsistencies, ensuring reliable validation of user interface functionalities before deployment.

Related Skills

Explore More Software Engineering Skills→
Adityashandilya555Adityashandilya555

local-test

Build, run, and validate IronClaw locally with Docker and Chrome MCP.

Community
Intermediate
ssdeanxssdeanx
43

browser

Automate Chrome browser tasks via Chrome DevTools Protocol over WebSocket.

Community
Intermediate
faustellar1995faustellar1995
1

local-test

Build, deploy, and test IronClaw web gateway changes locally with Docker and Chrome MCP.

Community
Intermediate
LambdaTestLambdaTest
350

testcafe-skill

Generate TestCafe end-to-end tests in JavaScript or TypeScript.

Official
Intermediate