skills.rest
teachskillofskills-ai
teachskillofskills-aiCOMMUNITY
Explore all skills by this author →
GitHub

cf-cowork-setup

Configures ContentForge in Anthropic Cowork to route outputs into shared Google Drive folders.

1|Updated Aug 18, 2026
Search Tags:#configuration#mcp#setup#google drive#cowork#content routing#team workspace
One-click install
npx skills add https://github.com/teachskillofskills-ai/ContentForge-techshu --skill cf-cowork-setup-teachskillofskills-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cf-cowork-setup
Source: https://github.com/teachskillofskills-ai/ContentForge-techshu/tree/main/skills/cf-cowork-setup
Command: npx skills add https://github.com/teachskillofskills-ai/ContentForge-techshu --skill cf-cowork-setup-teachskillofskills-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? ContentForge was built for local Claude Code, where outputs land on the host filesystem. In Anthropic Cowork, files written to the Linux sandbox vanish at session end and are invisible to the team. This Skill performs the one-time setup that verifies the Cowork environment, confirms a Google Drive MCP is connected, creates the canonical Drive folder structure, and persists routing config so .docx outputs, brand profiles, and run checkpoints land in shared Drive. ## Core Features & Use Cases - Environment Detection: Runs scripts/plugin-metadata.py to distinguish Cowork sandbox, uncertain sandbox, local Claude Code, and unknown environments, with tailored guidance per branch. - Drive MCP Verification: Scans available tools for Google Drive integrations (Anthropic platform, Pipedream, Composio, Zapier) and stops with setup instructions if none is found. - Canonical Folder Provisioning: Creates the ContentForge Drive root with _brands/ and _runs/ subfolders, supporting per-team namespace isolation via custom folder names. - Persistent Config: Writes environment, Drive folder ID/URL, and MCP tool prefix to ~/.claude-marketing/_cowork-config.json via scripts/drive-sync-state.py. - Use Case: A marketing team adopts Cowork and runs /contentforge:cf-cowork-setup --brand "Acme" once; every subsequent content run for any teammate saves .docx files and brand profiles to the shared Drive automatically. ## Quick Start Run /contentforge:cf-cowork-setup to verify your Cowork environment, connect Google Drive, and wire all ContentForge outputs to your team's shared Drive folder.

Frequently Asked Questions about cf-cowork-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up ContentForge in Anthropic Cowork for a team?▼

Run /contentforge:cf-cowork-setup once. It verifies the Cowork sandbox environment, checks for a connected Google Drive MCP, creates the ContentForge folder with _brands/ and _runs/ subfolders, and saves the routing config so all outputs persist in shared Drive.

Why aren't my ContentForge files showing up in Google Drive?▼

ContentForge defaults to local filesystem paths, which in Cowork point to an ephemeral sandbox deleted at session end. Run /contentforge:cf-cowork-setup to detect the environment, connect a Drive integration, and route outputs to shared Drive.

Which Google Drive integrations work with Cowork setup?▼

The setup detects the Anthropic platform Google Drive integration (Settings → Integrations), plus Pipedream, Composio, and Zapier Drive connectors. If none is found, it stops and walks you through connecting one before continuing.

Does cf-cowork-setup change anything in local Claude Code?▼

No. When the environment check detects local Claude Code on Windows, Mac, or Linux, the skill explains that Drive routing is unnecessary and exits without changes. Local outputs continue landing in ~/Documents/ContentForge/ on the host.

Can multiple teams share one Google Drive with ContentForge?▼

Yes. Each team picks a distinct Drive root folder name during setup, such as "ACME ContentForge". Each team's config points to its own folder, providing namespace isolation so runs and brand profiles never collide.

Does the Cowork setup migrate existing local brands to Drive?▼

No, it does not migrate existing local-mode brands. After setup completes, re-run /contentforge:brand-setup for each brand inside Cowork to recreate its profile in the Drive-backed layout.

Related Skills

Explore More Content & Communication Skills→
vZulinvZulin

google-drive-automation

Automate Google Drive file upload, download, search, and share via Rube MCP.

Community
Intermediate
danielscholldanielscholl
23

brand-voice-generator

Generate brand.json, config.json, brand-system.md, and tone-of-voice.md files.

Community
Advanced
cellarwoodcellarwood

recipe-log-deal-update

Append deal status updates to a Google Sheets Sales Pipeline spreadsheet.

Official
Basic
MSApps-MobileMSApps-Mobile
8

google-drive-upload

Upload files to Google Drive via a configured Apps Script endpoint.

Official
Intermediate