Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →indranilbanerjee/cowork-setup
One-shot setup that wires Digital Marketing Pro for team usage in Anthropic Cowork. Verifies the Cowork sandbox, checks for a Google Drive integration, creates the canonical Drive folder layout, and confirms team-ready brand-state routing. Use this the first time a Cowork user installs DMP OR when brand profiles aren't persisting across sessions.
Passed 15 of 19 test cases with the skill, and 4 of 19 without it.
and 11 more in the full report
12 fixed5 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
To what exact local path on the VM sandbox does the Drive configuration helper write state settings?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the path ~/.claude-marketing/_cowork-config.json | Missed | Passed |
The instructions your model reads when the skill loads.
Script location. If your host does not set
${CLAUDE_PLUGIN_ROOT}, the scripts are in this plugin'sscripts/folder, next toskills/. Run them with Python 3.10 or newer:python, orpython3wherepythonis not found (macOS, many Linux systems).
The one-time setup that makes Digital Marketing Pro persistent in Cowork by a team. Wires up the Cowork → Drive routing so brand profiles, campaign plans, audit reports, and run records survive past the end of the current Cowork session.
Run it the first time a team installs DMP in Cowork, when brand profiles stop persisting across Cowork sessions, or when switching to a different team's Drive root folder. Examples: /digital-marketing-pro:cowork-setup, ... --brand acme, ... --drive-root "ACME DigitalMarketingPro".
Cowork is the friendliest Anthropic surface for marketers — agency teams, in-house marketers, growth ops — who don't live in a terminal. The natural team workflow is "everyone uses Cowork; brand state and outputs live in our shared Drive". But DMP's filesystem layer was designed for local Claude Code (writes to ~/.claude-marketing/ on the host machine). In Cowork that path is the per-session Linux sandbox — vanishes at session end, invisible to the team.
${CLAUDE_PLUGIN_DATA} does not help here either. Anthropic's plugin docs describe it as the persistent per-plugin storage path. In Cowork it resolves to a session-scoped VM mount that disappears the same way (open: claude-code#51398). Every OAuth-backed MCP plugin hits the same wall.
v3.12.0 fixed this with environment-aware routing: when Cowork is detected AND a Drive MCP is configured, brand profiles and reports round-trip through Drive instead of the ephemeral sandbox. This skill is the one-shot setup that ensures both conditions are true before you start producing real work.
python "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-metadata.py" --section environment
Parse the JSON. Three branches:
environment == "cowork-sandbox" — Proceed to Step 2.
environment == "claude-code-windows" / "-mac" / "-linux" — Tell the user:
"You're running in local Claude Code, not Cowork. The Cowork-specific Drive routing isn't needed here — brand state at
~/.claude-marketing/persists on your host as designed. If you ALSO want Drive backups for team sharing, you can run this skill anyway and it'll mirror state to Drive as a backup. Want to proceed?"
Only proceed if the user confirms.
environment == "unknown" — Show the indicators from the JSON and ask the user where they're running, then proceed assuming Cowork (since unknown-from-Cowork is the most likely case).
Scan your available tools for any Google Drive MCP. Common signatures:
test cases passed, vs 4 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.