CF Environment

Detects Cowork sandbox vs local Claude Code and reports which ContentForge capabilities actually work there.

Works with setup

Test report

Verdict
Works with setup
Score
9.2/10
Tested
Jul 16, 2026
Environment
Claude Code 2.x (agent harness)
Upstream re-checked
Aug 10, 2026 · 1a77ad8

The probe script it calls (scripts/plugin-metadata.py) lives at the ContentForge repo root, not inside skills/cf-environment/, so a plain skill-folder copy has nothing to run -- confirmed by executing the copied skill and hitting a bare FileNotFoundError -- but run from the full repo the same script returns exactly the documented JSON schema (environment/indicators/cowork_warning) and the doc is unusually honest about its own limits ('does not enable Cowork-to-host file writes... that's an Anthropic platform feature, not something a plugin can add').

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

  • Installs cleanly 4/5
  • Triggers reliably 5/5
  • Output vs. baseline 9/10
  • Docs & honesty 5/5

What CF Environment does

Runs a Python environment probe (platform/cwd/home/writable_cwd) to classify the runtime as cowork-sandbox, claude-code-mac/windows/linux, or unknown, then renders a capability matrix (file persistence, Drive integration, MCP transport support, pipeline completeness) specific to that environment. Triggers on 'will this work in Cowork', unexpected empty-output-folder reports, or wanting a capability check before a long ContentForge run.

How to install CF Environment

git clone https://github.com/indranilbanerjee/contentforge
mkdir -p ~/.claude/skills
cp -r contentforge/skills/cf-environment ~/.claude/skills/cf-environment

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger CF Environment

  • /cf-environment Detects Cowork sandbox vs local Claude Code and reports which ContentForge capabilities actually work there.

It also activates on plain-language prompts like these:

  • Will my ContentForge output files actually save if I run this in Cowork?
  • Check whether I'm in a Cowork sandbox or local Claude Code right now
  • My output folder keeps coming back empty, is this even the right runtime?

Frequently asked questions

Is the CF Environment skill free?
Yes. The skill itself is free from indranilbanerjee/contentforge. SkillProof publishes the install command and an independent test verdict at no cost.
Does CF Environment work with Claude Code?
We tested it with Claude Code 2.x (agent harness) on Jul 16, 2026. Verdict: Works with setup. The probe script it calls (scripts/plugin-metadata.py) lives at the ContentForge repo root, not inside skills/cf-environment/, so a plain skill-folder copy has nothing to run -- confirmed by executing the copied skill and hitting a bare FileNotFoundError -- but run from the full repo the same script returns exactly the documented JSON schema (environment/indicators/cowork_warning) and the doc is unusually honest about its own limits ('does not enable Cowork-to-host file writes... that's an Anthropic platform feature, not something a plugin can add').
What is the CF Environment SkillProof Score?
9.2/10 — installs cleanly 4/5, triggers reliably 5/5, output vs. baseline 9/10, docs & honesty 5/5.
How do I install CF Environment?
Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use CF Environment with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.