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
- amirbiron/claude-skillstheir own version, first seen Oct 11, 2026
- 0chandansharma/claude-skillstheir own version, first seen May 22, 2026
- minamagdyyyy/agentic-marketingtheir own version, first seen Mar 13, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- minamagdyyyy/agentic-marketing★ 5same name
- 0chandansharma/claude-skills★ 0same name
- amirbiron/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- content-rewriteSkill
- content-writeSkill
- core-auditSkill
- core-bootstrapSkill
- core-commitSkill
- core-explainSkill
- core-finalizeSkill
- core-orchestrateSkill
- core-pullSkill
- core-setupSkill
- core-updateSkill
- design-convertSkill
- design-shipSkill
- design-tokensSkill
- dev-inspectSkill
- dev-learnSkill
- dev-manualSkill
- dev-optimizeSkill
- dev-securitySkill
- dev-shipSkill
- dev-tweakSkill
- game-debugSkill
- game-optimizeSkill
- game-shipSkill
- game-tweakSkill
- marketing-researchSkill
- marketing-screenshotsSkill
- project-addSkill
- project-appSkill
- project-memorySkill
- project-planSkill
- project-removeSkill
- project-researchSkill
- project-seedSkill
- project-syncSkill
- project-todoSkill
- project-tunnelSkill
- team-issuesSkill
- team-outsourceSkill
- team-reviewSkill
- team-verifySkill
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
- Very specific: line 24
Search for .project/thinking/*-marketing-research.md.
- Distinctive: line 31
If not found: ask for a free-text description of the topic and target audience.
- Distinctive: line 71
Use the selected tone as a style constraint in PHASE 2: every variant must consistently reflect the selected tone, even if the trajectory …
- Distinctive: line 121
No generic text allowed. If a variant is not traceable to a concrete signal or one of the angles, do not write it.
- Very specific: line 152
NEVER blockquote syntax (>) — unreadable background in dark terminals
- Distinctive: line 153
NEVER backticks for emphasis on regular words — use bold
- Distinctive: line 156
Language: Follow the Language Policy in CLAUDE.md.
≈ “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.
Files
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: truePlatform 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: trueTone/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: falseUse 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:
| Signal | Messaging frame |
acute_rise | Urgency — "this is the moment" |
comeback | Contrast — "it's back, and different now" |
plateau | Differentiation — "what makes you different from mainstream" |
zombie | Counter-indicator — avoid, or use as contrast |
| sentiment-conflict | Provocation — "not everyone agrees about..." |
| audience language | Mirror — 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:
| Format | Length | Tone |
| Twitter/X post | Max 280 chars | Direct, no formatting |
| LinkedIn post | 150-300 chars | Professional, opener allowed |
| Instagram caption | 100-150 + tags | Visually supportive, emojis ok |
| Email subject line | Max 50 chars | Curiosity or urgency |
| Ad headline | Max 30 chars | Action-driven, single core message |
| Landing page hero | 6-10 words | Promise or problem statement |
| Landing page subline | 15-25 words | Explanation 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 topicGuidelines
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.
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
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.

