cf-cowork-setup

# /contentforge:cf-cowork-setup The one-time setup that makes ContentForge usable in Cowork by a team. Wires up the Cowork → Drive routing so generated `.docx` files, brand profiles, and run records actually persist somewhere the team can reach. ## Why this skill exists Cowork is the most user-friendly Anthropic surface for non-CLI users — marketers, content teams, agency staff. The natural team workflow is "everyone uses Cowork; outputs live in our shared Google Drive". But ContentForge's filesystem layer was originally designed for local Claude Code (writes to `~/Documents/ContentForge/` on the host). In Cowork that path is the Linux sandbox — gone at session end, invisible to the team. v3.12.9 fixed this with environment-aware routing: when Cowork is detected AND a Drive MCP is configured, the output-manager agent uploads to Drive instead. This skill is the one-shot setup that ensures both conditions are true before you start producing real content. ## Behavior ### Step 1 — Verify Cowork environment ```bash python scripts/plugin-metadata.py --section environment ``` Parse the JSON. Three branches: **`environment == "cowork-sandbox"`** — Proceed to Step 2. **`environment == "claude-code-windows"` / `"-mac"` / `"-linux"`** — Tell the user: > "You're running in local Claude Code, not Cowork. The Cowork-specific Drive routing isn't needed here — your files will land in `~/Documents/ContentForge/<brand>/` on your host as designed. If you ALSO want Drive backups for t...