agentleFS
Infinite-Labs-AIInfinite-Labs-AI/infinite-skills/skills/marketing-brief/SKILL.md

marketing-brief

Skill43 starsChanged 5 months agoMITView on GitHub

Use when turning a product, feature, client, or rough idea into a practical marketing brief: audience, problem, promise, proof, channels, risks, and next actions.

2 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 a short brief that helps a founder decide who to target, what to say, and what to try next.

    line 8
  2. Distinctive:

    Look for existing context before asking questions: README files, website copy, pitch decks, product docs, analytics notes, CRM exports, …

    line 12
  3. Distinctive:

    If the brief lacks enough context, ask only for the missing decision-critical inputs:

    line 14
  4. Distinctive:

    Write in plain operator language.

    line 24
  5. Distinctive:

    Prefer one sharp segment over a broad persona map.

    line 43
  6. Distinctive:

    Keep claims within the available proof.

    line 44

≈ “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

Marketing Brief

Create a short brief that helps a founder decide who to target, what to say, and what to try next.

First Pass

Look for existing context before asking questions: README files, website copy, pitch decks, product docs, analytics notes, CRM exports, customer interviews, support tickets, and prior campaign material.

If the brief lacks enough context, ask only for the missing decision-critical inputs:

  • Product: what it does, who uses it, and the moment they need it.
  • Customer: role, company type, pain, urgency, buying trigger.
  • Market: alternatives, status quo, competitors, category language.
  • Proof: customer names, usage, revenue, testimonials, screenshots, demos, case data.
  • Constraint: budget, deadline, geography, compliance, founder preference, channels to avoid.

Build The Brief

Write in plain operator language. Avoid founder mythology unless it changes positioning or channel choice.

Cover these sections:

  • One-line product read: what this is, for whom, and why now.
  • First reachable pocket: the smallest reachable buyer or user group with a real trigger.
  • Job and pain: what they are trying to get done and what currently makes it expensive, slow, risky, embarrassing, or annoying.
  • Alternatives: direct competitors, workarounds, spreadsheets, agencies, internal teams, doing nothing.
  • Positioning angle: the narrow angle where this product can win first.
  • Promise: the believable outcome the market should remember.
  • Proof inventory: facts that can be shown, quoted, measured, or demonstrated.
  • Objections: reasons a serious buyer would hesitate.
  • Channel evidence: where this customer already looks, complains, compares, or buys.
  • Claim risk: claims that are attractive but weakly supported.
  • Fastest disproof: the quickest test that could show the read is wrong.
  • This-week validation: actions that can be executed without a full campaign.

Decision Rules

  • Prefer one sharp segment over a broad persona map.
  • Keep claims within the available proof.
  • Separate facts from assumptions.
  • Name the weak points instead of smoothing them over.
  • Turn vague words into observable behavior: not "busy teams," but "ops leads compiling weekly reports from five tools."

Output

Use this structure:

Marketing Brief: [product/company]
Read: [one sentence]

First reachable pocket:
[specific segment]

Market tension:
[what changed, what hurts, why existing options disappoint]

Positioning angle:
[where to enter and why it is credible]

Message:
Promise:
Proof:
Objections:

Channel bets:
1. [channel] - [why it fits]
2. [channel] - [why it fits]
3. [channel] - [why it fits]

Claim risk:
- [claim] - [why risky]

Fastest disproof:
[test]

This week:
1. [action]
2. [action]
3. [action]

Open assumptions:
- [assumption to validate]

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.