MCPInstall

openwork-docker-chrome-mcp

by different-aiAI & Agents

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"

Installs
90
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/different-ai/openwork --skill openwork-docker-chrome-mcp
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads openwork-docker-chrome-mcp automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Quick Usage (Already Configured)

1) Start the dev stack (Docker)

Run from the OpenWork repo root:

packaging/docker/dev-up.sh

This prints:

  • Web UI URL (http://localhost:<WEB_PORT>)
  • OpenWork server URL (http://localhost:<OPENWORK_PORT>)
  • Token file path (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.

Verification checklist (copy into PR)

  • Started stack with packaging/docker/dev-up.sh from repo root.
  • Used the printed Web UI URL (not a guessed port).
  • Completed one full user flow in the UI (input -> action -> visible result).
  • Captured at least one screenshot for the success state.
  • Captured failure evidence when relevant (console and/or Docker logs).
  • Stopped stack with the exact printed docker compose -p ... down command.

Suggested screenshot set for user-facing changes:

  • Before action state.
  • During action/progress state.
  • Success state.
  • Failure or recovery state (if applicable).

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>):

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.

FAQ

What does the openwork-docker-chrome-mcp skill do?

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"

How do I install openwork-docker-chrome-mcp?

Run npx skills add https://github.com/different-ai/openwork --skill openwork-docker-chrome-mcp in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/openwork-docker-chrome-mcp/ (personal) or .claude/skills/openwork-docker-chrome-mcp/ (project).

Which AI agents can use openwork-docker-chrome-mcp?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is openwork-docker-chrome-mcp safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains openwork-docker-chrome-mcp?

It is published by different-ai in different-ai/openwork. It has 90 recorded installs.

More from different-ai/openwork

View all →

opencode-primitives

different-ai/openwork

Reference OpenCode docs when implementing skills, plugins, MCPs, or config-driven behavior.

Docs & Writing729 installs

opencode-bridge

different-ai/openwork

Bridge between OpenWork UI and OpenCode runtime

Frontend & Design628 installs

solidjs-patterns

different-ai/openwork

SolidJS reactivity + UI state patterns for OpenWork

Frontend & Design570 installs

opencode-mirror

different-ai/openwork

Maintain the local OpenCode mirror for self-reference

564 installs

openwork-core

different-ai/openwork

Core context and guardrails for OpenWork native app

546 installs

tauri-solidjs

different-ai/openwork

Tauri 2.x + SolidJS stack for OpenWork native app

515 installs

Popular ai & agents skills

View category →

google-agents-cli-publish

google/agents-cli

This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).

AI & Agents513.9K installs

google-agents-cli-eval

google/agents-cli

This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).

AI & Agents513.5K installs

skill-creator

anthropics/skills

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

OfficialAI & Agents416.4K installs

codex-pet

prime-skills/runcomfy-agent-skills

Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.

AI & Agents402.1K installs

full-output-enforcement

leonxlnx/taste-skill

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

AI & Agents401K installs

executing-plans

obra/superpowers

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

AI & Agents245.7K installs