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 about an hour per brand on a top-tier model (measured in 2026; your model and plan change the time). 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 — 164 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, OpenClaw, and Grok + 35+ Agent Skills platforms. Created by Indranil Banerjee · LinkedIn · X.

🆕 Just shipped — v3.35.8 (October 12, 2026): the command that returns autopilot to propose-only works from any folder, and the script checks cover new folders by default. What's new · 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.

How it works

Every brand runs the same 12 parts in the same order; Part 5 is the one stop where the client validates. Details: The 12-Part Engagement Methodology.

Try this first

Install, then ask in plain words. Each of these kinds of request reached the right skill in our trigger tests.

Safety and approvals

• Writes the plugin sends itself (/digital-marketing-pro:execute-action) fire only against a single-use approval record for that exact request: the script prepares the record with a preview of the request, the skill approves it after you type yes, and the request must match it byte for byte within 15 minutes. The record proves the approval step ran for this request, once; it cannot prove who typed yes, because the agent runs every command.
• Writes through MCP server tools (Google Ads, Meta, LinkedIn, TikTok, Amazon and other connected servers) are outside that code check. They rely on the skill's typed-yes gate and your host's permission prompt.
• Keep the gate you control. Leave connector_executor.py --execute and MCP write tools out of your host's command allowlist so it asks you every time; bypass or auto-approve modes remove that check.
• Autopilot proposes by default. It applies a correction on its own only under a standing approval you approved: scoped, capped per day, at most 30 days. Details in PRIVACY.md.

What it will never do

• Install a package on its own. A missing one prints the exact pinned install command.
• Send, publish or spend without your typed yes (or a standing rule you approved). Writes it sends itself also need the single-use approval record above.
• Ask for an API key in the chat. Connectors read keys from environment variables.
• Connect a service you did not set up. No MCP server ships enabled and no hooks run.
• Remove or hide AI watermarks. AI involvement is disclosed, with C2PA provenance where the format supports it.

What it costs

• The plugin is free (MIT-licensed).
• Model usage (tokens). On a subscription (Claude Pro, Max, Team or Enterprise in Claude Code or Cowork; a ChatGPT plan in Codex; a Cursor or Copilot plan; the same goes for other hosts' plans) the tokens count against your plan's usage limits instead of being billed per token; check your plan for any optional extra-usage billing. Only pay-as-you-go API-key users pay per token. Context (the skill listing, a skill's instructions, the documents it reads) uses context window and usage allowance for everyone, and money only for API users. A full engagement is a heavy user; /usage in Claude Code shows per-model consumption.
• Services you connect with your own keys (ad, email and CRM platforms, SEO and data APIs such as Ahrefs or DataForSEO) are billed by those providers whatever plan you are on, and the money an action moves (an ad budget, a send) is spent on their side. Live writes wait for your typed yes first.

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 in with your Claude account (Cowork usage counts against your plan).
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.

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/brands/<brand-slug>/
├── profile.json                              ← brand voice, audience, guardrails, jurisdictions
├── insights.json                             ← cross-engagement learnings
└── engagements/
    └── <engagement-id>/
        ├── _engagement.json                  ← state: current part, completed parts, change log
        ├── living-instruction-file.md        ← Living Project Instruction File
        ├── part-01-client-inputs/            ← Part 1 Stone-vs-Opinion intake
        ├── part-02-external-research/        ← Part 2 external market research
        ├── part-03-four-core-documents/      ← Part 3 Four Core Documents (61 steps), v1/ and v2/
        ├── part-04-competitive-customer-market/  ← Part 4 analyses, v1/ and v2/
        ├── part-05-client-validation/        ← Part 5 Client Validation Document
        ├── part-06-v2-reruns/                ← Part 6 selective v2 re-runs
        ├── part-07-preparation/              ← Part 7 internal operating layer
        ├── part-08-growth-plan/              ← Part 8 Growth Plan + Yearly Planner
        ├── part-09-channel-strategy/         ← Part 9 channel-strategy fan-out
        ├── part-10-execution-artefacts/      ← Part 10 ad copy / post copy / headlines / CTAs
        ├── part-11-ai-creative-instructions/ ← Part 11 AI creative instructions
        └── part-12-continuous-improvement/   ← Part 12 continuous improvement loop

The workspace is ~/.claude-marketing/ unless CLAUDE_MARKETING_HOME or your host's plugin data folder says otherwise; user-facing deliverables are also copied to ~/Documents/DigitalMarketingPro/ (/digital-marketing-pro:output-folder opens it).

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

Who this is for

How does this compare?

Other marketing plugins exist, including Anthropic's own marketing plugin and community SEO skill sets, and each is good at what it covers. What sets Digital Marketing Pro apart:

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 164 skills, 24 agents, 2026 compliance updates, Cowork persistence — exists to make that 12-Part Flow ship cleanly across real marketing operations.

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 a top-tier model (measured 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 current image- and video-model guidance and C2PA + deepfake-disclosure clauses)
• Part 12 — Continuous improvement loop

Cost: the plugin is MIT-licensed and free. A full 12-part engagement writes about 50–60 documents, so it uses a lot of model tokens: on a subscription that counts against your plan's usage limits, and only pay-as-you-go API-key users are billed per token (What it costs).

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-class)
/digital-marketing-pro:check  engagements/<id>/part-03-four-core-documents/v1/*.md   # pre-publish gate before client review

Output: ~50–60 canonical files. 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 --brand acme --execute         # GA4 + GSC tag/consent check (MCP path: returns the manifest)
/digital-marketing-pro:execute-action --action audit-current --brand acme --execute      # current SEO state (Ahrefs over HTTP; GSC via MCP)
/digital-marketing-pro:execute-action --action enable-automation --brand acme --execute  # email automation flow: prepares a preview + approval record
# after you type yes: approval-manager.py --brand acme --action approve --id <id>, then re-run with --approval-id <id>

Output: HTTP calls for the 8 executable connectors (Slack, HubSpot, Klaviyo, SendGrid, Brevo, Customer.io, Mailchimp, Ahrefs), MCP manifests for the rest; each write fires against a single-use approval record for that exact request and is logged at ~/.claude-marketing/brands/{brand}/executions/. See Safety and approvals.

🛡 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.35.8)

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 164 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.

Recommended Claude Code version: current. Claude Code has no plugin-level minimum-version field — requiredMinimumVersion is a managed setting that pins the host version for everyone, so a plugin cannot enforce it (DMP declared it in plugin.json from v3.12.0 to v3.31.1, where Claude Code silently stripped it; corrected in v3.32.0). Teams that want a floor set it in their own settings.json — see settings.json.example.

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

Beyond the 9 surfaces above where we ship a native manifest, DMP's 164 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, copy our skill folders (the folders inside skills/) into the folder it reads and all 164 marketing skills are discoverable. No platform-specific manifest needed.

Platforms that have adopted the Agent Skills standard. Where a row gives an install hint, it was checked against that tool's own documentation in October 2026; most of these tools read skills from a folder, so the hint names the folder to copy the skill folders into:

Quick test on any of these platforms:

# 1. Clone the repository
git clone --depth=1 https://github.com/indranilbanerjee/digital-marketing-pro.git
# 2. Copy the folders inside ./digital-marketing-pro/skills/ into your tool's skills folder (see the table above)
# 3. Try: "Run a competitor analysis on stripe.com"
# Your agent should pick the competitor-analysis skill.

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

v3.35.8 — the propose-only command works from any folder (October 12, 2026)

From the fresh-install smoke test's recheck. PRIVACY.md's command for returning autopilot to propose-only used a relative scripts/ path that fails from your own project; it now uses the plugin's folder. The check that every script-running file says where the scripts are now covers every document by default instead of a list of folders. Printed commands carry no text after them, so a PowerShell note never swallows it, and a test confirms no script waits for input on Claude Code's open stdin pipe. 700 tests.

v3.35.7 — errors exit non-zero; commands paste into Git Bash (October 12, 2026)

From the fresh-install smoke test's recheck. Fifteen scripts printed an error and exited 0, so a caller checking $? read a failure as success: utm-generator (a missing CSV, or a CSV where every row failed), the SEO and local-SEO auditors, the budget, ROI and lifetime-value calculators, the scorers and others. A bad argument now exits 2 and a failure 1; utm-generator exits 3 for a partly failed batch, as its --help says. Printed commands use forward slashes, so they run in Git Bash (Claude Code's Bash tool on Windows) as well as PowerShell. 694 tests.

v3.35.6 — quoted paths, BOM-safe inputs, hints that run anywhere (October 12, 2026)

From the fresh-install smoke test's final pass. Five skill commands ran an unquoted ${CLAUDE_PLUGIN_ROOT} path, which breaks in a folder with a space; every such path is now quoted and a test checks them all. utm-generator.py --csv turned Excel's "CSV UTF-8" export into rows of missing URLs (still exiting 0), and --prepare-batch refused a plan saved by PowerShell; every script now reads files with or without a BOM and never writes one. Printed hints run a script by the interpreter and its absolute path. 680 tests.

Older releases are in CHANGELOG.md.

How the SEO skills chain together

Most SEO work uses 3-5 skills in sequence rather than one mega-skill. The plugin is designed so that each skill produces numbered intermediate files (01-...md, 02-...md, …, PLAN.md) under ${CLAUDE_PLUGIN_DATA}/{brand}/seo/{workflow}/{date}/ — downstream skills read those numbered files, not the endpoint, so you can re-run any single step without redoing the whole chain.

Agency onboarding workflow (week 1 of a new client engagement):

1. /digital-marketing-pro:brand-setup
2. /digital-marketing-pro:competitor-analysis        ← picks the right competitors for everything downstream
3. Run all in parallel:
   /digital-marketing-pro:tech-seo-audit             ← baseline technical health
   /digital-marketing-pro:aeo-audit                  ← baseline AI visibility
   /digital-marketing-pro:backlink-gap               ← link prospects (needs competitors from step 2)
   /digital-marketing-pro:gsc-ai-performance         ← GSC AI Performance Report (3 Jun 2026)
4. /digital-marketing-pro:keyword-cluster            ← pillar+spokes architecture from aeo-audit content gaps
5. /digital-marketing-pro:seo-plan                   ← DISPATCHER — reads all of the above, scores 4 pillars,
                                                       the weakest pillar drives the lead theme of Q1's roadmap

Quarterly review workflow:

1. /digital-marketing-pro:gsc-ai-performance         ← fresh GSC AI export
2. /digital-marketing-pro:seo-drift                  ← compare this quarter vs last (auto-classifies gainers,
                                                       losers, reshuffles, new keys, lost keys)
3. Branch by finding:
   - High decline → /digital-marketing-pro:seo-audit + /digital-marketing-pro:content-decay-scan
   - High reshuffle → /digital-marketing-pro:aeo-geo (intent realignment)
   - High growth → /digital-marketing-pro:content-engine (amplification briefs)
4. /digital-marketing-pro:seo-plan                   ← re-run dispatcher with fresh inputs;
                                                       lead theme may shift to a different pillar

Content production workflow:

1. /digital-marketing-pro:keyword-cluster            ← from your seed list
2. /digital-marketing-pro:content-brief              ← per pillar from the cluster plan
3. /digital-marketing-pro:content-engine             ← drafts with brand voice + fact-check + humanize + SEO checklist
4. /digital-marketing-pro:check                      ← pre-publish gate (hallucination + brand voice + structure)
5. /digital-marketing-pro:publish-blog               ← push to CMS
6. /digital-marketing-pro:c2pa-metadata              ← if EU markets are targeted and AI images accompany

Backlink campaign workflow:

1. /digital-marketing-pro:competitor-analysis
2. /digital-marketing-pro:backlink-gap               ← gap-vs-competitors with link-prospect priority scoring
3. /digital-marketing-pro:digital-pr                 ← consumes the prospect shortlist + outreach templates
4. /digital-marketing-pro:pr-pitch                   ← drafts individual pitches per prospect

Each skill has a quality scorecard that must pass before its PLAN.md is declared ready, and every heavy skill carries a Tips & caveats section with the common pitfalls. The seo-plan dispatcher uses Confirm-Then-Dispatch — it never silently re-runs expensive specialists, always asking explicitly with cost estimate before fanning out.

Architecture — what's actually in the box

24 specialist agents

Marketing Strategist · Brand Guardian · Content Creator · Email Specialist · Social Media Manager · PR Outreach · SEO Specialist · CRO Specialist · Analytics Analyst · Marketing Scientist · Market Intelligence · Influencer Manager · CRM Manager · Growth Engineer · Journey Orchestrator · Agency Operations · Performance Monitor · Quality Assurance · Memory Manager · Execution Coordinator · Intelligence Curator · Localization Specialist · Media Buyer · Competitive Intel

Each agent has scoped responsibilities, explicit input/output contracts, and reads the Living Project Instruction File before acting.

164 skills

Skills are invoked by description match through the Skill tool, addressable as /digital-marketing-pro:<skill-name> from chat. Coverage: brand setup, content production (blog / ad / email / social / landing / video / PR / case study), SEO / AEO / GEO audits (6 platforms incl. Google AI Mode), competitor monitoring, campaign planning, channel-specific strategies, attribution, churn risk, lifecycle journeys, intelligence reports, eval framework, knowledge management, multi-brand operations, regional configuration, C2PA content provenance, Cowork+Drive team persistence.

Slash commands

Every skill answers to /digital-marketing-pro:<skill-name>. Five more are standalone commands with no same-named skill: engagement, resume, output-folder, doctor and execute-action. v3.33.0 folded every command that duplicated a same-named skill into that skill, so those slash names work exactly as before and each now loads once instead of twice. The most-used:

Every other skill works the same way — :competitor-monitor, :churn-risk, :autopilot-status, :agency-dashboard, :aeo-audit, :geo-monitor, :c2pa-metadata, :client-onboarding, :journey-design … see /digital-marketing-pro:help after install for the full list, or browse skills/ in the repo.

95 Python scripts (optional)

Plugin works fully without Python — all marketing knowledge, frameworks, agent capabilities, and skills work out of the box via the 177 reference knowledge files.

14 HTTP MCP connectors

Notion · Slack · Canva · Figma · HubSpot · Amplitude · Ahrefs · SimilarWeb · Klaviyo · Google Calendar · Gmail · Stripe · Asana · Webflow

These are an opt-in catalog — no .mcp.json ships (it is gitignored), so nothing auto-connects; enable only the ones you need. All HTTP, all Cowork-compatible. For services without first-party HTTP MCPs (Google Sheets, Drive, Salesforce, etc.), see .mcp.json.connectors-reference for Pipedream / Composio / Zapier / Make.com aggregator paths.

For the extended stdio catalog (Google Ads, Meta Ads, GA4, GSC, Brevo, etc. via npx, Claude Code only — not Cowork-compatible; verify each npm package exists before use, npx runs remote code): cp .mcp.json.example .mcp.json. See CONNECTORS.md and Integrations Guide.

Resumable workflows and a visible output folder

Two user-team complaints from the v3.7.5 cycle drove this release: "dm pro is taking too long to process" (the 60-minute engagement that breaks midway loses 30+ minutes of work on restart) and the general "where did my 50 deliverable files save?" confusion (everything was landing under the Windows-hidden ~/.claude-marketing/ dotfolder).

Fix 1 — Resumable workflows. Every long-running DMP workflow now writes per-part checkpoints to disk so an interrupted session can resume from the next un-checkpointed part instead of restarting from Part 1. Covered workflows: engagement (12-Part Strategy Flow), campaign-plan, content-engine, seo-audit, competitor-analysis, campaign-audit (v3.7.5), launch-campaign (v3.7.5), plus a custom slot for any other long flow. Resume with:

/digital-marketing-pro:resume                              # auto-pick latest in-progress run
/digital-marketing-pro:resume engagement                   # filter to a workflow
/digital-marketing-pro:resume engagement <run-id>          # pick a specific run

Fix 2 — Visible output folder. Every artifact a workflow produces is now copied to TWO locations: the internal tracking copy under ~/.claude-marketing/brands/{brand}/output/{workflow}/... (system-of-record), and a user-visible published copy under ~/Documents/DigitalMarketingPro/{brand}/{workflow}/{YYYY-MM}/{filename} (visible in Windows Explorer / macOS Finder by default). Override the visible root with DIGITAL_MARKETING_PRO_PUBLISH_DIR=/path (e.g. a Dropbox share for the team). Reveal the folder any time with:

/digital-marketing-pro:output-folder                       # opens ~/Documents/DigitalMarketingPro/{brand}/
/digital-marketing-pro:output-folder <brand> <workflow>    # drill down

Implementation: scripts/checkpoint-manager.py (per-step storage + atomic writes, stdlib only) + scripts/output-publisher.py (dual-copy publish + where + open subcommands: internal tracking copy + user-visible published copy). The engagement/checkpoint state machine ships tests in tests/test_engagement_state.py + tests/test_checkpoint_roundtrip.py; a fuller 5-scenario end-to-end simulation (clean 12-part run / interrupt-resume / parallel workflows / quality-gate fail / all-workflows-accepted) was used during development but is a dev tool, not shipped in the repo.

Connector-aware action resolver

The campaign-audit and launch-campaign skills depend on 14 actions that map to real marketing APIs (Google Ads, Meta Marketing, LinkedIn, TikTok, HubSpot, Salesforce, Klaviyo, Mailchimp, Customer.io, Gmail, Cision, Muckrack, Slack, Google Calendar, Ahrefs, Similarweb, SEMrush, Google Search Console). v3.7.5–v3.7.7 shipped these actions as honest stubs that always returned status: stub_implementation regardless of which connectors the user had. v3.7.10 introduces a resolver that probes the live state and resolves each action to one of three modes per call:

Check what's live in your environment any time:

/digital-marketing-pro:doctor                              # full readiness table
/digital-marketing-pro:doctor --summary                    # one-line counts
/digital-marketing-pro:doctor --action inventory --channel google_ads  # drill in

Test coverage: the resolver's action layer ships tests in tests/test_connector_resolver.py. A fuller 27-scenario development harness (14 actions × unconfigured / configured / local-execution variants) was used while building this out, but it is a dev tool and is not shipped in the repo.

Implementation: scripts/_connector_registry.py (catalog of 33 connectors, 11 categories, is_connector_configured() probe) + scripts/connector_resolver.py (ACTION_SPECS map + per-action manifest builders + local executors) + scripts/action-doctor.py (the doctor command's underlying script).

v3.7.11 — actions can actually fire HTTP requests from Python

The v3.7.10 resolver returned a manifest of "what would be sent." v3.7.11 adds scripts/connector_executor.py (stdlib urllib.request, no third-party deps) that takes that manifest and actually executes the request against the real API. Public CLI: /digital-marketing-pro:execute-action.

Executes end-to-end from Python (8 connectors, verified vendor docs):

Requires the MCP path (28 OAuth-only or MCP-only connectors): Google Ads, Meta Marketing, LinkedIn Marketing, LinkedIn Publishing, TikTok Ads, Twitter/X, Gmail, Google Calendar, Google Analytics, Google Search Console, Meta Graph, Salesforce, Pipedrive, Zoho CRM, Buffer, Hootsuite, Cision, Muckrack, Amplitude, Similarweb, SEMrush, Moz, Intercom, Canva, Figma, plus the official ad-platform MCP servers Meta Ads AI Connectors, Google Ads MCP (read-only) and Amazon Ads MCP. For all of these, the resolver still returns manifest_ready so you can see the exact HTTP shape Claude's MCP tool will send — Python just can't execute the OAuth flow itself.

Safety gates (updated in v3.35.0): read ops auto-execute with --execute; write ops need a matching approved, single-use approval record (--approval-id), see Safety and approvals; missing env vars block with setup_hint_credential; unresolved {VAR} placeholders block before the request fires. Every fired call logs to ~/.claude-marketing/brands/{brand}/executions/.

Test coverage: end-to-end HTTP send-and-receive for the 8 connectors (Slack body.ok post-check, Klaviyo vnd.api+json, Brevo lowercase header, Mailchimp Basic, plus the safety gates and data substitution) was validated during development against a stdlib http.server mock. That mock harness is a dev tool and is not shipped in the repo; the shipped suite covers the resolver layer via tests/test_connector_resolver.py.

Model curator: no hardcoded model ids

Frontier models change every ~6 weeks. Hardcoding claude-sonnet-4-5-20250929 or gemini-2.0-flash across dozens of scripts means a provider deprecation silently 404s, the user blames the plugin, and the maintainer has to grep three repos. So we don't hardcode.

• scripts/model_registry.json — single source of truth for every model id used by the plugin, with vendor, tier, modality, status, and replacement_id for deprecated entries.
• scripts/resolve_model.py — Python module + CLI. Resolves human aliases (latest-balanced-anthropic, latest-fast-anthropic, latest-text-openai, latest-vision-google, latest-image-google, latest-video-google) to concrete ids at call time. Deprecated ids passed via --model auto-fall-forward to their replacement (with a stderr warning).
• scripts/refresh_models.py — polls Anthropic / OpenAI / Google / Evolink list endpoints with your API keys and reports drift versus the registry (NEW models in the provider catalog, STALE models in the registry).

Every script that calls a provider model now accepts --model (or --openai-model / --anthropic-model for scripts/ai-visibility-checker.py) and the value is validated against the registry. See docs/MODEL-CURATOR.md for the full alias map, curation policy, and worked examples.

python scripts/resolve_model.py --alias latest-balanced-anthropic    # -> claude-sonnet-4-6
python scripts/resolve_model.py --check gemini-2.0-flash              # -> retired (auto-routes to gemini-3.5-flash)
python scripts/resolve_model.py --list --vendor anthropic --status current
python scripts/refresh_models.py                                      # drift report (needs API keys)

Compliance — 16 jurisdictions, EU AI Act Article 50 ready

DM Pro carries jurisdiction-specific compliance rules that auto-apply when a brand declares its target markets. Coverage:

🇪🇺 EU (GDPR + AI Act Article 50) · 🇺🇸 US Federal (CAN-SPAM) · 🇺🇸 California (CCPA/CPRA) · US 20+ state privacy laws · 🇨🇦 Canada (CASL + PIPEDA) · 🇧🇷 Brazil (LGPD) · 🇬🇧 UK (UK GDPR + PECR) · 🇦🇺 Australia (Privacy Act + Spam Act) · 🇸🇬 Singapore (PDPA) · 🇨🇳 China (PIPL) · 🇮🇳 India (DPDPA) · 🇯🇵 Japan (APPI) · 🇰🇷 South Korea (PIPA) · 🇸🇦 Saudi Arabia (PDPL) · 🇦🇪 UAE (Federal Decree-Law No. 45) · 🇹🇭 Thailand (PDPA)

EU AI Act Article 50 readiness (applicable 2 August 2026):

• C2PA content-provenance signing via /digital-marketing-pro:c2pa-metadata (end-to-end tested against c2pa-python 0.32 — 75-byte test PNG → 42,818-byte signed PNG with manifest_embedded_and_verified=true)
• Pre-publish gate (/digital-marketing-pro:check) treats missing C2PA on AI-flagged assets in EU campaigns as CRITICAL → BLOCKED
• Final Article 50 Guidelines + final Code of Practice on Transparency of AI-Generated Content (10 June 2026) in compliance-rules.md §1.1b.i with six-row clarification table + five-point action list
• Production cert guide at docs/c2pa-production-cert-guide.md covers the four CAI-recognised authorities (Adobe Content Credentials, Truepic, Numbers Protocol, Microsoft Azure Confidential Ledger)

Other May 2026 regulatory updates baked in:

• NY synthetic-performer disclosure law (live June 2026, $1K–$5K per violation, $10K repeat) — applies to synthetic influencers + AI endorsements
• FTC May 2026 endorsement guidance — synthetic influencers, AI testimonials, AI-edited creator content
• CJEU March 2026 ruling — pseudonymized cookie IDs are personal data when re-identification is feasible
• CCPA Jan 2026 ADMT amendments + AI-derived sensitive data classification
• DPDP Phase II preparation — consent manager registration opens Nov 2026

AEO / GEO — what changed in 2026

The search landscape pivoted hard in 2025–2026:

• Google AI Overviews appear on ~55% of all Google searches (Seer Interactive, Sept 2025); organic CTR on AI Overview queries dropped ~61% (1.76% → 0.61%); ~58% of Google searches are now zero-click
• Google AI Mode became the default conversational search experience for opted-in users at I/O 2026 (19 May 2026), backed by Gemini 3.5 Flash — ~1B MAUs
• ChatGPT search reaches ~883M MAU; Perplexity heavily skews citations to Reddit (47% of factual cites); Wikipedia drives 48% of ChatGPT citations

DM Pro's AEO/GEO skills (/digital-marketing-pro:aeo-audit, :geo-monitor, :entity-audit) reflect this:

• 6-platform audit standard — ChatGPT, Perplexity, Google AI Mode, Google AI Overviews, Gemini, Microsoft Copilot (was 5 — AI Mode added May 2026)
• Schema strategy refresh — Google's March 2026 core update demoted FAQ/Review/HowTo schema on non-primary pages. Skills emphasise entity-rich JSON-LD (Article + Organization + Person + Product) and offer an optional LLMs.txt companion (Google states it is not required for AI-features eligibility)
• Citation tracking across all 6 surfaces, with Profound / Otterly / Conductor AgentStack integration paths in the connectors layer
• Share of AI Voice as a first-class metric in /digital-marketing-pro:performance-report

Channel guidance — 2026 platform changes built in

• LinkedIn (March 2026 algorithm shift): external links and engagement bait penalized ~60%. New Depth Score measures dwell time. Followers no longer guarantee reach. Skills optimize for relevance and Depth Score.
• Email: Apple MPP affects ~64% of B2C opens — open rate is functionally dead as a primary KPI. DMARC + RFC 8058 one-click POST unsubscribe mandatory; non-compliant bulk mail to Gmail/Yahoo/Microsoft gets permanent 550 rejections. Spam threshold tightened to <0.10%.
• TikTok (post Jan 22 2026 USDS Joint Venture closing): US data + algorithm under USDS LLC; ByteDance retains <20%. AI-generated creators require disclosure label; AI content excluded from Creator Rewards Program; daily shoppable-post limits effective May 11 2026.
• Meta Advantage+ Leads (global as of May 2026), Threads ads (global, image-only), brand-safety inventory tiers (Expanded/Moderate/Limited — Limited costs ~30% reach).
• WhatsApp per-message pricing (since 1 July 2025) — India marketing template ≈ USD 0.0118 per message; 72-hour free service window from CTWA ads or Page CTAs.
• Third-party cookies — deprecation cancelled. First-party data is the strategic priority. The attribution-model skill defaults to first-party + MMM + incrementality stack.
• Sora dependency note: OpenAI consumer Sora app discontinued April 26 2026; Sora API September 24 2026. AI creative briefs default to Veo 3.1, Kling v3.0 Pro, Runway Gen-4, Gemini Omni.

Documentation

Two PDF references at the repo root: DM_Strategy_Complete_Learning_Guide.pdf (full methodology) and DM_Strategy_Flow_v3_2_Visualization_v1_23Apr26.pdf (one-page visual map).

FAQ

Q: How does this compare to LangChain marketing templates / CrewAI marketing crews / general AI marketing tools? Those are frameworks. DM Pro is a packaged, opinionated methodology with explicit dependency rules between every output. You can build something like it in LangChain or CrewAI — at the cost of months of engineering. DM Pro ships it.

Q: Which Claude interface should I use?

Q: How much does a full engagement cost? The plugin is free (MIT-licensed). A complete 12-part engagement writes ~50–60 documents, so it uses a lot of model tokens: on a subscription that counts against your plan's usage limits, and only pay-as-you-go API-key users are billed per token (What it costs). Track per-brand consumption via Claude Code v2.1.149+ /usage (now integrated into /digital-marketing-pro:agency-dashboard).

Q: Can I run multiple brands in parallel? Yes. Each brand has its own ~/.claude-marketing/brands/<brand-slug>/ directory and Python script state. Switch with /digital-marketing-pro:switch-brand.

Q: What if I only want a campaign plan, not the full methodology? Skip to /digital-marketing-pro:campaign-plan. Every individual surface (campaign / SEO / content / competitor / email / report) is independently runnable. The full engagement is the canonical path, not the only path.

Q: Will this work on Codex / Cursor / Copilot CLI / Antigravity? Yes — verified-real native manifests ship for all 9 surfaces (CC, Cowork, Codex, Cursor, Copilot CLI, Antigravity, Hermes Agent, OpenClaw, Grok). See Supported surfaces above for per-platform install commands.

Q: I run my team on Anthropic Cowork. Does brand state persist between sessions? Yes — but you need to run /digital-marketing-pro:cowork-setup once per team first (v3.12.0). Cowork's per-session filesystem is ephemeral, and ${CLAUDE_PLUGIN_DATA} is too (open issue #51398). The setup wizard routes brand profiles + plans + reports through a Google Drive MCP so everything survives across sessions and is shared across the team. Multi-team isolation via per-team folder names.

Q: What happens when a new Claude / OpenAI / Google model ships? Do I need to update the plugin? No — the plugin uses a shared model curator (scripts/resolve_model.py) that resolves aliases (latest-balanced-anthropic, latest-text-google, etc.) at call time. When a model is deprecated, the curator auto-falls-forward to the replacement. /digital-marketing-pro:doctor reports registry age and severity (ok <60d / warn 60-119d / urgent ≥120d); when stale it prints the exact python scripts/refresh_models.py invocation to poll the provider APIs for drift. Plus settings.json.example ships a fallbackModel chain so Claude Code transparently swaps models on overload.

Q: Is this an Anthropic product? No — independent open-source plugin built by Indranil Banerjee. MIT-licensed. Runs on Claude Code + Cowork.

Q: I found a compliance rule that looks out of date. File an issue with the citation. Privacy and AI law change quarterly — DM Pro is actively maintained against the May 2026 reality but enforcement actions and amendments keep coming.

Troubleshooting

Common install + first-run issues across all 9 supported platforms, with the fix.

Claude answers in chat instead of using a skill

Claude Code lists every installed skill in a budget of 1% of the context window. Digital Marketing Pro's 170 entries fit a 1M window in full, but on a 200k window only the names fit, so Claude can't see what each skill does. Add "skillListingBudgetFraction": 0.05 to your Claude Code settings.json. You can also start any skill by name, e.g. /digital-marketing-pro:seo-audit.

Claude Code + Cowork

"/plugin isn't available in this environment" You're in the standard Claude chat app (browser claude.ai or the Claude Desktop app). The /plugin slash command only works in Claude Code (the dev CLI/IDE at claude.com/code) and Anthropic Cowork. Everywhere else, plugins install via the UI: click the Plugins button at the bottom of the chat. See Updating for the full recovery procedure.

"Plugin installed but slash commands not showing" Run /reload-plugins (Claude Code) or restart the Cowork chat session. If still missing, your Claude Code build may be too old for the plugin features DMP relies on — run claude --version and update via npm install -g @anthropic-ai/claude-code (DMP cannot enforce a minimum itself; see Supported surfaces).

"Brand profile vanishes between Cowork sessions" Cowork's filesystem is per-session ephemeral — ~/.claude-marketing/ AND ${CLAUDE_PLUGIN_DATA} both reset at session end (open issue #51398). Fix: run /digital-marketing-pro:cowork-setup once per team — it routes brand state through a Google Drive MCP so profiles survive across sessions and your whole team sees them. See v3.12.0 release notes for the why-and-how.

"/digital-marketing-pro:doctor says urgent (model registry stale)" The model registry hasn't been refreshed for 60+ days — frontier models shift every ~6 weeks so deprecated IDs may start 404-ing. Fix: ANTHROPIC_API_KEY=... OPENAI_API_KEY=... GEMINI_API_KEY=... EVOLINK_API_KEY=... python scripts/refresh_models.py. The script polls each provider's /v1/models endpoint and reports drift versus our registry.

OpenAI Codex / Cursor / GitHub Copilot CLI / Antigravity

"Skills install but commands not discovered" These platforms read SKILL.md by description match — invoke via natural language ("Run a competitor analysis on stripe.com") rather than typing a slash command. Slash commands (/digital-marketing-pro:<name>) are a Claude Code convention; on other surfaces the agent picks up the skill from intent.

"Codex says skill name failed regex check" Codex enforces [a-z0-9-]+ on skill names. All 164 DMP skill names pass this regex (verified in the test suite). If you see this error, it's likely a personal skill you added — rename it to lowercase + hyphens only.

"Cursor /add-plugin returns 'plugin not found'" Use the full Git URL form: /add-plugin digital-marketing-pro@https://github.com/indranilbanerjee/digital-marketing-pro. Cursor's marketplace integration is fastest, but the Git URL form always works.

Hermes Agent

"hermes plugins install ... finishes but no skills appear" The plugin needs to be enabled after install: hermes plugins enable digital-marketing-pro. Then verify with hermes plugins list. If the adapter's register() returned silently with no skills, run the audit: cd ~/.hermes/plugins/digital-marketing-pro && python __init__.py — it'll print the discovered skill count + the first five skills, confirming the clone got the full skills/ tree.

"register_skill error in Hermes logs" Check Hermes version: this plugin targets v0.15.2+. Run hermes --version. Older builds may have a different ctx API surface — the adapter degrades gracefully (logs an error, doesn't crash) but won't register skills. Upgrade Hermes to the latest public preview.

OpenClaw

"OpenClaw can't find the plugin manifest" Use the git: install scheme: openclaw plugins install git:github.com/indranilbanerjee/digital-marketing-pro. If you used another scheme and it failed, the fallback is: cd ~/.openclaw/plugins && git clone https://github.com/indranilbanerjee/digital-marketing-pro && openclaw plugins enable digital-marketing-pro.

"OpenClaw uses Claude bundle but loses some features" OpenClaw auto-detects our .claude-plugin/plugin.json as a Claude-compatible bundle, but the native openclaw.plugin.json gives first-class discoverability. Both load the same 164 skills from ./skills. Verify with openclaw plugins inspect digital-marketing-pro --runtime --json.

Grok (xAI Build CLI)

"grok plugin install can't find the plugin" Use the direct repo form: grok plugin install indranilbanerjee/digital-marketing-pro — the native .grok-plugin/ manifest pair ships in-repo, so no separate marketplace is needed. Alternatively add the marketplace first: grok plugin marketplace add indranilbanerjee/neels-plugins then grok plugin install digital-marketing-pro. Append --trust to skip the install confirmation. Grok also reads the Claude Code manifests for compatibility, so even a pre-3.31.0 clone loads — the native pair is what gives first-class discoverability.

General (any platform)

"Tests in tests/ fail when I git clone locally" Run python tests/run_all.py from the repo root. All 700 tests are stdlib-only — no pip install needed. If they fail, the most likely cause is a Python version mismatch (DMP supports Python 3.10+) or a clone that omitted some skills/ subdirectories. Try git clone --depth=1 again.

"/digital-marketing-pro:doctor shows my action as stub_unconfigured" That action needs an MCP connector configured. Run python scripts/connector-status.py --action setup-guide --name <connector-name> for the exact setup snippet. Add it to your .mcp.json under mcpServers, restart your agent, and the action becomes manifest_ready. See Connector-aware action resolver for the full readiness model.

"Where do my brand files actually go?" Run /digital-marketing-pro:output-folder — it prints the active output directory and (on local Claude Code) opens it in your OS file manager. Default: ~/.claude-marketing/brands/<brand-slug>/ for working state + ~/Documents/DigitalMarketingPro/<brand>/ for finished deliverables. Both configurable via output-folder.

Still stuck? Open an issue with the exact error message + platform name + version. We respond within a few days.

Updating

If you see "/plugin isn't available in this environment" — you're in the standard Claude chat app (browser OR installed desktop app). The /plugin slash command is only supported in two environments: Claude Code (the developer CLI / IDE at claude.com/code, npm install -g @anthropic-ai/claude-code) and Anthropic Cowork. Everywhere else — claude.ai web chat, the Claude Desktop app, mobile — plugins are managed through the UI, not slash commands.

The plugin IS installed (your DM Pro skills work); only the management command is unavailable. Fix:

1. In the chat UI — click the Plugins button at the bottom of the chat → Manage plugins → find Digital Marketing Pro → look for Update / Refresh / Remove. If no Update button, Remove then Add plugin → re-install from indranilbanerjee/neels-plugins. The re-pull fetches the latest version.
2. For slash-command management — switch to Claude Code (CLI or IDE) or Cowork. The plugin runs identically across every Anthropic surface; you're choosing where to type management commands.

Once you're in Claude Code or Cowork, the rest of this section applies.

/plugin marketplace update neels-plugins
/plugin uninstall digital-marketing-pro@neels-plugins
/plugin install digital-marketing-pro@neels-plugins
/reload-plugins

/plugin marketplace update only refreshes the catalog — the uninstall + reinstall is what actually pulls the new version. /reload-plugins applies the change without restart.

If a version stays the same but content changed (fast-iteration debugging): delete the folder ~/.claude/plugins/cache/neels-plugins (it holds only downloaded plugin copies), then:

/plugin install digital-marketing-pro@neels-plugins
/reload-plugins

Neelverse Marketing Suite

DM Pro is part of a three-plugin suite by Indranil Banerjee — one marketplace, installed together, designed to chain (each plugin keeps its own brand setup):

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

Star history

If DM Pro saves your team time, ⭐ star the repo — it's the single most useful thing you can do to help other marketing teams discover it.

About the maintainer

DM Pro is built and maintained by Indranil “Neel” Banerjee — a builder and systems thinker with roots in information security and a second act across growth marketing, enterprise digital operations, and AI transformation. This repository is one public implementation of a broader focus on trustworthy AI execution: preserve context, make evidence inspectable, and keep people at consequential decision points.

• 🌐 Website: indranil.in
• 💼 LinkedIn: linkedin.com/in/askneelnow
• 🐦 X / Twitter: @askneelnow
• 💻 GitHub: @indranilbanerjee
• 📦 Other plugins: ContentForge · SocialForge
• 💬 Discussions: GitHub Discussions
• 🐛 Bug reports: GitHub Issues

Why this plugin exists: Most AI marketing tools generate isolated outputs that don't compose. The 12-Part Strategy Flow encodes the canonical sequence a real engagement actually needs — Stone-vs-Opinion intake, Four Core Documents, Client Validation, Two-Views Model, Decision Matrix, Growth Plan + Yearly Planner, channel fan-out, execution artefacts, creative briefs, continuous improvement loop. Once it's a plugin, every engagement looks the same, handoffs work, and quality is auditable. That's the whole product.

If DM Pro saves your team time, ⭐ star the repo — it's the single most useful thing you can do to help other marketing teams discover it. Sharing it on LinkedIn or X helps people discover the work too.

Contributing

PRs welcome — especially on compliance rules (privacy and AI law change fast), industry profiles, and channel-specific updates. See CONTRIBUTING.md for the contribution workflow, .github/PULL_REQUEST_TEMPLATE.md for the PR checklist, and TESTING-GUIDE.md for per-phase test checklists. All contributors are expected to follow the Code of Conduct. Security issues: please use Private Security Advisories per SECURITY.md — do not file public issues for vulnerabilities.

Sponsor this project

This plugin is MIT-licensed, free to use commercially, and collects no telemetry. What sponsorship pays for is the unglamorous half of keeping it accurate: platform-API updates when a vendor ships a breaking version, model-registry refreshes when a model is retired, compliance passes when regulatory guidance moves, and issue triage.

If it saves your team time, you can sponsor the work. Sponsors from $25/mo are listed in SPONSORS.md.

License

MIT — see LICENSE. Free to use commercially.

Release notes

Every release, with what changed and why: CHANGELOG.md.