cf-environment

# /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`, `linux-sandbox-uncertain`, `unknown` — six possible values), filesystem indicators, a `cowork_warning` field that's non-null when a sandbox (confirmed or suspected) is detected, and a `signals` object (`strong` / `weak` lists) showing exactly which detection heuristics fired — useful for `--verbose` or when a user disputes the classification. ### Step 2 — Present the capability matrix for the detected environment Render one of the matrices below based on the JSON `environment`. The six values map to three matrices: `cowork-sandbox` AND `linux-sandbox-uncertain` both use the Cowork matrix (uncertain gets a on...