$npx -y skills add indranilbanerjee/contentforge --skill cf-environmentDetect the runtime environment (Cowork sandbox vs local Claude Code) and report which ContentForge capabilities work in it. Use this when the user asks 'will this work in Cowork', sees unexpected file-path behavior, or wants a capability matrix before running a long pipeline.
| 1 | # /contentforge:cf-environment |
| 2 | |
| 3 | 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. |
| 4 | |
| 5 | ## When to use this skill |
| 6 | |
| 7 | - User asks "will my files actually save to my Documents folder?" |
| 8 | - User asks "does this work in Cowork?" |
| 9 | - User reports that `~/Documents/ContentForge/` is empty after a run |
| 10 | - Before kicking off a long (20-60 min) content pipeline, to set expectations |
| 11 | - During brand-setup, to decide between MCP-Drive and service-account routes |
| 12 | |
| 13 | ## Behavior |
| 14 | |
| 15 | ### Step 1 — Run the environment probe |
| 16 | |
| 17 | ```bash |
| 18 | python scripts/plugin-metadata.py --section environment |
| 19 | ``` |
| 20 | |
| 21 | This returns JSON with `environment` (one of `cowork-sandbox`, |
| 22 | `claude-code-windows`, `claude-code-mac`, `claude-code-linux`, `unknown`), |
| 23 | filesystem indicators, and a `cowork_warning` field that's non-null when |
| 24 | the Cowork sandbox is detected. |
| 25 | |
| 26 | ### Step 2 — Present the capability matrix for the detected environment |
| 27 | |
| 28 | Render one of the three matrices below based on the JSON `environment`. |
| 29 | |
| 30 | #### `cowork-sandbox` |
| 31 | |
| 32 | 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. |
| 33 | |
| 34 | **Also check: is a Drive MCP available in this session?** Scan your available tools for `mcp__*drive*` or the Anthropic-platform Drive integration. The capability matrix below splits on that. |
| 35 | |
| 36 | ``` |
| 37 | === ContentForge in Cowork === |
| 38 | |
| 39 | | Capability | Cowork + Drive | Cowork alone | |
| 40 | |---------------------------------------------|-------------------|----------------| |
| 41 | | /plugin commands | YES | YES | |
| 42 | | HTTP MCP connectors (Slack, HubSpot, ...) | YES | YES | |
| 43 | | npx / stdio MCP connectors | NO | NO | |
| 44 | | | | | |
| 45 | | Final .docx delivery | -> Drive folder | -> sandbox (gone after session) | |
| 46 | | Brand profile persistence | -> Drive | sandbox only | |
| 47 | | Per-phase checkpoint files | -> Drive | sandbox only | |
| 48 | | /contentforge:resume across sessions | YES (via Drive) | NO | |
| 49 | | Team sharing of outputs | YES (Drive) | NO | |
| 50 | | Files visible to user without download | YES (Drive) | NO | |
| 51 | | Full 10-phase pipeline | YES | LOGICAL ONLY -- outputs sandbox-only | |
| 52 | ``` |
| 53 | |
| 54 | **If Cowork + Drive:** This is the recommended team setup. Run `/contentforge:cf-cowork-setup` once to wire the Drive folder layout, then use ContentForge normally. Every `.docx`, brand profile, and run record lands in `My Drive/ContentForge/...` where your team can access it from anywhere. |
| 55 | |
| 56 | **If Cowork without Drive:** Connect Drive first. Easiest path: Cowork → **Settings** → **Integrations** → **Google Drive** → Connect (60 seconds). Then run `/contentforge:cf-cowork-setup`. Until that's done, generated files will only exist for the current session and won't be retrievable after you close the chat. |
| 57 | |
| 58 | Local Claude Code (CLI or IDE extension) is the alternative if you don't want to use Drive — files land directly in `~/Documents/ContentForge/<brand>/...` on your machine. But for team usage, Cowork+Drive is simpler. |
| 59 | |
| 60 | #### `claude-code-windows`, `claude-code-mac`, `claude-code-linux` |
| 61 | |
| 62 | ``` |
| 63 | === ContentForge in local Claude Code (<platform>) === |
| 64 | |
| 65 | | Capability | Works locally? | |
| 66 | |---------------------------------------------|------------------------------| |
| 67 | | /plugin commands | YES | |
| 68 | | All HTTP MCP connectors | YES | |
| 69 | | npx / stdio MCP connectors | YES (requires Node.js) | |
| 70 | | Google Drive via Anthropic platform | LIMITED -- depends on | |
| 71 | | | whether the host Claude | |
| 72 | | | Code session has the | |
| 73 | | | Drive integration | |
| 74 | | Google Drive via Pipedream / Composio | YES (HTTP) | |
| 75 | | Google Drive via service-account JSON | YES |