How do I install the Openwork Docker Chrome MCP skill?

Run npx skillmds@latest add different-ai/openwork-docker-chrome-mcp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openwork Docker Chrome MCP safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openwork Docker Chrome MCP?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openwork Docker Chrome MCP free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openwork Docker Chrome MCP?

different-ai (@different-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openwork Docker Chrome MCP by different-ai

Name: Openwork Docker Chrome MCP
Author: different-ai

File contents

Quick Usage (Already Configured)

1) Start the dev stack (Docker)

Run from the OpenWork repo root:

cd _repos/openwork
packaging/docker/dev-up.sh

This prints:

Web UI URL (http://localhost:)
OpenWork server URL (http://localhost:)
Token file path (_repos/openwork/tmp/.dev-env-<id>) containing OPENWORK_TOKEN + OPENWORK_HOST_TOKEN
A docker compose ... down command that stops this stack

2) Verify a real UI flow (Chrome MCP)

Minimum gate:

Open the printed Web UI URL.
Navigate to the session/chat surface (typically /session).
Send a message (example: smoke: hello from chrome mcp).
Confirm a response renders in the UI.

Chrome MCP tool recipe (typical):

chrome-devtools_list_pages (optional: see existing tabs)
chrome-devtools_new_page with the Web UI URL (or chrome-devtools_navigate_page if a page is already open)
chrome-devtools_take_snapshot to locate the chat input + Send button uids
chrome-devtools_fill the chat input uid with your message
chrome-devtools_click the Send button uid
chrome-devtools_wait_for a distinctive piece of response text (or re-snapshot until the response appears)
chrome-devtools_take_screenshot (save to /tmp/...png when possible)
If debugging: chrome-devtools_list_console_messages

Evidence:

Take a Chrome MCP screenshot after the response appears.
If something fails, capture console logs and (optionally) Docker logs.

3) Stop the stack

Use the exact docker compose -p ... down command printed by dev-up.sh.

If you lost it, you can find the project name via:

docker ps --format '{{.Names}}' | rg '^openwork-dev-'

Then stop it (replace <project>):

cd _repos/openwork
docker compose -p <project> -f packaging/docker/docker-compose.dev.yml down

Required Gate (Non-Negotiable)

Any user-facing change or change that touches remote behavior must be validated end-to-end in the running UI.
The change is not "done" until it succeeds via Chrome MCP against the Docker dev stack started by packaging/docker/dev-up.sh.

Common Gotchas

Docker is required (and the docker CLI must be available on PATH).
dev-up.sh uses random host ports; do not assume 5173/8787.
If the UI looks up but is disconnected, confirm you opened the printed URL and that headless is healthy.

---name: openwork-docker-chrome-mcpdescription: Start the OpenWork dev stack via Docker and verify real user flows via Chrome MCP. Triggers when user mentions: - "dev-up.sh" - "docker dev stack" - "verify in chrome mcp" - "test the real flow"---## Quick Usage (Already Configured)### 1) Start the dev stack (Docker)Run from the OpenWork repo root:```bashcd _repos/openworkpackaging/docker/dev-up.sh```This prints:- Web UI URL (http://localhost:<WEB_PORT>)- OpenWork server URL (http://localhost:<OPENWORK_PORT>)- Token file path (`_repos/openwork/tmp/.dev-env-<id>`) containing `OPENWORK_TOKEN` + `OPENWORK_HOST_TOKEN`- A `docker compose ... down` command that stops this stack### 2) Verify a real UI flow (Chrome MCP)Minimum gate:1. Open the printed Web UI URL.2. Navigate to the session/chat surface (typically `/session`).3. Send a message (example: `smoke: hello from chrome mcp`).4. Confirm a response renders in the UI.Chrome MCP tool recipe (typical):- `chrome-devtools_list_pages` (optional: see existing tabs)- `chrome-devtools_new_page` with the Web UI URL (or `chrome-devtools_navigate_page` if a page is already open)- `chrome-devtools_take_snapshot` to locate the chat input + Send button uids- `chrome-devtools_fill` the chat input uid with your message- `chrome-devtools_click` the Send button uid- `chrome-devtools_wait_for` a distinctive piece of response text (or re-snapshot until the response appears)- `chrome-devtools_take_screenshot` (save to `/tmp/...png` when possible)- If debugging: `chrome-devtools_list_console_messages`Evidence:- Take a Chrome MCP screenshot after the response appears.- If something fails, capture console logs and (optionally) Docker logs.### 3) Stop the stackUse the exact `docker compose -p ... down` command printed by `dev-up.sh`.If you lost it, you can find the project name via:```bashdocker ps --format '{{.Names}}' | rg '^openwork-dev-'```Then stop it (replace `<project>`):```bashcd _repos/openworkdocker compose -p <project> -f packaging/docker/docker-compose.dev.yml down```## Required Gate (Non-Negotiable)- Any user-facing change or change that touches remote behavior must be validated end-to-end in the running UI.- The change is not "done" until it succeeds via Chrome MCP against the Docker dev stack started by `packaging/docker/dev-up.sh`.## Common Gotchas- Docker is required (and the `docker` CLI must be available on PATH).- `dev-up.sh` uses random host ports; do not assume `5173`/`8787`.- If the UI looks up but is disconnected, confirm you opened the *printed* URL and that headless is healthy.

Frequently asked questions

Openwork Docker Chrome MCP