This is the glue between OpenWork and OpenCode, giving you three ways to talk to OpenCode: spawn it from CLI with JSON responses, read directly from its SQLite database to grab sessions and messages, or use the MCP bridge for real-time streaming. You'd reach for this when you're building OpenWork features that need to interact with OpenCode's AI operations, whether that's triggering prompts programmatically, inspecting conversation history, or setting up bidirectional communication channels. It's infrastructure more than a feature, the kind of bridge skill that other parts of the system depend on to coordinate between tools.
npx skills add https://github.com/different-ai/openwork --skill opencode-bridge