Systems Lab

Agent skill

campaign-brief-builder

Turn a launch, segment push, or quarterly bet into one campaign argument with the asset set, the sales handoff, and the number that judges it.

activeSelf-containedInstructions only478 words

Filed under Positioning and messaging.

From vcxcvii/pipeline-skills · 10 skill entries · 0 · pushed 2026-09-25

What it does when it runs

Turn a launch, segment push, or quarterly bet into one campaign argument with the asset set, the sales handoff, and the number that judges it. Use when the user is planning a launch or campaign, has a calendar of activities but no through-line, or says activity is up and pipeline is flat.

Automated analysis of the skill and the 0 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-brief-builder

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/vcxcvii/pipeline-skills.git /tmp/pipeline-skills
git -C /tmp/pipeline-skills sparse-checkout set "skills/campaign-brief-builder"
mkdir -p ~/.claude/skills/campaign-brief-builder
cp -R "/tmp/pipeline-skills/skills/campaign-brief-builder/." ~/.claude/skills/campaign-brief-builder/

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 ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 10 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add vcxcvii/pipeline-skills
/plugin

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 vcxcvii/pipeline-skills/blob/d284df833e7dd2f21ff15384461ea6fcd3f454c4/skills/campaign-brief-builder/SKILL.md, which is licensed MIT (repository). 478 words, 11 headings.

Campaign Brief Builder (B2B SaaS)

A campaign is one argument delivered across the places a buyer already goes. A calendar of activities that ship on the same date is not a campaign, and it is the most common reason activity rises while pipeline does not.

Setup

Ask:

  1. What is the commercial bet? A launch, a new segment, a competitive displacement, a pricing change, or a reactivation.
  2. What number should move, and from what to what, by when?
  3. Which audience, and what do they currently believe?
  4. What is already built that we can reuse?

If the answer to (2) is "awareness", stop and get a pipeline number. A campaign with no target number cannot be judged, so it will be judged on how it looked.

Build the brief

1. The one argument

A single sentence the whole campaign carries. Every asset makes this argument more specific, never a different one. Test: read the sentence to someone in sales. If they say "sure, but what does that mean for my deals", it is not specific enough yet.

2. The belief shift

What the audience believes today, what you need them to believe by the end, and the evidence that moves them. Name the evidence. Campaigns without evidence become repetition, and repetition without proof reads as noise.

3. The asset set, in order of dependency

List assets in build order, and mark each with the argument stage it serves. Cut anything that does not advance the argument, however cheap it is to make. Typical spine: one anchor asset, one landing page, one sequence, three social posts, one enablement note.

4. The sales handoff

What sales receives, when, and what they are expected to do with it. Most campaigns die here: demand arrives and nobody told the people who answer it. Specify the trigger, the owner, and the response time.

5. The measurement plan

The single number, the leading indicator that predicts it, the measurement window, and who reads the result. Also write the kill condition: what result would make you stop, and when you will check.

Output

  • The campaign argument, one sentence
  • The belief shift, with the evidence
  • The asset list in build order, with owners
  • The sales handoff, with trigger and response time
  • The measurement plan, including the kill condition
  • What this campaign will deliberately not do

Rules

  • One argument. If the brief contains two, it is two campaigns, and you should say so.
  • Never plan a channel you cannot staff for the whole window.
  • Reuse before you build. Note what already exists.
  • No em-dashes, no "integrated 360 campaign", no vanity metrics as the target.

Related skills

positioning-canvas for the claim the campaign inherits. outbound-sequence-writer and landing-page-teardown for the assets. gtm-dashboard-spec for the measurement plan.

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-brief-builder 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.