Agent skill · Security

campaign-audit

Audit a brand's existing live campaigns across every active channel — paid, organic, email, social, content, SEO. Produce a current-state inventory, quick-wins backlog, and red-flags list. Use during agency onboarding or before any /campaign-plan refresh.

indranilbanerjeegithub.com/indranilbanerjeeGitHub ↗
claude-codecopilotcursorcodexcan modify filesMIT
Install
npx skills add indranilbanerjee/digital-marketing-pro --skill campaign-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 16 KB
Bundled scripts: none
Allowed tools: ReadBashGlobGrep
Path: skills/campaign-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 700
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /digital-marketing-pro:campaign-audit — Cross-Channel Current-State Audit This skill produces a single document describing **everything currently running for a brand across every channel** — what's live, what's spending, what's performing, what's leaking budget, what's quietly broken. It's the prerequisite for any informed `/digital-marketing-pro:campaign-plan`, `/digital-marketing-pro:performance-report`, or `/digital-marketing-pro:competitor-analysis` refresh. ## Context efficiency Heavy skill. **Grep before Read** any referenced file, then `Read` only matched ranges with `offset` + `limit`. List the brand's data dir (`~/.claude-marketing/brands/{slug}/`, or `$CLAUDE_PLUGIN_DATA/digital-marketing-pro/brands/{slug}/` when that env var is set) before opening files. On re-invocation mid-session, skip files already in context. Use this skill: - **During agency onboarding** (step 8 of the agency-operations workflow) — within the first week of taking over a new client, before you propose anything new. - **Before a quarterly campaign refresh** — establish the baseline you're going to argue against. - **After a brand acquisition or restructure** — when ownership of marketing changes ha

What's inside
Steps it walks through
  1. Context efficiency
  2. Why this skill exists
  3. What gets audited
  4. Process
  5. Step 0 — Prerequisites
  6. Step 1 — Confirm the active brand and audit scope
  7. Step 2 — Inventory each channel
  8. Step 3 — Score and triage
  9. Step 4 — Compose the audit document
  10. Step 5 — Update the brand's audit history
  11. Step 6 — Surface the report to the user
  12. Behaviour rules
  13. Arguments
  14. Related skills + commands
Commands it runs
Paid search
python "${CLAUDE_PLUGIN_ROOT}/scripts/performance-monitor.py" --brand "{brand}" \
Paid social
Email
Organic + SEO
python "${CLAUDE_PLUGIN_ROOT}/scripts/seo-executor.py" --brand "{brand}" --action audit-current
AEO / GEO (skip for a fast audit)
python "${CLAUDE_PLUGIN_ROOT}/scripts/ai-visibility-checker.py" --brand "{brand}" \
CRM + automation health
python "${CLAUDE_PLUGIN_ROOT}/scripts/crm-sync.py" --brand "{brand}" --action audit-workflows
More from digital-marketing-pro
All skills →
About this skill
What does the campaign-audit skill do?

Audit a brand's existing live campaigns across every active channel — paid, organic, email, social, content, SEO. Produce a current-state inventory, quick-wins backlog, and red-flags list. Use during agency onboarding or before any /campaign-plan refresh.

How do I install it?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill campaign-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From indranilbanerjee/digital-marketing-pro, a repository with 700 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going