Plan a content strategy, decide what content to create

by coreyhaines31 · MIT license · ★ 51,120 on GitHub · updated Sep 5

Content strategy cover

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover.

---
name: content-strategy
description: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.
metadata:
  version: 2.1.1
---

# Content Strategy

You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.

## Before Planning

**Check for product marketing context first:**
If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

Overview

You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.

Manual install (npx, ZIP)
Claude Codenpx skills add coreyhaines31/marketingskills --skill content-strategy -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/coreyhaines31/marketingskills/tar.gz/5b2c0007766c \ | tar -xz -C ~/.claude/skills --strip-components=2 marketingskills-5b2c0007766c/skills/content-strategy
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/aee59d8df6e95d8f3a3d/content-strategy.zip" -OutFile "$env:TEMP\content-strategy.zip"; Expand-Archive "$env:TEMP\content-strategy.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md18.3 KB
  • evals/1 file · 10.0 KB
  • references/2 files · 13.7 KB
Read the files here
coreyhaines31/5b2c0004 files
SKILL.md
Show the full text440 lines

Content Strategy

You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.

Before Planning

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Business Context
  • What does the company do?
  • Who is the ideal customer?
  • What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)
  • What problems does your product solve?
2. Customer Research
  • What questions do customers ask before buying?
  • What objections come up in sales calls?
  • What topics appear repeatedly in support tickets?
  • What language do customers use to describe their problems?
3. Current State
  • Do you have existing content? What's working?
  • What resources do you have? (writers, budget, time)
  • What content formats can you produce? (written, video, audio)
4. Competitive Landscape
  • Who are your main competitors?
  • What content gaps exist in your market?

Treat Content Like a Product

Every piece is its own launch. Content isn't overhead—it's brand surface area: each published piece is a new entry point where a stranger can discover you, and hundreds of pieces compound into hundreds of doorways working 24/7. Plan, ship, and promote each piece with the same intent you'd bring to a product release. A post that's written and forgotten has almost no surface area; a post that's distributed (see Create Once, Distribute Twice below) multiplies it.

This section covers the searchable/shareable lens, then the execution and prioritization layer: which pieces to make (scoring), how the calendar splits, and per-format discipline.

Searchable vs Shareable

Every piece of content must be searchable, shareable, or both. Prioritize in that order—search traffic is the foundation.

Searchable content captures existing demand. Optimized for people actively looking for answers.

Shareable content creates demand. Spreads ideas and gets people talking.

When Writing Searchable Content
  • Target a specific keyword or question
  • Match search intent exactly—answer what the searcher wants
  • Use clear titles that match search queries
  • Structure with headings that mirror search patterns
  • Place keywords in title, headings, first paragraph, URL
  • Provide comprehensive coverage (don't leave questions unanswered)
  • Include data, examples, and links to authoritative sources
  • Optimize for AI/LLM discovery: clear positioning, structured content, brand consistency across the web
When Writing Shareable Content
  • Lead with a novel insight, original data, or counterintuitive take
  • Challenge conventional wisdom with well-reasoned arguments
  • Tell stories that make people feel something
  • Create content people want to share to look smart or help others
  • Connect to current trends or emerging problems
  • Share vulnerable, honest experiences others can learn from

Content Types

Searchable Content Types

Use-Case Content Formula: [persona] + [use-case]. Targets long-tail keywords.

  • "Project management for designers"
  • "Task tracking for developers"
  • "Client collaboration for freelancers"

Hub and Spoke Hub = comprehensive overview. Spokes = related subtopics.

/topic (hub)
├── /topic/subtopic-1 (spoke)
├── /topic/subtopic-2 (spoke)
└── /topic/subtopic-3 (spoke)

Create hub first, then build spokes. Interlink strategically.

Note: Most content works fine under /blog. Only use dedicated hub/spoke URL structures for major topics with layered depth (e.g., Atlassian's /agile guide). For typical blog posts, /blog/post-title is sufficient.

Template Libraries High-intent keywords + product adoption.

  • Target searches like "marketing plan template"
  • Provide immediate standalone value
  • Show how product enhances the template
Shareable Content Types

Thought Leadership

  • Articulate concepts everyone feels but hasn't named
  • Challenge conventional wisdom with evidence
  • Share vulnerable, honest experiences

Data-Driven Content

  • Product data analysis (anonymized insights)
  • Public data analysis (uncover patterns)
  • Original research (run experiments, share results)

Expert Roundups 15-30 experts answering one specific question. Built-in distribution.

Case Studies Structure: Challenge → Solution → Results → Key learnings

Meta Content Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC."

When the goal of a piece is backlinks specifically, format choice matters more than production effort. Foundation Inc.'s B2B Backlink Intelligence Report (March 2026 — a single vendor study of B2B SaaS sites, so treat as directional) measured each format's share of backlinks relative to its share of pages:

Format Backlinks vs. page share
Statistics / data roundups 4.25x
Glossary / definition pages 1.47x
Interactive tools / calculators (see free-tools) 1.38x
How-to / tutorials 1.36x
Original research / reports 0.80x
Ultimate guides 0.77x
Thought leadership 0.74x
Templates / frameworks 0.68x

The counterintuitive read: curating statistics earns ~5x the links of producing original research. Writers link to whatever makes citation easiest — a maintained stat-roundup page is citation infrastructure, while original research often gets cited via the roundups that aggregate it. Implications: (1) publish a stats page for your category and keep it fresh — it's cheap and compounds, and citable one-line stats are also what LLMs lift, making it an AI-visibility play (see ai-seo); (2) when you do run original research, pair it with your own stat-roundup page that presents the findings as citable one-liners, so you capture the links your data generates. The formats at the bottom aren't dead — guides, templates, and thought leadership earn their keep on rankings, conversions, and brand. Judge each piece by the job it's for, and don't expect links from formats that don't earn them.

For programmatic content at scale, see programmatic-seo skill.


Content Pillars and Topic Clusters

Content pillars are the 3-5 core topics your brand will own. Each pillar spawns a cluster of related content.

Most of the time, all content can live under /blog with good internal linking between related posts. Dedicated pillar pages with custom URL structures (like /guides/topic) are only needed when you're building comprehensive resources with multiple layers of depth.

How to Identify Pillars
  1. Product-led: What problems does your product solve?
  2. Audience-led: What does your ICP need to learn?
  3. Search-led: What topics have volume in your space?
  4. Competitor-led: What are competitors ranking for?
Pillar Structure
Pillar Topic (Hub)
├── Subtopic Cluster 1
│   ├── Article A
│   ├── Article B
│   └── Article C
├── Subtopic Cluster 2
│   ├── Article D
│   ├── Article E
│   └── Article F
└── Subtopic Cluster 3
    ├── Article G
    ├── Article H
    └── Article I
Pillar Criteria

Good pillars should:

  • Align with your product/service
  • Match what your audience cares about
  • Have search volume and/or social interest
  • Be broad enough for many subtopics

Keyword Research by Buyer Stage

Map topics to the buyer's journey using proven keyword modifiers:

Awareness Stage

Modifiers: "what is," "how to," "guide to," "introduction to"

Example: If customers ask about project management basics:

  • "What is Agile Project Management"
  • "Guide to Sprint Planning"
  • "How to Run a Standup Meeting"
Consideration Stage

Modifiers: "best," "top," "vs," "alternatives," "comparison"

Example: If customers evaluate multiple tools:

  • "Best Project Management Tools for Remote Teams"
  • "Asana vs Trello vs Monday"
  • "Basecamp Alternatives"
Decision Stage

Modifiers: "pricing," "reviews," "demo," "trial," "buy"

Example: If pricing comes up in sales calls:

  • "Project Management Tool Pricing Comparison"
  • "How to Choose the Right Plan"
  • "[Product] Reviews"
Implementation Stage

Modifiers: "templates," "examples," "tutorial," "how to use," "setup"

Example: If support tickets show implementation struggles:

  • "Project Template Library"
  • "Step-by-Step Setup Tutorial"
  • "How to Use [Feature]"

Content Ideation Sources

1. Keyword Data

If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:

  • Topic clusters (group related keywords)
  • Buyer stage (awareness/consideration/decision/implementation)
  • Search intent (informational, commercial, transactional)
  • Quick wins (low competition + decent volume + high relevance)
  • Content gaps (keywords competitors rank for that you don't)

Output as prioritized table: | Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |

2. Call Transcripts

If user provides sales or customer call transcripts, extract:

  • Questions asked → FAQ content or blog posts
  • Pain points → problems in their own words
  • Objections → content to address proactively
  • Language patterns → exact phrases to use (voice of customer)
  • Competitor mentions → what they compared you to

Output content ideas with supporting quotes.

3. Survey Responses

If user provides survey data, mine for:

  • Open-ended responses (topics and language)
  • Common themes (30%+ mention = high priority)
  • Resource requests (what they wish existed)
  • Content preferences (formats they want)
4. Forum Research

Use web search to find content ideas:

Reddit: site:reddit.com [topic]

  • Top posts in relevant subreddits
  • Questions and frustrations in comments
  • Upvoted answers (validates what resonates)

Quora: site:quora.com [topic]

  • Most-followed questions
  • Highly upvoted answers

Other: Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord

Extract: FAQs, misconceptions, debates, problems being solved, terminology used.

5. Competitor Analysis

Use web search to analyze competitor content:

Find their content: site:competitor.com/blog

Analyze:

  • Top-performing posts (comments, shares)
  • Topics covered repeatedly
  • Gaps they haven't covered
  • Case studies (customer problems, use cases, results)
  • Content structure (pillars, categories, formats)

Identify opportunities:

  • Topics you can cover better
  • Angles they're missing
  • Outdated content to improve on
6. Sales and Support Input

Extract from customer-facing teams:

  • Common objections
  • Repeated questions
  • Support ticket patterns
  • Success stories
  • Feature requests and underlying problems

Prioritizing Content Ideas

Score each idea on four factors:

1. Customer Impact (40%)
  • How frequently did this topic come up in research?
  • What percentage of customers face this challenge?
  • How emotionally charged was this pain point?
  • What's the potential LTV of customers with this need?
2. Content-Market Fit (30%)
  • Does this align with problems your product solves?
  • Can you offer unique insights from customer research?
  • Do you have customer stories to support this?
  • Will this naturally lead to product interest?
3. Search Potential (20%)
  • What's the monthly search volume?
  • How competitive is this topic?
  • Are there related long-tail opportunities?
  • Is search interest growing or declining?
4. Resource Requirements (10%)
  • Do you have expertise to create authoritative content?
  • What additional research is needed?
  • What assets (graphics, data, examples) will you need?
Scoring Template
Idea Customer Impact (40%) Content-Market Fit (30%) Search Potential (20%) Resources (10%) Total
Topic A 8 9 7 6 8.0
Topic B 6 7 9 8 7.1

Score 1-10 per factor, multiply by the weight, sum for the total. Rank the list; make the top-scoring pieces first.


Calendar Split: 60/30/10

Balance the editorial calendar so search compounds while shareable pieces keep you visible:

  • 60% searchable — the foundation. Demand you can capture predictably (use-case content, hub/spoke, how-tos).
  • 30% shareable — thought leadership, original data, opinion. Creates demand and earns links/mentions.
  • 10% experimental — new formats, channels, or bets. Cheap insurance against a stale mix.

This is a starting ratio, not a rule. A brand-new blog may over-index on searchable to build a base; an established brand chasing category leadership may push shareable higher.


Per-Format Execution Discipline

Treating content like a product means each format has a production standard, not just a topic:

  • Blog post — write 10 title options before drafting (the title does most of the work; pick the strongest). Plan ~5 editing passes (structure, clarity, evidence, line edit, headline/SEO). For the writing itself, see copywriting.
  • Long-form guide — the flagship of a pillar. Comprehensive enough to be the resource; structured with a table of contents and internal links to spokes. Build the hub before the spokes.
  • Video — script the hook first; front-load the payoff. Repurpose into short-form clips at creation time (see social).
  • Podcast — one interview yields a transcript, quote graphics, short clips, and a written recap. Design the episode knowing it will be atomized.
  • Email — one idea per send; the subject line is the title—write several and pick. For sequences and lifecycle, see emails.

Create Once, Distribute Twice

Creating content is half the job—distribution is the other half, and most teams skip it. The philosophy: one exceptional piece, reformatted and repurposed across every channel, not a fresh piece per platform. Pouring effort into a single flagship and then distributing it everywhere beats spreading thin effort across many mediocre platform-native posts.

Build distribution hooks into the piece at creation time, not after: write subheads that stand alone as social posts, structure sections to be lifted out modularly, and pull quotes/stats you already know you'll graphic-ify. A well-designed guide is a distribution kit in disguise.

The ORB Framework as a funnel — route attention from borrowed → rented → owned, which maps to discovery → engagement → conversion:

  • Borrowed (other people's audiences: podcasts, guest posts, partnerships) — discovery / breakthrough reach.
  • Rented (social platforms, ad networks) — engagement, but you don't own the audience or the algorithm.
  • Owned (email list, blog, community) — conversion and the only durable asset. Everything upstream should funnel here.

ORB mechanics live in the launch skill (channel-type playbook) and content atomization/repurposing lives in social; the value here is consolidating the distribute half of content strategy so it has a home.

Failure modes to avoid:

  • Spray-and-pray — posting everywhere with no flagship and no repurposing plan. Effort scatters, nothing compounds.
  • Platform dependency — building on rented land. Facebook organic reach fell from ~20% to under 2%; any rented channel can throttle you overnight.
  • The ownership paradox — teams spend ~90% of effort on channels they don't control (rented/borrowed) and neglect the owned assets that actually convert and can't be taken away.

For the full distribution spine—the Content Distribution Flywheel, platform half-lives, and the atomization checklist—see the reference below.


Output Format

When creating a content strategy, provide:

1. Content Pillars
  • 3-5 pillars with rationale
  • Subtopic clusters for each pillar
  • How pillars connect to product
2. Priority Topics

For each recommended piece:

  • Topic/title
  • Searchable, shareable, or both
  • Content type (use-case, hub/spoke, thought leadership, etc.)
  • Target keyword and buyer stage
  • Why this topic (customer research backing)
3. Topic Cluster Map

Visual or structured representation of how content interconnects.


Task-Specific Questions

  1. What patterns emerge from your last 10 customer conversations?
  2. What questions keep coming up in sales calls?
  3. Where are competitors' content efforts falling short?
  4. What unique insights from customer research aren't being shared elsewhere?
  5. Which existing content drives the most conversions, and why?

References

  • Content Distribution Spine: Create Once Distribute Twice, ORB as a funnel, the ownership paradox, platform half-lives, the Content Distribution Flywheel, and the per-flagship atomization checklist
  • Headless CMS Guide: CMS selection, content modeling for marketing, editorial workflows, platform comparison (Sanity, Contentful, Strapi)

  • copywriting: For writing individual content pieces
  • seo-audit: For technical SEO and on-page optimization
  • ai-seo: For optimizing content for AI search engines and getting cited by LLMs
  • programmatic-seo: For scaled content generation
  • site-architecture: For page hierarchy, navigation design, and URL structure
  • emails: For email-based content
  • social: For social media content, content atomization, and repurposing execution
  • launch: For the ORB channel-type playbook and launch-day distribution
1---
2name: content-strategy
3description: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.
4metadata:
5 version: 2.1.1
6---
7 
8# Content Strategy
9 
10You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.
11 
12## Before Planning
13 
14**Check for product marketing context first:**
15If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
16 
17Gather this context (ask if not provided):
18 
19### 1. Business Context
20- What does the company do?
21- Who is the ideal customer?
22- What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)
23- What problems does your product solve?
24 
25### 2. Customer Research
26- What questions do customers ask before buying?
27- What objections come up in sales calls?
28- What topics appear repeatedly in support tickets?
29- What language do customers use to describe their problems?
30 
31### 3. Current State
32- Do you have existing content? What's working?
33- What resources do you have? (writers, budget, time)
34- What content formats can you produce? (written, video, audio)
35 
36### 4. Competitive Landscape
37- Who are your main competitors?
38- What content gaps exist in your market?
39 
40---
41 
42## Treat Content Like a Product
43 
44Every piece is its own launch. Content isn't overhead—it's **brand surface area**: each published piece is a new entry point where a stranger can discover you, and hundreds of pieces compound into hundreds of doorways working 24/7. Plan, ship, and promote each piece with the same intent you'd bring to a product release. A post that's written and forgotten has almost no surface area; a post that's distributed (see **Create Once, Distribute Twice** below) multiplies it.
45 
46This section covers the searchable/shareable lens, then the execution and prioritization layer: which pieces to make (scoring), how the calendar splits, and per-format discipline.
47 
48## Searchable vs Shareable
49 
50Every piece of content must be searchable, shareable, or both. Prioritize in that order—search traffic is the foundation.
51 
52**Searchable content** captures existing demand. Optimized for people actively looking for answers.
53 
54**Shareable content** creates demand. Spreads ideas and gets people talking.
55 
56### When Writing Searchable Content
57 
58- Target a specific keyword or question
59- Match search intent exactly—answer what the searcher wants
60- Use clear titles that match search queries
61- Structure with headings that mirror search patterns
62- Place keywords in title, headings, first paragraph, URL
63- Provide comprehensive coverage (don't leave questions unanswered)
64- Include data, examples, and links to authoritative sources
65- Optimize for AI/LLM discovery: clear positioning, structured content, brand consistency across the web
66 
67### When Writing Shareable Content
68 
69- Lead with a novel insight, original data, or counterintuitive take
70- Challenge conventional wisdom with well-reasoned arguments
71- Tell stories that make people feel something
72- Create content people want to share to look smart or help others
73- Connect to current trends or emerging problems
74- Share vulnerable, honest experiences others can learn from
75 
76---
77 
78## Content Types
79 
80### Searchable Content Types
81 
82**Use-Case Content**
83Formula: [persona] + [use-case]. Targets long-tail keywords.
84- "Project management for designers"
85- "Task tracking for developers"
86- "Client collaboration for freelancers"
87 
88**Hub and Spoke**
89Hub = comprehensive overview. Spokes = related subtopics.
90```
91/topic (hub)
92├── /topic/subtopic-1 (spoke)
93├── /topic/subtopic-2 (spoke)
94└── /topic/subtopic-3 (spoke)
95```
96Create hub first, then build spokes. Interlink strategically.
97 
98**Note:** Most content works fine under `/blog`. Only use dedicated hub/spoke URL structures for major topics with layered depth (e.g., Atlassian's `/agile` guide). For typical blog posts, `/blog/post-title` is sufficient.
99 
100**Template Libraries**
101High-intent keywords + product adoption.
102- Target searches like "marketing plan template"
103- Provide immediate standalone value
104- Show how product enhances the template
105 
106### Shareable Content Types
107 
108**Thought Leadership**
109- Articulate concepts everyone feels but hasn't named
110- Challenge conventional wisdom with evidence
111- Share vulnerable, honest experiences
112 
113**Data-Driven Content**
114- Product data analysis (anonymized insights)
115- Public data analysis (uncover patterns)
116- Original research (run experiments, share results)
117 
118**Expert Roundups**
11915-30 experts answering one specific question. Built-in distribution.
120 
121**Case Studies**
122Structure: Challenge → Solution → Results → Key learnings
123 
124**Meta Content**
125Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC."
126 
127### Link-Earning Formats
128 
129When the goal of a piece is backlinks specifically, format choice matters more than production effort. Foundation Inc.'s B2B Backlink Intelligence Report (March 2026 — a single vendor study of B2B SaaS sites, so treat as directional) measured each format's share of backlinks relative to its share of pages:
130 
131| Format | Backlinks vs. page share |
132|---|---|
133| Statistics / data roundups | **4.25x** |
134| Glossary / definition pages | 1.47x |
135| Interactive tools / calculators (see **free-tools**) | 1.38x |
136| How-to / tutorials | 1.36x |
137| Original research / reports | 0.80x |
138| Ultimate guides | 0.77x |
139| Thought leadership | 0.74x |
140| Templates / frameworks | 0.68x |
141 
142The counterintuitive read: **curating statistics earns ~5x the links of producing original research.** Writers link to whatever makes citation easiest — a maintained stat-roundup page is citation infrastructure, while original research often gets cited *via* the roundups that aggregate it. Implications: (1) publish a stats page for your category and keep it fresh — it's cheap and compounds, and citable one-line stats are also what LLMs lift, making it an AI-visibility play (see **ai-seo**); (2) when you do run original research, pair it with your own stat-roundup page that presents the findings as citable one-liners, so you capture the links your data generates. The formats at the bottom aren't dead — guides, templates, and thought leadership earn their keep on rankings, conversions, and brand. Judge each piece by the job it's for, and don't expect links from formats that don't earn them.
143 
144For programmatic content at scale, see **programmatic-seo** skill.
145 
146---
147 
148## Content Pillars and Topic Clusters
149 
150Content pillars are the 3-5 core topics your brand will own. Each pillar spawns a cluster of related content.
151 
152Most of the time, all content can live under `/blog` with good internal linking between related posts. Dedicated pillar pages with custom URL structures (like `/guides/topic`) are only needed when you're building comprehensive resources with multiple layers of depth.
153 
154### How to Identify Pillars
155 
1561. **Product-led**: What problems does your product solve?
1572. **Audience-led**: What does your ICP need to learn?
1583. **Search-led**: What topics have volume in your space?
1594. **Competitor-led**: What are competitors ranking for?
160 
161### Pillar Structure
162 
163```
164Pillar Topic (Hub)
165├── Subtopic Cluster 1
166│ ├── Article A
167│ ├── Article B
168│ └── Article C
169├── Subtopic Cluster 2
170│ ├── Article D
171│ ├── Article E
172│ └── Article F
173└── Subtopic Cluster 3
174 ├── Article G
175 ├── Article H
176 └── Article I
177```
178 
179### Pillar Criteria
180 
181Good pillars should:
182- Align with your product/service
183- Match what your audience cares about
184- Have search volume and/or social interest
185- Be broad enough for many subtopics
186 
187---
188 
189## Keyword Research by Buyer Stage
190 
191Map topics to the buyer's journey using proven keyword modifiers:
192 
193### Awareness Stage
194Modifiers: "what is," "how to," "guide to," "introduction to"
195 
196Example: If customers ask about project management basics:
197- "What is Agile Project Management"
198- "Guide to Sprint Planning"
199- "How to Run a Standup Meeting"
200 
201### Consideration Stage
202Modifiers: "best," "top," "vs," "alternatives," "comparison"
203 
204Example: If customers evaluate multiple tools:
205- "Best Project Management Tools for Remote Teams"
206- "Asana vs Trello vs Monday"
207- "Basecamp Alternatives"
208 
209### Decision Stage
210Modifiers: "pricing," "reviews," "demo," "trial," "buy"
211 
212Example: If pricing comes up in sales calls:
213- "Project Management Tool Pricing Comparison"
214- "How to Choose the Right Plan"
215- "[Product] Reviews"
216 
217### Implementation Stage
218Modifiers: "templates," "examples," "tutorial," "how to use," "setup"
219 
220Example: If support tickets show implementation struggles:
221- "Project Template Library"
222- "Step-by-Step Setup Tutorial"
223- "How to Use [Feature]"
224 
225---
226 
227## Content Ideation Sources
228 
229### 1. Keyword Data
230 
231If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:
232- Topic clusters (group related keywords)
233- Buyer stage (awareness/consideration/decision/implementation)
234- Search intent (informational, commercial, transactional)
235- Quick wins (low competition + decent volume + high relevance)
236- Content gaps (keywords competitors rank for that you don't)
237 
238Output as prioritized table:
239| Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |
240 
241### 2. Call Transcripts
242 
243If user provides sales or customer call transcripts, extract:
244- Questions asked → FAQ content or blog posts
245- Pain points → problems in their own words
246- Objections → content to address proactively
247- Language patterns → exact phrases to use (voice of customer)
248- Competitor mentions → what they compared you to
249 
250Output content ideas with supporting quotes.
251 
252### 3. Survey Responses
253 
254If user provides survey data, mine for:
255- Open-ended responses (topics and language)
256- Common themes (30%+ mention = high priority)
257- Resource requests (what they wish existed)
258- Content preferences (formats they want)
259 
260### 4. Forum Research
261 
262Use web search to find content ideas:
263 
264**Reddit:** `site:reddit.com [topic]`
265- Top posts in relevant subreddits
266- Questions and frustrations in comments
267- Upvoted answers (validates what resonates)
268 
269**Quora:** `site:quora.com [topic]`
270- Most-followed questions
271- Highly upvoted answers
272 
273**Other:** Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord
274 
275Extract: FAQs, misconceptions, debates, problems being solved, terminology used.
276 
277### 5. Competitor Analysis
278 
279Use web search to analyze competitor content:
280 
281**Find their content:** `site:competitor.com/blog`
282 
283**Analyze:**
284- Top-performing posts (comments, shares)
285- Topics covered repeatedly
286- Gaps they haven't covered
287- Case studies (customer problems, use cases, results)
288- Content structure (pillars, categories, formats)
289 
290**Identify opportunities:**
291- Topics you can cover better
292- Angles they're missing
293- Outdated content to improve on
294 
295### 6. Sales and Support Input
296 
297Extract from customer-facing teams:
298- Common objections
299- Repeated questions
300- Support ticket patterns
301- Success stories
302- Feature requests and underlying problems
303 
304---
305 
306## Prioritizing Content Ideas
307 
308Score each idea on four factors:
309 
310### 1. Customer Impact (40%)
311- How frequently did this topic come up in research?
312- What percentage of customers face this challenge?
313- How emotionally charged was this pain point?
314- What's the potential LTV of customers with this need?
315 
316### 2. Content-Market Fit (30%)
317- Does this align with problems your product solves?
318- Can you offer unique insights from customer research?
319- Do you have customer stories to support this?
320- Will this naturally lead to product interest?
321 
322### 3. Search Potential (20%)
323- What's the monthly search volume?
324- How competitive is this topic?
325- Are there related long-tail opportunities?
326- Is search interest growing or declining?
327 
328### 4. Resource Requirements (10%)
329- Do you have expertise to create authoritative content?
330- What additional research is needed?
331- What assets (graphics, data, examples) will you need?
332 
333### Scoring Template
334 
335| Idea | Customer Impact (40%) | Content-Market Fit (30%) | Search Potential (20%) | Resources (10%) | Total |
336|------|----------------------|-------------------------|----------------------|-----------------|-------|
337| Topic A | 8 | 9 | 7 | 6 | 8.0 |
338| Topic B | 6 | 7 | 9 | 8 | 7.1 |
339 
340Score 1-10 per factor, multiply by the weight, sum for the total. Rank the list; make the top-scoring pieces first.
341 
342---
343 
344## Calendar Split: 60/30/10
345 
346Balance the editorial calendar so search compounds while shareable pieces keep you visible:
347 
348- **60% searchable** — the foundation. Demand you can capture predictably (use-case content, hub/spoke, how-tos).
349- **30% shareable** — thought leadership, original data, opinion. Creates demand and earns links/mentions.
350- **10% experimental** — new formats, channels, or bets. Cheap insurance against a stale mix.
351 
352This is a starting ratio, not a rule. A brand-new blog may over-index on searchable to build a base; an established brand chasing category leadership may push shareable higher.
353 
354---
355 
356## Per-Format Execution Discipline
357 
358Treating content like a product means each format has a production standard, not just a topic:
359 
360- **Blog post** — write **10 title options** before drafting (the title does most of the work; pick the strongest). Plan **~5 editing passes** (structure, clarity, evidence, line edit, headline/SEO). For the writing itself, see **copywriting**.
361- **Long-form guide** — the flagship of a pillar. Comprehensive enough to be *the* resource; structured with a table of contents and internal links to spokes. Build the hub before the spokes.
362- **Video** — script the hook first; front-load the payoff. Repurpose into short-form clips at creation time (see **social**).
363- **Podcast** — one interview yields a transcript, quote graphics, short clips, and a written recap. Design the episode knowing it will be atomized.
364- **Email** — one idea per send; the subject line is the title—write several and pick. For sequences and lifecycle, see **emails**.
365 
366---
367 
368## Create Once, Distribute Twice
369 
370Creating content is half the job—distribution is the other half, and most teams skip it. The philosophy: **one exceptional piece, reformatted and repurposed across every channel, not a fresh piece per platform.** Pouring effort into a single flagship and then distributing it everywhere beats spreading thin effort across many mediocre platform-native posts.
371 
372Build **distribution hooks into the piece at creation time**, not after: write subheads that stand alone as social posts, structure sections to be lifted out modularly, and pull quotes/stats you already know you'll graphic-ify. A well-designed guide is a distribution kit in disguise.
373 
374**The ORB Framework as a funnel** — route attention from borrowed → rented → owned, which maps to discovery → engagement → conversion:
375 
376- **Borrowed** (other people's audiences: podcasts, guest posts, partnerships) — discovery / breakthrough reach.
377- **Rented** (social platforms, ad networks) — engagement, but you don't own the audience or the algorithm.
378- **Owned** (email list, blog, community) — conversion and the only durable asset. Everything upstream should funnel here.
379 
380ORB mechanics live in the **launch** skill (channel-type playbook) and content atomization/repurposing lives in **social**; the value here is consolidating the *distribute* half of content strategy so it has a home.
381 
382**Failure modes to avoid:**
383- **Spray-and-pray** — posting everywhere with no flagship and no repurposing plan. Effort scatters, nothing compounds.
384- **Platform dependency** — building on rented land. Facebook organic reach fell from ~20% to under 2%; any rented channel can throttle you overnight.
385- **The ownership paradox** — teams spend ~90% of effort on channels they don't control (rented/borrowed) and neglect the owned assets that actually convert and can't be taken away.
386 
387For the full distribution spine—the Content Distribution Flywheel, platform half-lives, and the atomization checklist—see the reference below.
388 
389---
390 
391## Output Format
392 
393When creating a content strategy, provide:
394 
395### 1. Content Pillars
396- 3-5 pillars with rationale
397- Subtopic clusters for each pillar
398- How pillars connect to product
399 
400### 2. Priority Topics
401For each recommended piece:
402- Topic/title
403- Searchable, shareable, or both
404- Content type (use-case, hub/spoke, thought leadership, etc.)
405- Target keyword and buyer stage
406- Why this topic (customer research backing)
407 
408### 3. Topic Cluster Map
409Visual or structured representation of how content interconnects.
410 
411---
412 
413## Task-Specific Questions
414 
4151. What patterns emerge from your last 10 customer conversations?
4162. What questions keep coming up in sales calls?
4173. Where are competitors' content efforts falling short?
4184. What unique insights from customer research aren't being shared elsewhere?
4195. Which existing content drives the most conversions, and why?
420 
421---
422 
423## References
424 
425- **[Content Distribution Spine](references/content-distribution.md)**: Create Once Distribute Twice, ORB as a funnel, the ownership paradox, platform half-lives, the Content Distribution Flywheel, and the per-flagship atomization checklist
426- **[Headless CMS Guide](references/headless-cms.md)**: CMS selection, content modeling for marketing, editorial workflows, platform comparison (Sanity, Contentful, Strapi)
427 
428---
429 
430## Related Skills
431 
432- **copywriting**: For writing individual content pieces
433- **seo-audit**: For technical SEO and on-page optimization
434- **ai-seo**: For optimizing content for AI search engines and getting cited by LLMs
435- **programmatic-seo**: For scaled content generation
436- **site-architecture**: For page hierarchy, navigation design, and URL structure
437- **emails**: For email-based content
438- **social**: For social media content, content atomization, and repurposing execution
439- **launch**: For the ORB channel-type playbook and launch-day distribution
440 
View all files on GitHub →

Details

Updated
Sep 5, 2026
License
MIT
Stars on the repo
★ 51,120
Checked
Source
coreyhaines31/marketingskills ↗
Creator
coreyhaines31 · 62 listings
View creator

Similar skills

See all →
MCP3-5 days | Agents: 6 | Gate Keepers: DevOps Automator +⚙️ Phase 2 Playbook — Foundation & Scaffoldingmsitarzewski/agency-agents · by msitarzewski> Duration: 3-5 days | Agents: 6 | Gate Keepers: DevOps Automator + Evidence Collector★ 154k GitHub starsMCPNEXUS transforms The Agency's independent AI specialists🌐 NEXUS — Network of EXperts, Unified in Strategymsitarzewski/agency-agents · by msitarzewski> NEXUS transforms The Agency's independent AI specialists into a synchronized intelligence network. This is not a prompt collection — it…★ 154k GitHub starsSkillGenerate an Ansoff Matrix analysis mapping growth strategiesphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsSkillSurvey any codebase as a senior advisorImproveshadcn/improve · by shadcnSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.★ 9.2k GitHub starsSkillTranslate skills from one industry to anotherCareer changer translatorParamchoudhary/ResumeSkills · by ParamchoudharyTranslate skills from one industry to another, identify transferable skills★ 2.4k GitHub starsSkillA collection of 37 battle-tested marketing skillsOpenClaw Marketing SkillsLeoYeAI/openclaw-marketing-skills · by LeoYeAIA collection of 37 battle-tested marketing skills for OpenClaw agents. Use when you want to install or reference any marketing skill including: CRO (page-cro, signup-flow-cro, onboarding-cro, form-cro, popup-cro, paywall-upgrade-cro), copywriting, copy-editing, cold-email, email-sequence, social-content, seo-audit, ai-seo, programmatic-seo, site-architecture, schema-markup, content-strategy, paid-ads, ad-creative, ab-test-setup, analytics-tracking, referral-program, free-tool-strategy, churn-prevention, revops, sales-enablement, launch-strategy, pricing-strategy, competitor-alternatives, marketing-ideas, marketing-psychology, lead-magnets, product-marketing-context, and data connectors (google-ads-connect, search-console-connect, meta-ads-connect, x-twitter-connect). Start with product-marketing-context to set up your product context document, then use any other skill naturally. Powered by MyClaw.ai.★ 1k GitHub stars

More from coreyhaines31

SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillPlan, design, or implement an A/B test or experimentA/B Test Setupcoreyhaines31/marketingskills · by coreyhaines31When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.★ 51.1k GitHub starsSkillGenerate, iterate, or scale ad creativecoreyhaines31/marketingskills · by coreyhaines31When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.★ 51.1k GitHub starsSkillBusiness-brainstorm — Pressure-test a business ideacoreyhaines31/makerskills · by coreyhaines31When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) — this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."★ 855 GitHub starsSkillYour team's shared, AI-ready knowledge base/company-brain — Team-shared AI-ready knowledge basecoreyhaines31/makerskills · by coreyhaines31Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X.★ 855 GitHub starsSkillMonthly CFO workflow for a company or agency/company-cfo — Monthly company CFO workflowcoreyhaines31/makerskills · by coreyhaines31Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse.★ 855 GitHub stars