agentleFS
Ootto-AIOotto-AI/claude-content-skills/skills/campaign-brief/SKILL.md

campaign-brief

Skill417 starsChanged 3 months agoMITView on GitHub

Use when a social campaign needs a decision-ready brief before anyone writes posts, books creators, or spends budget. Trigger phrases include "brief this launch", "turn this into a campaign plan", "what should this campaign say?", "make a social brief", and "align the team on this promotion". Do not use this for a content calendar, a single caption, or an unapproved product claim; use content-calendar for scheduling, caption-and-hashtags for a post, and positioning-audit when the core message is still unclear.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create the shared decision document that keeps a social campaign focused on one real outcome, one truthful promise, and clear channel roles.

    line 8
  2. Distinctive:

    Ask what must change, by when, and for whom.

    line 12
  3. Distinctive:

    Write the audience situation, the useful tension, the promise, the proof available, and the action requested.

    line 20
  4. Distinctive:

    Do not set a target or promise that has no measurement source or proof.

    line 28
  5. Distinctive:

    Keep one primary action; secondary actions must not compete with it.

    line 29
  6. Distinctive:

    Do not claim results, integrations, customer stories, or availability that the product team has not approved.

    line 30
  7. Distinctive:

    Use social-listening, audience-personas, and positioning-audit to supply the evidence and message before this skill.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Campaign Brief

Create the shared decision document that keeps a social campaign focused on one real outcome, one truthful promise, and clear channel roles.

1. Confirm the business decision

Ask what must change, by when, and for whom. Name one primary outcome such as qualified sign-ups, waitlist intent, event attendance, product education, or retained attention. Record the measurement source before choosing a vanity metric.

2. Establish the claim boundary

Collect the approved offer, audience evidence, product facts, proof, limitations, and required legal or brand constraints. Separate facts the team can say now from hypotheses the campaign may test. If proof is missing, make the campaign ask a question or demonstrate a workflow rather than assert an outcome.

3. Define the campaign spine

Write the audience situation, the useful tension, the promise, the proof available, and the action requested. Add the explicit non-goal so the team does not turn every campaign into a broad awareness exercise. Give each channel a role rather than copying one message everywhere.

4. Turn the brief into execution decisions

Provide message pillars, approved examples, prohibited claims, required assets, owners, timing, measurement events, and review gates. Include open questions with a named owner. The output should let a writer, creator manager, and operator make consistent choices without inventing strategy in the comments.

Hard rules

  • Do not set a target or promise that has no measurement source or proof.
  • Keep one primary action; secondary actions must not compete with it.
  • Do not claim results, integrations, customer stories, or availability that the product team has not approved.
  • Distinguish an experiment from a commitment to customers.
  • Name the audience context, not an assumed demographic stereotype.

Failure modes

FailureDo this instead
The brief is a list of deliverablesStart with the decision, audience situation, promise, proof, and action.
Every channel gets identical workGive channels complementary jobs based on their format and audience context.
Measurement happens after launchSpecify the event, owner, and reporting cadence in the brief.
Claims outrun evidenceNarrow the promise, add a demonstration, or wait for approved proof.

Where it sits

Use social-listening, audience-personas, and positioning-audit to supply the evidence and message before this skill. Use cross-platform-distribution, paid-social-brief, influencer-partnerships, and content-calendar to execute it. Use launch-retrospective once the campaign has enough evidence to learn from.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.