mcpbeat

Campaign Plan

indranilbanerjee/campaign-plan

Build multi-channel campaign plans. Use when: objectives, audience targeting, channel mix, budget, timeline, KPIs.

2k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
694
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill campaign-plan

The instruction itself

6 sections, as written by the author

/digital-marketing-pro:campaign-plan

Purpose

Generate a comprehensive multi-channel campaign plan ready for execution. Covers strategic objectives, audience segmentation, channel selection, budget distribution, phased timeline, and measurable KPIs.

Input Required

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

  • Campaign goal: What the campaign should achieve (awareness, leads, sales, retention, etc.)
  • Product/service: What is being promoted
  • Target audience: Who the campaign is for (or use existing brand personas)
  • Budget: Total available budget or budget range
  • Timeline: Campaign duration or key dates (launch, event, season)
  • Constraints: Any channel restrictions, compliance requirements, or creative limitations

Process

  • Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
  • Load shared planning references (don't re-derive them): Consume the campaign-orchestrator reference docs rather than duplicating their frameworks — skills/campaign-orchestrator/campaign-planning.md (planning framework), skills/campaign-orchestrator/channel-strategy.md (channel selection), skills/campaign-orchestrator/budget-allocation.md (budget-split heuristics), skills/campaign-orchestrator/utm-tracking.md (UTM naming conventions), and skills/campaign-orchestrator/abm-strategy.md (ABM). This skill produces the plan document; /digital-marketing-pro:campaign-orchestrator runs the broader multi-agent orchestration on top of the same references.
  • Clarify campaign objective and classify as awareness, consideration, or conversion
  • Define primary and secondary audience segments with targeting parameters
  • Recommend channel mix based on audience behavior, budget, and objective
  • Allocate budget across channels using expected CPM/CPC benchmarks for the industry
  • Build a phased timeline: pre-launch, launch, sustain, optimize, wrap-up
  • Define KPIs per channel and overall campaign success metrics
  • Identify dependencies, risks, and contingency actions

10. Output the full plan in a structured, actionable format

Output

A structured campaign plan document containing:

  • Campaign overview and SMART objectives
  • Audience segments with targeting criteria
  • Channel strategy with rationale for each channel
  • Budget allocation table with expected reach/cost estimates
  • Phased timeline with milestones and deliverables
  • KPI dashboard framework with targets and measurement approach
  • Risk register with mitigation strategies

Agents Used

  • marketing-strategist — Campaign architecture, audience strategy, objective setting
  • media-buyer — Channel selection, budget allocation, performance benchmarks

How to use it

Copy the folder

Take indranilbanerjee/campaign-plan from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.