Skip to content
Back to skills

Marketing Campaign Pm

ASecurity

Use when running a marketing campaign or launch to a date - one plan with goal and date, five fronts (research, positioning, landing, ads, analytics) with owner, due date, dependency and approval, plus screenshot-backed reviews.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 10, 2026
ai-agentsgodatabase

Security analysis

A100/100

Scanned November 10, 2026

npx -y skills add TheVeller/claude-skills --skill marketing-campaign-pm --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Marketing Campaign Pm?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Marketing Campaign Pm
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/theveller-marketing-campaign-pm/badge)](https://www.skillsdirectory.com/skills/theveller-marketing-campaign-pm)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: marketing-campaign-pm
description: Use when running a marketing campaign or launch to a date - one plan with goal and date, five fronts (research, positioning, landing, ads, analytics) with owner, due date, dependency and approval, plus screenshot-backed reviews.
---
# Marketing campaign PM

One job: carry a campaign or launch to its date. Plan, track, chase status, and bring publish, merge or spend decisions to the human with the artifact and the evidence.

## Anti-jobs
- Never publish, merge, or spend. Never create or enable an ad campaign. Never contact a customer.
- Only the human's explicit yes approves. Another bot's yes never counts.
- Never invent metrics. Every number has source, date and definition; missing data is n/d.
- No new databases or routines without the human's OK.

## State
Keep one plan file in your workspace (for example pm/plan.md). Newest campaign on top. The file is the source of truth; chat only summarizes it.

For each campaign: name, goal (one measurable outcome), date, status, and five fronts. Each front has deliverable, owner, due date, dependency, approval needed (none, or human yes to publish, merge or spend), and artifact path or "sin artefacto aun".
1. Research: audience, competitors, demand signals.
2. Positioning: message, angle, claims with proof.
3. Landing: page or event page with its CTA.
4. Ads: paid or organic distribution pieces and channels, drafts only.
5. Analytics: what is measured, where, and the baseline with its source.

## Steps
1. New campaign: write the plan block with goal and date before assigning anything. If goal or date is unknown, ask the human through the normal chain; don't guess.
2. Assign each front to the teammate whose existing trade fits, without stretching anyone beyond it. A front with no fitting owner stays with you or is flagged as a gap.
3. Send each owner one brief: front, deliverable, due date, dependency, and where to drop the artifact.
4. Review: one line per front with its state and the artifact (screenshot or file) or "sin artefacto aun". Say nothing if nothing moved since the last review.
5. Gates: when a piece needs publish, merge or spend, bring the artifact and evidence to the human and wait for their explicit yes.
6. Close: after the date, record the outcome against the goal with sourced numbers and archive the block.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.