agentleFS
AirMileAirMile/claude-config/skills/marketing-content/SKILL.md

marketing-content

Skill0 starsChanged 4 months agoMITView on GitHub

Generate marketing copy variants per format. Use with /marketing-content.

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, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Search for .project/thinking/*-marketing-research.md.

    line 24
  2. Distinctive:

    If not found: ask for a free-text description of the topic and target audience.

    line 31
  3. Distinctive:

    Use the selected tone as a style constraint in PHASE 2: every variant must consistently reflect the selected tone, even if the trajectory …

    line 71
  4. Distinctive:

    No generic text allowed. If a variant is not traceable to a concrete signal or one of the angles, do not write it.

    line 121
  5. Very specific:

    NEVER blockquote syntax (>) — unreadable background in dark terminals

    line 152
  6. Distinctive:

    NEVER backticks for emphasis on regular words — use bold

    line 153
  7. Distinctive:

    Language: Follow the Language Policy in CLAUDE.md.

    line 156

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

Turn research signals into concrete text variants per format and platform. Each variant is traceable to a specific signal — no generic output.

Trigger: /marketing-content or /marketing-content [topic]

Second step in the marketing pipeline: /marketing-research → /marketing-content → /marketing-screenshots

PHASE 0: Input & Context

Research auto-detect:

Search for .project/thinking/*-marketing-research.md. If found:

  • Load the SCOPE ANCHORS section (topic, target audience, channels, trajectory labels)
  • Load the Signal Analysis section (platform temperatures, sentiment conflict)
  • Load the Audience Language section (exact words and frames used by the audience)
  • Confirm to the user which research file was loaded

If not found: ask for a free-text description of the topic and target audience.

Format selection via AskUserQuestion:

header: "Format"
question: "What type of content do you want to generate?"
options:
  - label: "Social post (Recommended)", description: "Twitter/X, LinkedIn, Instagram"
  - label: "Email subject line", description: "3-5 variants for A/B test"
  - label: "Ad headline", description: "Google/Meta — max 30 characters"
  - label: "Landing page section", description: "Hero headline + subline"
multiSelect: true

Platform selection (only if Social post chosen) via AskUserQuestion:

header: "Platform"
question: "Which platform?"
options:
  - label: "Twitter/X (Recommended)", description: "Max 280 characters, direct tone"
  - label: "LinkedIn", description: "Professional, more context allowed"
  - label: "Instagram", description: "Visual, caption + hashtags"
multiSelect: true

Tone/voice selection via AskUserQuestion:

header: "Tone"
question: "Which tone fits this brand or campaign?"
options:
  - label: "Informative (Recommended)", description: "Clear, factual, educational — builds trust"
  - label: "Urgent", description: "Action-driven, time-bound — pushes to decision"
  - label: "Provocative", description: "Sharp, challenging, bold — captures attention"
  - label: "Inspiring", description: "Motivating, aspirational — connects emotionally"
multiSelect: false

Use the selected tone as a style constraint in PHASE 2: every variant must consistently reflect the selected tone, even if the trajectory label suggests a different direction.

PHASE 1: Distill Messaging Angles

Map the strongest research signals to messaging frames:

SignalMessaging frame
acute_riseUrgency — "this is the moment"
comebackContrast — "it's back, and different now"
plateauDifferentiation — "what makes you different from mainstream"
zombieCounter-indicator — avoid, or use as contrast
sentiment-conflictProvocation — "not everyone agrees about..."
audience languageMirror — use their exact words back

Select the 3 strongest angles based on available signals. If no research is available: use Competitor Differentiation, Audience Mirror, and Problem/Solution as default angles.

Present:

MESSAGING ANGLES

1. {angle name} — {frame} — based on: {signal + source}
2. {angle name} — {frame} — based on: {signal + source}
3. {angle name} — {frame} — based on: {signal + source}

PHASE 2: Generate Variants

Per chosen format: generate 3-5 variants, spread across the messaging angles.

Length and tone rules per format:

FormatLengthTone
Twitter/X postMax 280 charsDirect, no formatting
LinkedIn post150-300 charsProfessional, opener allowed
Instagram caption100-150 + tagsVisually supportive, emojis ok
Email subject lineMax 50 charsCuriosity or urgency
Ad headlineMax 30 charsAction-driven, single core message
Landing page hero6-10 wordsPromise or problem statement
Landing page subline15-25 wordsExplanation of the promise

Each variant contains:

  • The text (length rule respected)
  • Angle: which messaging frame
  • Signal: which research signal justifies this
  • Trajectory: acute_rise / plateau / comeback / zombie (if applicable)

No generic text allowed. If a variant is not traceable to a concrete signal or one of the angles, do not write it.

Present per format:

{FORMAT} — {platform}

Variant 1:
"{text}"
Angle: {frame} | Signal: {signal} | Trajectory: {label}

Variant 2:
...

PHASE 3: Save

Save to .project/thinking/{topic}-marketing-content.md.

Show next steps:

Next steps:
- /marketing-screenshots — screenshots + visuals for launch
- /marketing-research — new research round for another topic

Guidelines

Formatting:

  • NEVER blockquote syntax (>) — unreadable background in dark terminals
  • NEVER backticks for emphasis on regular words — use bold
  • Backticks only for code, file paths, and command references

Language: Follow the Language Policy in CLAUDE.md.

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.