cf-environmentlisted

# /contentforge:cf-environment Detect where ContentForge is running and report which of its capabilities work in that environment. ContentForge has different real-world behavior on each surface because filesystem access, MCP transports, and subprocess invocation all differ. ## When to use this skill - User asks "will my files actually save to my Documents folder?" - User asks "does this work in Cowork?" - User reports that `~/Documents/ContentForge/` is empty after a run - Before kicking off a long (20-60 min) content pipeline, to set expectations - During brand-setup, to decide between MCP-Drive and service-account routes ## Behavior ### Step 1 — Run the environment probe ```bash python scripts/plugin-metadata.py --section environment ``` This returns JSON with `environment` (one of `cowork-sandbox`, `claude-code-windows`, `claude-code-mac`, `claude-code-linux`, `unknown`), filesystem indicators, and a `cowork_warning` field that's non-null when the Cowork sandbox is detected. ### Step 2 — Present the capability matrix for the detected environment Render one of the three matrices below based on the JSON `environment`. #### `cowork-sandbox` Cowork is **the recommended environment for teams** as of v3.12.9 — it has the friendliest UX, lowest setup friction, and works for non-CLI users. But it requires one extra setup step (connecting Google Drive) because the sandbox filesystem doesn't persist. After Drive is wired, everything works. **Also check: is a Drive MCP av