Atlas / Skills / indranilbanerjee / digital-marketing-pro

digital-marketing-proBLOCK

skills/indranilbanerjee/digital-marketing-pro

An open-source AI marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable outputs.

Verdict
BLOCK
Grade
F
Trust score
49 /100
Version
—
Hosts
8 documented
License
MIT
Stars
867
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

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.

[](CHANGELOG.md) [](LICENSE) [](https://github.com/indranilbanerjee/digital-marketing-pro/stargazers) [](tests/) [](#works-on-40-agent-harnesses-via-the-agent-skills-open-standard) [](skills/context-engine/compliance-rules.md)

Read from source at commit 1117a7b602c4OBSERVED · 2026-10-12
Advertisement
02

Install

Commands as the repository documents them. They are shown, not run.

git clone --depth=1 https://github.com/indranilbanerjee/digital-marketing-pro.git
claude plugin install digital-marketing-pro
claude plugin add /path/to/digital-marketing-pro
claude plugin add "C:\Users\yourname\Downloads\digital-marketing-pro"
claude plugin add digital-marketing-pro
npm init -y
03

Host compatibility

What the documentation claims. We have not run a compatibility test.

HostStatusNotes
claude-codementioned
claude-desktopmentioned
codexmentioned
copilotmentioned
cursormentioned
gemini-climentioned
openclawmentioned
windsurfmentioned
04

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: ab-test-plan
description: "Plan an A/B test by script: sample size per variant, days to run, stopping rules. \"how many visitors per variant\""
argument-hint: "[element-to-test]"
---

# /digital-marketing-pro:ab-test-plan

> **Script location.** If your host does not set `${CLAUDE_PLUGIN_ROOT}`, the scripts are in this plugin's `scripts/` folder, next to `skills/`. Run them with Python 3.10 or newer: `python`, or `python3` where `python` is not found (macOS, many Linux systems).

## Purpose

Dedicated A/B test planning with a structured hypothesis framework, statistical sample size calculation, variant design, and monitoring plan. Produces a complete experiment specification with statistical rigor and clear decision criteria.

## Input Required

The user must provide (or will be prompted for):

- **Element to test**: The specific page, component, or experience being tested (landing page headline, CTA button, pricing page layout, email subject line, checkout flow, form design, etc.)
- **Current conversion rate**: Baseline conversion rate for the metric being tested (or best estimate)
- **Desired minimum detectable effect (MDE)**: The smallest improvement worth detecting. **MDE is ABSOLUTE by default** — expressed in the same units as the baseline (baseline 5.0% and you want to catch a +1.0 percentage-point lift, i.e. 5.0% → 6.0% ⇒ `--mde 0.01 --mde-type absolute`). To express it as a **relative** lift instead (a 10% relative improvement on a 5% baseline = 5.5% ⇒ `--mde 0.10 --mde-type relative`), pass `--mde-type relative`. This distinction is the single most common sample-size error: the same "10%" read as absolute vs. relative changes the required sample size by roughly two orders of magnitude (~200×) at a 5% baseline. Always confirm which the user means.
- **Daily traffic or impressions**: Average daily visitors or impressions to the test page or element
- **Significance level**: Desired confidence level, default 95% (alpha = 0.05)
- **Statistical power**: Desired power, default 80% (beta = 0.20)
- **Number of variants**: How many variants to test (default 1 treatment + 1 control; more for multivariate)
- **Business context**: What prompted the test idea (analytics data, user feedback, competitive analysis, heuristic audit, stakeholder request)

## Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply voice, compliance, industry context. Check `guidelines/_manifest.json` for restrictions, messaging, channel styles, voice-and-tone rules, and templates. If a template matching this command exists in `~/.claude-marketing/brands/{slug}/templates/`, apply its format. If no brand exists, prompt for `/digital-marketing-pro:brand-setup` or proceed with defaults.
2. **Check campaign history**: Run `python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns` to review past test results and avoid re-testing already-validated hypotheses.
3. **Run sample size calculator**: Execute the calculator with the baseline rate, MDE, MDE type, significance, and power. The `--mde-type` flag defaults to `absolute` — always confirm with the user which interpretation they mean before computing (the two differ by roughly two orders of magnitude, ~200×, at a 5% baseline):
   ```bash
   # Absolute MDE — detect a 1.0 percentage-point lift on a 5% baseline (5.0% → 6.0%)
   python "${CLAUDE_PLUGIN_ROOT}/scripts/sample-size-calculator.py" --baseline-rate 0.05 --mde 0.01 --mde-type absolute --significance 0.95 --power 0.80

   # Relative MDE — detect a 10% relative lift on a 5% baseline (5.0% → 5.5%)
   python "${CLAUDE_PLUGIN_ROOT}/scripts/sample-size-calculator.py" --baseline-rate 0.05 --mde 0.10 --mde-type relative --significance 0.95 --power 0.80
   ```
   This determines the required sample size per variant. Later, when the test has run, evaluate the result with `python "${CLAUDE_PLUGIN_ROOT}/scripts/significance-tester.py" --control-visitors {n} --control-conversions {n} --variant-visitors {n} --variant-conversions {n} --confidence 0.95`.
4. **Build hypothesis statement**: Structure the hypothesis in the format: "If [specific change], then [primary metric] will [direction and magnitude] because [rationale grounded in data, user research, or established UX principle]."
5. **Design test variants**: Define the control (current experience) and one or more treatment variants. Specify exactly what changes in each variant -- copy, layout, color, imagery, flow, or functionality. For multivariate tests, define the variable matrix and interaction effects to watch.
6. **Define primary and secondary metrics**: Identify the primary success metric (the one that determines the winner) and secondary metrics to monitor for unintended effects (e.g., testing CTA click rate as primary, but watching bounce rate, time on page, and downstream conversion as secondary guardrails).
7. **Calculate test duration**: Based on sample size requirements and daily traffic, estimate the number of days needed. Ensure the duration spans at least one full business cycle (7 days minimum) to account for day-of-week variation. Flag if duration exceeds 8 weeks (validity risk).
8. **Create monitoring plan**: Define interim checkpoints for technical QA (not statistical peeking), sample ratio mismatch (SRM) detection, and guardrail metric alerts that would trigger early test stoppage for data quality or user experience reasons.
9. **Define stopping rules and decision criteria**: Specify when to call the test (sample size reached + significance threshold met), when to stop early (guardrail violations, SRM detected, implementation bugs), and the protocol for inconclusive results (extend, redesign, or implement based on directional signal).
10. **Assess traffic feasibility**: Verify that the daily traffic can reach the required sample size within a reasonable timeframe (under 8 weeks). If traff
05

Trust audit

BLOCKgrade F · trust 49/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeWARN
L2Instruction surface (what it tells the agent)FAIL
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (2 observation(s))
Network
declared (7 observation(s))
Shell
declared (1 observation(s))
Dependencies
pinned
Secrets in source
found

Findings (25)

CRITICALPrompt injection · prompt.transfer_instruction · CWE-94, CWE-1427
skills/c2pa-metadata/SKILL.md:23
- **Content Credentials 2.3** (released 9 February 2026 — [launch post](https://c2pa.org/the-c2pa-launches-content-credentials-2-3-and-celebrates-5-years-of-impact-across-the-digital-ecosystem/)) adde
Why it matters. an instruction to move sensitive data to an outside destination
Fix. remove; a skill never needs the user's secrets off the machine
HIGHPrompt injection · prompt.zero_width · CWE-94, CWE-1427
README.md:1
# Digital Marketing Pro
Why it matters. invisible characters in instruction text
Fix. strip non-printing characters
MEDIUMCode injection · code.dynamic_import · CWE-78, CWE-94, CWE-95
scripts/dm-status.py:364
__import__(import_name)
MEDIUMNetwork egress · net.beacon_words · CWE-200, CWE-319
scripts/ai-tell-scan.py:97
"realm", "beacon", "cacophony", "testament", "pivotal", "landscape",
MEDIUMHard-coded secrets · secret.slack · CWE-798, CWE-321
tests/test_approval_gate.py:40
TOKEN = "xoxb-test-token-123"
MEDIUMHard-coded secrets · secret.slack · CWE-798, CWE-321
tests/test_executor_delivery.py:167
ENV = {"SLACK_BOT_TOKEN": "xoxb-test-token-123"}
MEDIUMHard-coded secrets · secret.slack · CWE-798, CWE-321
tests/test_executor_exit_codes.py:31
TOKEN = "xoxb-test-token-123"
MEDIUMHard-coded secrets · secret.slack · CWE-798, CWE-321
tests/test_text_encodings.py:128
SLACK_BOT_TOKEN="xoxb-test-token-123", PYTHONIOENCODING="utf-8")
LOWInventory / provenance · inv.hidden_file · CWE-1104
.mcp.json.connectors-reference
.mcp.json.connectors-reference
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWInventory / provenance · inv.hidden_file · CWE-1104
.mcp.json.example
.mcp.json.example
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWInsecure crypto · crypto.weak_hash · CWE-327, CWE-338
scripts/audience-simulator.py:79
return int(hashlib.md5(raw.encode()).hexdigest()[:8], 16)
LOWInsecure crypto · crypto.weak_hash · CWE-327, CWE-338
scripts/campaign-health-monitor.py:511
correction_id = hashlib.md5(f"{campaign_id}-{ts}".encode()).hexdigest()[:12]
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
tests/test_manifest_paths.py:95
copilot = {"skills": "../../skills/", "mcpServers": "../../.mcp.json"}
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
tests/test_manifest_paths.py:99
[".github/plugin/plugin.json points at ../../.mcp.json, which does not ship"])
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
tests/test_manifest_paths.py:102
self.assertEqual(resolve(".github/plugin/plugin.json", "../../skills/"), "skills")
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
tests/test_path_containment.py:45
bad = ["../x", "../../etc/passwd", "..\\x", "a/b", "a\\b", "/etc/passwd", "C:\\Windows", "C:",
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
tests/test_path_containment.py:75
for raw in ("../../outside", str(tmp / "outside"), "..\\..\\outside"):
LOWNetwork egress · net.metadata_ip · CWE-200, CWE-319
tests/test_url_guard.py:36
"meta.example": "169.254.169.254",
Why it matters. cloud metadata endpoint: the classic SSRF credential grab
LOWNetwork egress · net.metadata_ip · CWE-200, CWE-319
tests/test_url_guard.py:65
"http://169.254.169.254/": False,
Why it matters. cloud metadata endpoint: the classic SSRF credential grab
LOWNetwork egress · net.metadata_ip · CWE-200, CWE-319
tests/test_url_guard.py:118
for url in ("http://lan.example/", "file:///etc/hosts", "http://169.254.169.254/"):
Why it matters. cloud metadata endpoint: the classic SSRF credential grab
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
tests/test_executor_delivery.py:90
return {"method": "POST", "url": f"http://127.0.0.1:{port}/api/chat.postMessage",
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
tests/test_executor_delivery.py:185
out["url"] = f"http://127.0.0.1:{port}/api/chat.postMessage"
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
tests/test_url_guard.py:64
"http://127.0.0.1/": False,
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
tests/test_url_guard.py:65
"http://169.254.169.254/": False,
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
tests/test_url_guard.py:118
for url in ("http://lan.example/", "file:///etc/hosts", "http://169.254.169.254/"):

Gates applied: critical_finding, no_behavioural_pass, undeclared_transfer.

Audited 2026-10-12 · audit v0.4.1 · source sha 1117a7b602c4full audit observations/trust-audit/skill/indranilbanerjee__digital-marketing-pro.json · Report an issue / request a re-scan
06

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-121117a7b602c4BLOCKF49first audit
07

Questions

What does the digital-marketing-pro skill do?

An open-source AI marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable outputs.

Is digital-marketing-pro safe to install?

No — not without reading the findings first. The audit graded it F (49/100) and found 2 critical or high issues in the source. Each one is listed on this page with the file and line it is on.

What can digital-marketing-pro access on my machine?

The audit observed that it reaches the network, runs shell commands and reads or writes files. Each of those is consistent with what it says it does. Secrets in the source: found — see the findings.

Which assistants does digital-marketing-pro work with?

Its documentation mentions claude-code, claude-desktop, codex, copilot, cursor, gemini-cli, openclaw and windsurf. That is what the text claims, not a compatibility test we ran.

How current is this page?

The grade is for one exact copy of the source (1117a7b602c4), read on 2026-10-12. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement