share-docker-chrome-verify

Start the OpenWork Docker stack and verify share links via Chrome MCP.

63|8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/different-ai/the-factory --skill share-docker-chrome-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: share-docker-chrome-verify
Source: https://github.com/different-ai/the-factory/tree/main/.opencode/skills/share-docker-chrome-verify
Command: npx skills add https://github.com/different-ai/the-factory --skill share-docker-chrome-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of verifying the local share flow by setting up the OpenWork Docker environment and guiding the user through essential browser-based checks.

Core Features & Use Cases

  • Docker Stack Setup: Automates the startup of the OpenWork Docker environment.
  • Local Share Verification: Provides clear steps to test the share service and generated links via Chrome MCP.
  • Use Case: After deploying a new feature related to content sharing, developers can quickly spin up the necessary environment and confirm the end-to-end sharing functionality works as expected before further testing.

Quick Start

Run the share docker flow verification by executing the provided setup script.

Frequently Asked Questions about share-docker-chrome-verify

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

FAQPage Schema
How do I verify a local share flow in a Docker environment?

To verify a local share flow in a Docker environment, this Skill initiates the OpenWork Docker stack and performs browser interactions via Chrome MCP to confirm share link generation and content rendering.

What is the best way to test share link generation locally before deployment?

The best way to test share link generation locally is by running the provided setup script to start the OpenWork Docker stack, then following guided Chrome browser interactions to validate the end-to-end sharing functionality.

How does Chrome MCP work with Docker to validate content sharing?

Chrome MCP works with Docker by executing specific user actions in the browser after the OpenWork Docker environment starts, allowing developers to verify that generated share links render content correctly.

Do I need Docker running to test OpenWork share functionality?

Yes, Docker is required because the Skill automates the startup of the OpenWork Docker stack to set up the environment needed for validating the local share flow and generating share links.

What are the limitations of using Docker and Chrome to verify local share flows?

The verification is limited to local Docker environments and browser-based checks via Chrome MCP, meaning it validates share link generation and content rendering but does not cover external deployment or production testing scenarios.