What problem does it solve? ContentForge behaves differently depending on where it runs — Cowork sandboxes cannot write to your host filesystem, so users run a long pipeline and then find their Documents folder empty. This Skill detects the actual runtime environment and tells you exactly which capabilities work before you invest 20-60 minutes in a content pipeline. ## Core Features & Use Cases - Environment Detection: Runs a probe script that classifies the runtime into one of six values (cowork-sandbox, claude-code-windows/mac/linux, linux-sandbox-uncertain, unknown) using strong and weak detection signals. - Capability Matrix: Renders a per-environment table covering MCP connector transports, file persistence, Drive integration, and whether /contentforge:resume survives across sessions. - Drive MCP Scan: Checks the session for Google Drive MCP availability to distinguish Cowork+Drive (recommended team setup) from Cowork alone, where outputs vanish after the session. - Use Case: Before launching a 10-phase content pipeline in Cowork, run the check to learn that files will only persist if Google Drive is connected — then wire it up via /contentforge:cf-cowork-setup instead of losing the output. ## Quick Start Ask the assistant to run /contentforge:cf-environment to detect the current environment and show which ContentForge capabilities work here.
