launch-campaign
Orchestrate the full multi-channel launch of an approved campaign plan — pre-launch checklist, asset readiness gate, channel-by-channel activation, CRM campaign record creation, kickoff comms, day-1 monitor setup. Broader than /launch-ad-campaign (which is paid-ads only).
npx skills add indranilbanerjee/digital-marketing-pro --skill launch-campaign --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /digital-marketing-pro:launch-campaign — Multi-Channel Campaign Launch Orchestrator This skill takes an **approved** campaign plan (from `/digital-marketing-pro:campaign-plan`) and walks it through every step required to go live: pre-launch gates, channel-by-channel activation, CRM record creation, kickoff comms to the team, and day-1 monitoring setup. It complements — and is broader than — `/digital-marketing-pro:launch-ad-campaign`, which handles only paid-ads activation on Google / Meta / LinkedIn / TikTok. Use this skill **once** per campaign, after the campaign plan is approved and all creative + landing pages + email sequences are signed off. Not for paid-ads alone — for the full multi-channel launch (paid + organic + email + content + CRM + PR). ## Why this skill exists A campaign plan is a document. A campaign launch is twenty separate platform actions in the correct order with the correct dependencies. Without an orchestrator, agencies miss steps — landing page goes live without the analytics tag wired, email automation gets enabled before the source list is GDPR-clean, paid ads get activated before the LP is indexed, the team finds out the campaign launched by seeing th
- Why this skill exists
- What this skill does NOT do
- Process
- Step 0 — Prerequisites (BLOCKER gates)
- Step 1 — Load the campaign plan
- Step 2 — Dry-run preview
- Step 3 — Execute in dependency order
- Step 4 — Write the launch record
- Step 5 — Confirm to the user
- Behaviour rules
- Arguments
- Related skills + commands
CRM Campaign object
python "${CLAUDE_PLUGIN_ROOT}/scripts/crm-sync.py" --brand "{brand}" \
Landing page check
curl -sS -o /dev/null -w "%{http_code}" "{landing_url}"
Email automation enable (idempotent — skips if already enabled)
python "${CLAUDE_PLUGIN_ROOT}/scripts/execution-tracker.py" --brand "{brand}" \
Paid-ads activation (delegates to launch-ad-campaign for the paid-only subset)
Organic social scheduling
Influencer notification
PR sendWhat does the launch-campaign skill do?
Orchestrate the full multi-channel launch of an approved campaign plan — pre-launch checklist, asset readiness gate, channel-by-channel activation, CRM campaign record creation, kickoff comms, day-1 monitor setup. Broader than /launch-ad-campaign (which is paid-ads only).
How do I install it?
Run `npx skills add indranilbanerjee/digital-marketing-pro --skill launch-campaign --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.