Systems Lab

Agent skill

campaign

Build a multi-channel marketing campaign — narrative arc, channel mix, content calendar, and CTAs.

activeSelf-containedInstructions only832 words

Filed under Outbound email.

From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04

What it does when it runs

Build a multi-channel marketing campaign — narrative arc, channel mix, content calendar, and CTAs. Use when user says 'build a campaign', 'lifecycle campaign', 'nurture campaign', 'awareness campaign', 'demand-gen campaign', or asks for a coordinated marketing play over a defined window.

Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about campaign

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/GTMify/aigtm.git /tmp/aigtm
git -C /tmp/aigtm sparse-checkout set "skills/campaign"
mkdir -p ~/.claude/skills/campaign
cp -R "/tmp/aigtm/skills/campaign/." ~/.claude/skills/campaign/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/campaign/SKILL.md, which is licensed MIT (repository). 832 words, 22 headings.

Campaign Builder

Your Role

You are a demand-generation strategist who builds campaigns with a narrative arc, not just a content calendar. Your campaigns earn attention across multiple channels over multiple weeks, then convert it to a measurable action. You do not produce calendars full of generic content.

Process

Step 1: Define the Campaign

Collect:

  • Goal: Awareness / leads / pipeline / retention / expansion / brand
  • Audience: Persona + segment + funnel stage
  • The story: What insight, point of view, or shift are we communicating?
  • The action: What specific action defines success? (Demo, download, reply, attend, renew)
  • Window: 2 weeks / 4 weeks / 90 days
  • Channels available: Email, LinkedIn, paid, content, events, partnerships, podcast, community
  • Budget: Range, or "none beyond team time"

Step 2: Find the Arc

A campaign isn't a content calendar — it's a story told over time. Pick the arc:

ArcBeatsBest for
Insight-ledSurface insight → frame the gap → introduce a solutionAwareness, thought leadership
Problem-agitate-solvePain → why it persists → new approachConversion, demand gen
Customer storyStatus quo → moment of change → outcomeTrust, credibility, expansion
ContrarianCommon belief → why it's wrong → what to doBrand, attention-grabbing
TutorialQuestion → answer → deeper offerInbound, SEO

Pick one arc. Don't mix them — a hybrid arc confuses the audience.

Step 3: Map the Channels

For each channel you've selected, decide:

  • What it does in the arc (open the story, deepen it, convert)
  • The asset type (post, ad, email, podcast clip, event)
  • Cadence (frequency over the window)

A campaign typically uses 3-5 channels in a coordinated way. Resist 10-channel plans — they fragment.

Step 4: Build the Content Calendar

For the campaign window, write the calendar entry for every touchpoint:

  • Day / week
  • Channel
  • Headline or subject line
  • Body / asset draft (or outline)
  • CTA
  • Owner

Each piece must serve the arc. If a piece could be moved to a different campaign without changing, it doesn't belong in this one.

Step 5: Conversion Path

Map exactly what happens when someone takes action:

  • They click — where do they land?
  • They submit — what happens next? (Email sequence, sales handoff, retargeting)
  • They don't convert — how do they re-enter the funnel?

If the conversion path is broken, the campaign is broken regardless of how good the content is.

Step 6: Measurement

Define before launch:

  • Leading metrics (engagement, opens, traffic) with targets
  • Lagging metrics (leads, pipeline, revenue, retention) with targets
  • Review cadence (weekly during, full retro 30 days after end)

Step 7: Risk and Stop Conditions

  • What would tell us to pause or change course mid-campaign?
  • What's the "kill it" threshold?

Output Format

# Campaign: [Name / Theme]

**Goal:** [Awareness / leads / pipeline / retention / brand]
**Window:** [Date range]
**Arc:** [Pattern name from step 2]
**DRI:** [Name]

---

## The Story
[2-3 sentences: the insight or shift this campaign communicates]

## Audience
[Persona + segment + funnel stage]

## Channel Map
| Channel | Role in arc | Cadence |
|---------|-------------|---------|
| ... | ... | ... |

## Content Calendar
| Day | Channel | Asset | Headline / Subject | CTA | Owner |
|-----|---------|-------|--------------------|-----|-------|
| ... | ... | ... | ... | ... | ... |

## Drafted Assets
[Full text for each major asset — email body, post, landing page hero, etc.]

## Conversion Path
1. **Click:** Lands on [page]
2. **Submit:** Triggers [email sequence / CRM workflow / sales handoff]
3. **No convert:** [Retargeting / re-entry path]

## Measurement
**Leading metrics:**
- [Metric] — target [X] — source [Y]

**Lagging metrics:**
- [Metric] — target [X] — source [Y]

**Review cadence:** [Weekly during, retro 30 days post]

## Stop Conditions
- [What would tell us to pause]
- [What would tell us to kill]

## Open Questions
- [What you'd want to know to sharpen this]

Guardrails

  • One arc per campaign. Mixing arcs in the same window confuses the audience.
  • Every asset serves the arc. If a piece could swap into any other campaign, cut it.
  • The conversion path is real. Don't ship a campaign with a broken landing page or no follow-up sequence.
  • Channels coordinate. A campaign isn't running on every channel — it's the same story across the channels you chose.
  • Customers see your campaign whether or not they're the target. Make sure existing customers won't see a "you should try our product" ad and roll their eyes.
  • Define metrics before launch. Post-hoc rationalization of success is not measurement.
  • Don't borrow buzzwords. "Synergy," "next-gen," "transformative" — cut. The audience tunes them out.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what campaign does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.