Digital Marketing Pro

Your agency just signed a 50-brand client. The previous agency left no playbook. Three brands are bleeding budget, two have stale positioning, one is launching in a regulated jurisdiction next month. Where do you start?

Run /digital-marketing-pro:engagement against each brand. Same 12-Part Strategy Flow, same Four Core Documents, same 61-step structure — auditable across the entire portfolio in ~60 minutes per brand on Claude Opus 4.8. No more inconsistent depth between brands. No more "what did the last agency do?" mysteries. No more compliance gaps in regulated jurisdictions.

Open-source AI marketing plugin — 158 skills, 24 specialist agents, EU AI Act Article 50 ready, Cowork team-persistent. Built for marketing agencies, in-house teams running 50–200 brands, and consultancies. Installs on Claude Code (CLI + IDE), Anthropic Cowork, OpenAI Codex, Cursor 2.5+, GitHub Copilot CLI, Google Antigravity 2.0, Hermes Agent, and OpenClaw + 35+ Agent Skills platforms. Created by Indranil Banerjee · LinkedIn · X.

🆕 Just shipped — v3.15.1 (July 12, 2026): Self-containment patch — removed every cross-plugin capability reference from skills. Visual-production handoffs, C2PA signing, workflow resume, and publish-dir checks are all DMP-native paths now; install DMP alone and every documented capability works. Read what's new → · Full changelog →

Previously — v3.15.0 (July 7, 2026): The Reliability & Truth release — a full-repo audit fixed ~200 findings in one pass. Connectors are honestly opt-in (the shipped .mcp.json is empty; fictional npm packages purged), all 18 execution skills carry a uniform typed-approval gate (closes issue #6), the Tessl review workflow moved to the tessl review CLI (closes issue #8), agents consolidated 25 → 24, C2PA gained the Article 50 --ai-disclosure assertion, and a new doc-vs-argparse contract linter + state-layer tests grew the suite from 123 to 207 passing. Read what's new → · Full changelog →

# Install — one line
/plugin marketplace add indranilbanerjee/neels-plugins
/plugin install digital-marketing-pro@neels-plugins

If this saves you time, give it a star ⭐ — it's the single thing that helps other marketers find it.

Who this is for

How does this compare?

Get started in 5 minutes (non-developer path)

Are you a marketer, agency owner, or content lead who doesn't live in a terminal? Here's the fastest path:

1. Open Anthropic Cowork in your browser (no installation, no terminal, no command line). Sign up free if you don't have an account.
2. Click your profile menu → Settings → Plugins → Add Marketplace. Paste: indranilbanerjee/neels-plugins
3. Find "Digital Marketing Pro" in the list → click Install.
4. Type in chat: "Let's set up a brand for ACME Corp" — Claude will walk you through brand setup (voice, audience, jurisdiction, competitors).
5. Then ask: "Run a full marketing engagement for ACME" — and watch ~50–60 strategy documents get produced over the next ~60 minutes.

That's it. You never touched a command line. Your team Drive will hold the outputs. Re-open Cowork tomorrow and pick up where you left off.

If you're more technical, see Quick start below for the Claude Code CLI install (one terminal command).

For team usage (agencies running 50+ brands), also run /digital-marketing-pro:cowork-setup once so brand state persists across Cowork sessions via your team's Google Drive.

Why Digital Marketing Pro

Most AI marketing tools generate isolated outputs — a campaign brief here, an email there. No canonical sequence, no shared state, no enforced structure. Result: inconsistent depth, missed dependencies, outputs that don't compound.

DM Pro runs every brand through the same 12 parts, producing the same files in the same order, with explicit dependency rules between them. That's the whole product. Everything else — the 158 skills, 24 agents, May–June 2026 compliance updates, Cowork persistence — exists to make that 12-Part Flow ship cleanly for real agencies on real client work.

What you get in 60 minutes

Run /digital-marketing-pro:engagement and the plugin produces a full brand-strategy engagement in roughly 60 minutes on Opus 4.8 — ~50–60 canonical files organized by part:

• Part 1 — Stone-vs-Opinion intake (what the client knows for certain vs what they believe)
• Part 2 — External market research (unbiased, no client docs)
• Part 3 — Four Core Documents — 61 explicit steps across Business & SBU Analysis, Segmentation Framework, Brand Positioning & Communications, DMFlow
• Part 4 — Competitive + Customer + Market analysis (4 unbiased docs)
• Part 5 — Client Validation Document — the one true stop
• Part 6 — Selective v2 re-runs per Decision Matrix
• Part 7 — Preparation documents (campaign architecture, KPI tree, content pillars, approval chains)
• Part 8 — Growth Plan + 12-month Yearly Planner (the flagship deliverable)
• Part 9 — Channel-strategy fan-out (up to 17 channel docs in 7 families)
• Part 10 — Execution artefacts (ad copy, post copy, headlines, CTAs)
• Part 11 — AI creative briefs (with Nano Banana Pro / Veo 3.1 / Gemini Omni model guidance and C2PA + deepfake-disclosure clauses)
• Part 12 — Continuous improvement loop

Cost: roughly $15–40 in Claude API spend for a full 12-part engagement using Opus 4.8. The plugin itself is MIT-licensed and free.

Quick start

1. Install on Claude Code (canonical)

/plugin marketplace add indranilbanerjee/neels-plugins
/plugin install digital-marketing-pro@neels-plugins

/plugin commands work in Claude Code (CLI + IDE at claude.com/code) and Anthropic Cowork. In the standard Claude chat app (browser claude.ai OR the installed Claude Desktop app) plugins still install and run, but management is via the Plugins UI button at the bottom of the chat — not via /plugin slash commands. See the Updating section for the recovery procedure if you accidentally try a slash command in the chat UI.

2. Turn on auto-update (recommended)

Third-party marketplaces have auto-update OFF by default in Claude Code — no banner tells you when a new version ships. Fix it once:

Open /plugin → Marketplaces tab → find neels-plugins → toggle Enable auto-update. Done — future releases pull at session start; /reload-plugins applies mid-session without restart.

3. Set up your first brand

/digital-marketing-pro:brand-setup

Interactive brand profiling — voice, audience, channels, industry, target jurisdictions, competitors, goals. Quick mode (5 questions) or full mode (17 questions). Optional: /digital-marketing-pro:import-guidelines to bulk-load existing brand guidelines, SOPs, or templates.

4. Run a full engagement, or jump straight to a workflow

/digital-marketing-pro:engagement           # full 12-Part Strategy Flow (~60 min)

Or jump straight to one workflow:

/digital-marketing-pro:campaign-plan        # multi-channel campaign with budget, timeline, KPIs
/digital-marketing-pro:seo-audit            # technical + content + E-E-A-T + AI visibility audit
/digital-marketing-pro:content-engine       # blog / ad / email / social / landing / video drafts
/digital-marketing-pro:competitor-analysis  # multi-dimensional deep-dive
/digital-marketing-pro:performance-report   # trends + anomalies + recommendations
/digital-marketing-pro:email-sequence       # subject lines, copy, timing, segmentation
/digital-marketing-pro:check                # pre-publish quality gate (hallucination + voice + claims)
/digital-marketing-pro:status               # unified brand snapshot
/digital-marketing-pro:resume               # resume an interrupted long workflow (engagement / campaign-plan / etc.)
/digital-marketing-pro:output-folder        # open the user-visible ~/Documents/DigitalMarketingPro/ folder

5. Find your output

~/.claude-marketing/<brand-slug>/
├── brand-profile.json           ← brand voice, audience, guardrails, jurisdictions
├── engagements/
│   └── <engagement-slug>/
│       ├── 01-client-inputs/    ← Part 1 Stone-vs-Opinion intake
│       ├── 02-research/         ← Part 2 external market research
│       ├── 03-four-core/        ← Part 3 Four Core Documents (61 steps)
│       ├── 04-analysis/         ← Part 4 competitive / customer / market
│       ├── 05-validation/       ← Part 5 Client Validation Document
│       ├── 06-v2-reruns/        ← Part 6 selective v2 re-runs
│       ├── 07-prep/             ← Part 7 internal operating layer
│       ├── 08-growth-plan/      ← Part 8 Growth Plan + Yearly Planner
│       ├── 09-channels/         ← Part 9 channel-strategy fan-out
│       ├── 10-execution/        ← Part 10 ad copy / post copy / headlines / CTAs
│       ├── 11-creative-briefs/  ← Part 11 AI creative instructions
│       ├── 12-improvement/      ← Part 12 continuous improvement loop
│       └── PROJECT_INSTRUCTIONS.md  ← Living Project Instruction File
└── insights/                    ← cross-engagement learnings

See the Multi-Brand & Agency Guide for the multi-client switching workflow.

Real workflows you'd actually run

🆕 New-client onboarding (agency, week 1)

/digital-marketing-pro:brand-setup "ACME Corp"        # interactive: voice, audience, channels, jurisdiction
/digital-marketing-pro:competitor-analysis            # multi-dimensional deep-dive on top 5 competitors
/digital-marketing-pro:engagement                     # full 12-Part Strategy Flow (~60 min on Opus 4.8)
/digital-marketing-pro:check  engagements/.../03-four-core/*.md   # pre-publish gate before client review

Output: ~50–60 canonical files. Cost: $15–40 in API spend. Time saved: ~3 weeks of senior-strategist labor.

📊 Quarterly business review (in-house, last week of quarter)

/digital-marketing-pro:performance-report   --period=Q2-2026
/digital-marketing-pro:attribution-report   --period=Q2-2026 --model=data-driven
/digital-marketing-pro:competitor-monitor   --since=2026-04-01
/digital-marketing-pro:continuous-improvement-loop --quarter=Q2-2026

Output: stakeholder-ready Q2 review with anomalies, attribution shift, competitor moves, and next-quarter recommendations.

🎯 SEO sprint (any audience, 1 week)

/digital-marketing-pro:seo-plan                       # 4-pillar scorecard; weakest pillar drives the theme
/digital-marketing-pro:keyword-cluster  seeds.csv     # SERP-overlap clustering into pillar+spokes
/digital-marketing-pro:backlink-gap  acme.com competitor1.com competitor2.com
/digital-marketing-pro:content-engine                 # draft the top 3 pillar pages
/digital-marketing-pro:check  drafts/*.md             # hallucination + brand voice + claims gate
/digital-marketing-pro:seo-drift  baseline.csv current.csv     # 30 days later, what moved

🤖 Marketing automation flow (builders)

/digital-marketing-pro:doctor                         # which actions are live vs need connector setup
/digital-marketing-pro:execute-action --action diagnostic --execute            # GA4 + GSC pull
/digital-marketing-pro:execute-action --action audit-current --execute         # workflow state check
/digital-marketing-pro:execute-action --action enable-automation --confirm     # Klaviyo flow activate

Output: real API calls fired against your stack with audit logging at ~/.claude-marketing/{brand}/executions/. Combine with n8n / Make / Zapier for human-in-the-loop approval gates.

🛡 Pre-publish compliance gate (every campaign)

/digital-marketing-pro:check  campaign.md --full      # hallucination + voice + claims + jurisdictions
/digital-marketing-pro:c2pa-metadata  hero.png        # sign image with provenance for EU Article 50

🎨 AI creative brief with EU disclosure (every AI-generated asset)

/digital-marketing-pro:ad-creative                # ad concepts + copy with EU/FTC disclosure clauses
/digital-marketing-pro:influencer-creator         # FTC + EU deepfake clauses baked in

Supported surfaces (v3.15.1)

Why this works: Agent Skills became an open standard in December 2025 (donated to the Agentic AI Foundation; adopted by 41+ agent products by June 2026 — see "Works on 40+ agent harnesses" below). All 158 SKILL.md files in DM Pro are platform-portable as written. The sibling manifests are thin platform-specific wrappers around the same skills/ directory — no skill duplication, no maintenance fork. The pattern is borrowed from Google's reference repo gemini-cli-extensions/data-agent-kit-starter-pack.

Minimum Claude Code version: 2.1.157 (declared via requiredMinimumVersion in plugin.json — landed in Claude Code v2.1.163, June 4 2026). Older Claude Code builds will be told to upgrade rather than load DMP with missing features.

Works on 40+ agent harnesses (via the Agent Skills open standard)

Beyond the 8 surfaces above where we ship a native manifest, DMP's 158 SKILL.md files work out-of-the-box on any agent that adopted the Agent Skills open standard (Anthropic-published Dec 2025, 41+ adopters as of June 2026). On each platform below, point it at our skills/ folder and all 158 marketing skills are immediately discoverable. No platform-specific manifest needed.

Tier 1 — verified-compatible platforms with explicit Agent Skills install paths:

Quick test on any Tier-1 platform:

# 1. Clone the skills folder (or point your platform at the GitHub raw URL)
git clone --depth=1 https://github.com/indranilbanerjee/digital-marketing-pro.git
# 2. Point your agent's skills-config at ./digital-marketing-pro/skills
# 3. Try: "Run a competitor analysis on stripe.com"
# Your agent picks /digital-marketing-pro:competitor-analysis automatically.

Why we don't ship per-platform manifests for these: the Agent Skills standard says agents discover by walking a directory tree for SKILL.md files — no manifest required. Shipping 35 extra wrapper manifests would create maintenance overhead with zero added value.

If you run into a platform-specific install snag, file a GitHub issue — we'll add platform-specific docs as users report patterns.

The 12-Part Engagement Methodology

Key architectural concepts:

• Two-Views Model — Every engagement carries v1 (unbiased market view) and v2 (client-validated view) after Part 5. Operating decisions reference v2; ideation references both. v1 is never deleted.
• Stone vs Opinion — Every fact captured at intake is tagged with confidence. Stone = client knows for certain. Opinion = client believes (becomes a research question, not ground truth).
• Decision Matrix — Maps client validation responses to which v1 documents need v2 re-runs. Prevents over- and under-re-running.
• Update-Back Rule — Live operations surface corrections → source documents get versioned (v2.1, v2.2 …) → Living Project Instruction File propagates the change to all downstream skills.
• Living Project Instruction File — Single source of truth per engagement. All skills read it first.

15+ strategic-framework reference documents in skills/context-engine/ support the methodology (Five Digital Markets, Channel Families, In-Market vs Out-Market, Multi-Dimensional Decision Framework, Unit Economics, Actionable Persona Format, B2B Decision-Making Unit, Three-Scenario Forecasting, 30/60/90-Day Framework, Reporting Cadence, Fixed vs Variable Budget, Competitor 3-Question Output, India Market Context, and more).

What's new

DM Pro is updated against the actual current marketing ecosystem state — June 2026 platform refresh, Google I/O 2026, the active broad core algorithm update, EU AI Act draft implementing guidelines, Meta platform expansions, and the latest AI image/video model landscape. No "trained on 2024 data" surprises in your client outputs.

v3.15.1 — Self-containment patch (July 12) Removed every cross-plugin capability reference from the skill surface: ad-creative and the engagement's Part 11 hand visual production to your own tooling (design team, AI generators, or connected design platforms) instead of naming a sibling plugin; launch-campaign C2PA signing and checkpoint-resume route through DMP's own c2pa-metadata and /digital-marketing-pro:resume; validate-profile checks DMP's own publish dir ($DIGITAL_MARKETING_PRO_PUBLISH_DIR / ~/Documents/DigitalMarketingPro/); the EU compliance reference docs are DMP-centric. DMP is fully standalone — no other plugin is ever required for any documented capability. Cross-promo links in this README stay; capability delegation is gone.

v3.15.0 — Reliability & Truth (July 7) A full-repo audit (orchestration, agents, skills, scripts, docs/manifests) surfaced ~200 findings, all fixed in one pass. One shared workspace-root/slugify/atomic-write helper (_common.py) ends the storage split-brain; connectors are honestly opt-in (the shipped .mcp.json is empty, fictional npm packages purged, memory backends demoted to "only if connected"); all 18 execution skills carry a uniform ## Execution gate and flip to disable-model-invocation: false (closes issue #6); the Tessl workflow moves to the tessl review CLI + .github/tessl-rubric.yml (closes issue #8); competitor-intelligence merges into competitive-intel (25 → 24 agents); embed-c2pa.py gains the EU AI Act Article 50 --ai-disclosure assertion; and a new check_skill_contracts.py doc-vs-argparse linter + state-layer tests grow the suite 123 → 207 passing. Every fabricated capability, stale count, and phantom flag is fixed or labeled.

v3.14.1 — README sync + test-infra extension (June 28) Patch release fixing 4 stale references in this README that escaped the v3.14.0 ship: the Cowork badge anchor, the ## Supported surfaces heading, a second internal anchor, and the missing v3.13.1 + v3.14.0 entries in this very section. Plus extended tests/test_release_consistency.py to lock the Supported-surfaces heading to the canonical version + verify all anchor links to #supported-surfaces-v… match — so this drift class can never reach a release again. No runtime change.

v3.14.0 — June 2026 market-refresh sweep (June 28) Comprehensive ecosystem-change audit against primary vendor docs. Every claim verified against Anthropic / OpenAI / Google AI / Google Ads / EU Commission primary sources before any code change.

• Meta Graph API bumped v20.0 → v24.0 in scripts/connector_resolver.py (4 callsites). All pre-v24 Meta Marketing API calls were scheduled to fail 2026-06-09 — our v20 hits would have started returning HTTP 400/410. Affected: campaigns / posts / feed / campaign-updates endpoints.
• Model registry rebuilt to 47 entries verified against platform.claude.com, developers.openai.com, ai.google.dev/gemini-api/docs/deprecations. New active flagships: Claude Opus 4.8 (now Anthropic's recommended), GPT-5.5 family, gpt-image-2, Gemini 3.1 Pro Preview, Gemini 3.1 Flash-Lite, Veo 3.1 Preview, Nano Banana Pro (GA gemini-3-pro-image), Nano Banana 2 (GA gemini-3.1-flash-image with video-to-image). Newly deprecated: full GPT-5 family + o3 family (shutdown 2026-12-11), Gemini 2.5 family (shutdown 2026-10-16), Imagen 4 (2026-06-15). Newly retired and routed to replacements automatically: Gemini 2.0 family (shutdown 2026-06-01), Gemini 3 preview image variants (shutdown 2026-06-25), Veo 2.0/3.0/3.0-Fast (shutdown 2026-06-30).
• Resolver now auto-rewrites retired model IDs to their replacement_id unconditionally (was previously only deprecated status). Means cached config pointing at dead model IDs gets routed to a working replacement instead of HTTP 404. New test test_retired_falls_forward_unconditionally covers this.
• python scripts/resolve_model.py --check-params <file> scanner flags any Python file passing temperature / top_p / top_k near Claude Opus 4.7+ targets (those return HTTP 400). Pre-flight scan of all 3 plugins' scripts/*.py was clean.
• 18 aliases re-pointed. latest-text-anthropic → claude-opus-4-8, latest-text-openai → gpt-5.5, latest-image-photoreal-google → gemini-3-pro-image (Imagen 4 was deprecated path), latest-video-google → veo-3.1-generate-preview, latest-image-google → gemini-3-pro-image (was retired preview ID).
• Google Ads API v24.1 + v24.2 documented in skills/paid-advertising/google-ads.md. v24.1 added 4 new experiment types (ADOPT_AI_MAX, ADOPT_BROAD_MATCH_KEYWORDS, OPTIMIZE_ASSETS, PMAX_REPLACEMENT_SHOPPING) + mobile_device_platform segment. v24.2 added GENERATE_LANDING_PAGE_TEXT asset automation + first-class Local Services Ads (AssetGroup.google_local_services_info) + beta MultiPartyAuthReview for regulated verticals.
• EU AI Act Code of Practice second-draft refresh in skills/context-engine/eu-code-of-practice.md. Section 1 (Providers) now consolidates around two-layered marking (secured metadata required + watermarking required); C2PA explicitly satisfies the metadata layer. Section 2 (Deployers) dropped the AI-generated-vs-AI-assisted taxonomy entirely in favor of design + placement requirements for icons/labels/disclaimers on deepfakes + text publications on matters of public interest. Added operational readiness checklist for 2026-08-02 Article 50 applicability date.
• Google I/O 2026 additions: skills/aeo-audit/SKILL.md adds callout for Google Information Agents (AI Pro/Ultra subscriber feature launching summer 2026) as future 7th probe target alongside ChatGPT/Perplexity/AI Mode/AI Overviews/Gemini/Copilot. skills/local-seo/SKILL.md adds 2026 priority section for Google Agentic Booking expansion to local services / home repair / beauty / pet care with three opt-in requirements (GBP scheduling integration, AvailabilityFeed structured data, Service-catalog price transparency).
• EvoLink vendor support added to model curator (via community PR merged during this release): multi-provider API gateway aggregating DeepSeek/Doubao/MiniMax through a single API key. 3 new aliases (latest-text-evolink, latest-balanced-evolink, latest-fast-evolink).
• docs/MODEL-CURATOR.md refresh with current alias resolutions + new § "Parameter compatibility — Claude Opus 4.7 and later" explaining the HTTP 400 risk.

Test count: 114 → 120. Native platforms unchanged at 8.

v3.13.1 — Test infrastructure hardening + user-friendliness polish (June 9) Triggered by user push-back: "you have the testing infrastructure, so test everything properly and make sure everything works awesomely."

• Tests expanded 70 → 114 with three new test modules: test_release_consistency.py (25 tests) catches version drift / README badge staleness / CHANGELOG out-of-sync / install commands going missing / critical sections going missing / broken anchor links; test_hermes_edge_cases.py (10 tests) for adapter resilience under bad ctx / None / SDK surface drift; plus assorted top-ups.
• Troubleshooting section added to README covering common install issues for all 8 native platforms (Claude Code / Cowork / Codex / Cursor / Copilot CLI / Antigravity / Hermes / OpenClaw).
• 5-minute non-developer install path added to README for marketers who don't want to read 60K of docs to get started.

v3.13.0 — Multi-harness expansion: native Hermes + OpenClaw + 40 Agent Skills platforms (June 9) Verified-real native manifests for two more agent harnesses, plus documented compatibility with 35 additional platforms via the Agent Skills open standard. Every claim verified against primary sources (the Hermes plugin docs at hermes-agent.nousresearch.com, the OpenClaw manifest spec at docs.openclaw.ai, the Agent Skills client showcase at agentskills.io).

• Hermes Agent (Nous Research) — native plugin via plugin.yaml + __init__.py at repo root. The Python adapter walks our skills/ directory at register-time and exposes all 158 marketing skills to Hermes via ctx.register_skill(). Defensive coding throughout — no Hermes runtime dependencies; uses stdlib only; degrades gracefully if the Hermes API surface differs from spec. Tested against Hermes Desktop v0.15.2 (public preview June 2 2026). Install: hermes plugins install indranilbanerjee/digital-marketing-pro.
• OpenClaw (formerly Clawdbot / Moltbot) — native manifest via openclaw.plugin.json at repo root. Points OpenClaw at ./skills for direct discovery. OpenClaw also auto-detects our existing .claude-plugin/plugin.json as a Claude-compatible bundle, so the native manifest is for first-class discoverability + ClawHub marketplace eligibility. Install: openclaw plugins install git:github.com/indranilbanerjee/digital-marketing-pro.
• 40+ Agent Skills platforms documented — Goose (Block) · OpenHands · OpenCode · Junie (JetBrains) · Gemini CLI · Roo Code · Kiro · Amp · Letta · Mux (Coder) · Factory · Workshop · Tabnine · Mistral Vibe · Emdash · Superconductor · Ona · VT Code · Qodo · Piebald · Autohand Code CLI · pi · Command Code · TRAE (ByteDance) · Firebender · bub · fast-agent · nanobot (HKUDS) · Vita · Snowflake Cortex Code · Databricks Genie Code · Laravel Boost · Spring AI · Agentman · Google AI Edge Gallery. All read SKILL.md files from a directory tree — point any of them at our skills/ folder and 158 marketing skills are immediately discoverable.
• 70-test stdlib suite (up from 49) — 21 new tests cover the Hermes adapter (plugin.yaml schema validation, __init__.py import smoke test, register(ctx) against mock context with all 158 skills, graceful degradation when ctx surface differs from spec) and the OpenClaw manifest (id + configSchema required, skills field points at ./skills, no hooks, no unexpected fields). Run with `pyt