cowork-setup

Configures Google Drive persistence routing for Digital Marketing Pro in Anthropic Cowork.

787|132|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill cowork-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cowork-setup
Source: https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/cowork-setup
Command: npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill cowork-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In Anthropic Cowork, Digital Marketing Pro's default filesystem writes land in a per-session Linux sandbox that vanishes when the session ends, so brand profiles, campaign plans, and run checkpoints are lost and invisible to teammates. This skill performs a one-time setup that routes all brand state through a shared Google Drive folder so work persists across sessions and is accessible to the whole team.

Core Features & Use Cases

  • Environment Detection: Runs plugin-metadata.py to detect whether you are in a Cowork sandbox or local Claude Code, and adjusts behavior accordingly (local installs only get optional Drive mirroring).
  • Drive MCP Verification: Scans for a connected Google Drive MCP (Anthropic platform integration, Pipedream, Composio, or Zapier) and stops with setup instructions if none is found.
  • Canonical Folder Skeleton: Creates the DigitalMarketingPro Drive root with _brands/, _runs/, and _plans/ subfolders, then writes the routing config via drive-sync-state.py for team namespace isolation.
  • Use Case: An agency team adopts Cowork for marketing work; the admin runs this skill once so every teammate's brand-setup, seo-audit, and campaign-plan outputs land in the shared Drive folder instead of disappearing at session end.

Quick Start

Ask the assistant to run /digital-marketing-pro:cowork-setup to connect your team's shared Google Drive and make brand profiles persist across Cowork sessions.

Frequently Asked Questions about cowork-setup

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

FAQPage Schema
How do I make Digital Marketing Pro brand profiles persist in Cowork?

Run /digital-marketing-pro:cowork-setup once per team. It verifies a Google Drive MCP is connected, creates the DigitalMarketingPro folder skeleton in Drive, and writes a routing config so brand profiles, plans, and checkpoints sync to Drive instead of the ephemeral sandbox.

Why do my Cowork session files disappear after the session ends?

Cowork runs in a per-session Linux sandbox, so paths like ~/.claude-marketing/ and ${CLAUDE_PLUGIN_DATA} are wiped at session end. This skill routes state through Google Drive so it survives across sessions.

Does cowork-setup work in local Claude Code?

In local Claude Code the skill detects the host environment and explains that Drive routing is unnecessary since ~/.claude-marketing/ persists on the host. It only proceeds with optional Drive mirroring if you explicitly confirm.

What happens if no Google Drive MCP is connected?

The setup stops with instructions to connect Google Drive via Cowork Settings → Integrations, then re-run the skill. A Notion MCP is mentioned as an alternative persistence target.

Can two teams share one Google Drive without conflicts?

Yes. Each team picks its own Drive root folder name (for example, 'ACME DigitalMarketingPro'), and the routing config points to that folder, providing automatic namespace isolation between teams.

Does cowork-setup migrate existing local brands to Drive?

No. It does not migrate existing local-mode brands. After setup, re-run /digital-marketing-pro:brand-setup for each brand in Cowork and the brand-setup skill will upload the local profile to Drive.