Skill Tracer
Skills › Marketing Skills › content-strategy

content-strategy

skill · 444 lines · MIT · skills/content-strategy/SKILL.md

The facts

Its 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.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

It fires when someone wants to decide what content to make — topics, pillars, an editorial calendar, a blog or content roadmap — rather than write, audit, or distribute an individual piece. The agent picks it up from a request to plan content or a plain admission that they don't know what to write about.

Things a person might say (the model's guesses)

  • “I want to start a blog for our SaaS but I have no idea what to write about.”
  • “Can you build us a content strategy with topic clusters and an editorial calendar for next quarter?”
  • “What content should we create to bring in more leads?”

A model's summary of when it is used.

A model's reading

Starts other agents

1 line mentions starting other agents

Lines in the file that mention starting another agent. Found by matching words, so treat them as pointers.

Found by matching wordsline 154

Files it mentions

references/content-distribution.md, references/headless-cms.md

Files the text names, such as ones to read or write. Found by matching words, so treat them as pointers.

Found by matching wordsline 429 line 430

What it leads to

Other skills this one hands off to, calls, requires or offers instead, as a model read them.

A model's reading

What leads to it

Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.

A model's reading

Licence

MIT, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

Other settings

metadata: version: 2.1.5

More settings at the top of the file, shown as written.

From its settingsline 4
Other files in this skill (3) Close

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

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.5
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.

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.

Raw lines 1 to 11
Names a skill copywriting :3
Names a skill seo-audit :3
Names a skill social :3
12## Before Planning
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.
17Gather this context (ask if not provided):

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):

Raw lines 12 to 18
Names a skill product-marketing :14
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?

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?
Raw lines 19 to 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?

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?
Raw lines 25 to 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)

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)
Raw lines 31 to 35
36### 4. Competitive Landscape
37- Who are your main competitors?
38- What content gaps exist in your market?
40---

4. Competitive Landscape

  • Who are your main competitors?
  • What content gaps exist in your market?

Raw lines 36 to 41
42## Treat Content Like a Product
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.
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.

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.

Raw lines 42 to 47
48## Searchable vs Shareable
50Every piece of content must be searchable, shareable, or both. Prioritize in that order—search traffic is the foundation.
52**Searchable content** captures existing demand. Optimized for people actively looking for answers.
54**Shareable content** creates demand. Spreads ideas and gets people talking.

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.

Raw lines 48 to 55
56### When Writing Searchable Content
58**The information-gain gate:** before committing to a searchable piece, read the current top results for its query and write one sentence on what yours will add that none of them have: original data, a real product example, a working tool or template, a clearer answer, a stronger opinion. If you can't write that sentence, don't write the piece. It will be the eleventh copy of the same article, and neither Google nor AI assistants have a reason to prefer it.
60- Target a specific keyword or question
61- Match search intent exactly—answer what the searcher wants
62- Use clear titles that match search queries
63- Structure with headings that mirror search patterns
64- Place keywords in title, headings, first paragraph, URL
65- Provide comprehensive coverage (don't leave questions unanswered)
66- Include data, examples, and links to authoritative sources
67- Optimize for AI/LLM discovery: clear positioning, structured content, brand consistency across the web

When Writing Searchable Content

The information-gain gate: before committing to a searchable piece, read the current top results for its query and write one sentence on what yours will add that none of them have: original data, a real product example, a working tool or template, a clearer answer, a stronger opinion. If you can't write that sentence, don't write the piece. It will be the eleventh copy of the same article, and neither Google nor AI assistants have a reason to prefer it.

  • 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
Raw lines 56 to 68
69### When Writing Shareable Content
71- Lead with a novel insight, original data, or counterintuitive take
72- Challenge conventional wisdom with well-reasoned arguments
73- Tell stories that make people feel something
74- Create content people want to share to look smart or help others
75- Connect to current trends or emerging problems
76- Share vulnerable, honest experiences others can learn from
78---

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

Raw lines 69 to 79
80## Content Types

Content Types

Raw lines 80 to 81
82### Searchable Content Types
84**Use-Case Content**
85Formula: [persona] + [use-case]. Targets long-tail keywords.
86- "Project management for designers"
87- "Task tracking for developers"
88- "Client collaboration for freelancers"
90**Hub and Spoke**
91Hub = comprehensive overview. Spokes = related subtopics.
92```
93/topic (hub)
94├── /topic/subtopic-1 (spoke)
95├── /topic/subtopic-2 (spoke)
96└── /topic/subtopic-3 (spoke)
97```
98Create hub first, then build spokes. Interlink strategically.
100**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.
102**Template Libraries**
103High-intent keywords + product adoption.
104- Target searches like "marketing plan template"
105- Provide immediate standalone value
106- Show how product enhances the template

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
Raw lines 82 to 107
108### Shareable Content Types
110**Thought Leadership**
111- Articulate concepts everyone feels but hasn't named
112- Challenge conventional wisdom with evidence
113- Share vulnerable, honest experiences
115**Data-Driven Content**
116- Product data analysis (anonymized insights)
117- Public data analysis (uncover patterns)
118- Original research (run experiments, share results)
120**Expert Roundups**
12115-30 experts answering one specific question. Built-in distribution.
123**Case Studies**
124Structure: Challenge → Solution → Results → Key learnings
126**Meta Content**
127Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC."

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."

Raw lines 108 to 128
129### Link-Earning Formats
131When 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:
133| Format | Backlinks vs. page share |
134|---|---|
135| Statistics / data roundups | **4.25x** |
136| Glossary / definition pages | 1.47x |
137| Interactive tools / calculators (see **free-tools**) | 1.38x |
138| How-to / tutorials | 1.36x |
139| Original research / reports | 0.80x |
140| Ultimate guides | 0.77x |
141| Thought leadership | 0.74x |
142| Templates / frameworks | 0.68x |
144The 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.
146To get those assets in front of the people who link, and to point their authority at the pages that need it, see **link-building**.
148For programmatic content at scale, see **programmatic-seo** skill.
150---

Link-Earning Formats

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:

FormatBacklinks vs. page share
Statistics / data roundups4.25x
Glossary / definition pages1.47x
Interactive tools / calculators (see free-tools)1.38x
How-to / tutorials1.36x
Original research / reports0.80x
Ultimate guides0.77x
Thought leadership0.74x
Templates / frameworks0.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.

To get those assets in front of the people who link, and to point their authority at the pages that need it, see link-building.

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


Raw lines 129 to 151
Names a skill free-tools :137
Names a skill ai-seo :144
Names a skill link-building :146
Names a skill programmatic-seo :148
152## Content Pillars and Topic Clusters
154Content pillars are the 3-5 core topics your brand will own. Each pillar spawns a cluster of related content.
156Most 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.

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.

Raw lines 152 to 157
Starts an agent spawns :154
158### How to Identify Pillars
1601. **Product-led**: What problems does your product solve?
1612. **Audience-led**: What does your ICP need to learn?
1623. **Search-led**: What topics have volume in your space?
1634. **Competitor-led**: What are competitors ranking for?

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?
Raw lines 158 to 164
165### Pillar Structure
167```
168Pillar Topic (Hub)
169├── Subtopic Cluster 1
170│ ├── Article A
171│ ├── Article B
172│ └── Article C
173├── Subtopic Cluster 2
174│ ├── Article D
175│ ├── Article E
176│ └── Article F
177└── Subtopic Cluster 3
178 ├── Article G
179 ├── Article H
180 └── Article I
181```

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
Raw lines 165 to 182
183### Pillar Criteria
185Good pillars should:
186- Align with your product/service
187- Match what your audience cares about
188- Have search volume and/or social interest
189- Be broad enough for many subtopics
191---

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

Raw lines 183 to 192
193## Keyword Research by Buyer Stage
195Map topics to the buyer's journey using proven keyword modifiers:

Keyword Research by Buyer Stage

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

Raw lines 193 to 196
197### Awareness Stage
198Modifiers: "what is," "how to," "guide to," "introduction to"
200Example: If customers ask about project management basics:
201- "What is Agile Project Management"
202- "Guide to Sprint Planning"
203- "How to Run a Standup Meeting"

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"
Raw lines 197 to 204
205### Consideration Stage
206Modifiers: "best," "top," "vs," "alternatives," "comparison"
208Example: If customers evaluate multiple tools:
209- "Best Project Management Tools for Remote Teams"
210- "Asana vs Trello vs Monday"
211- "Basecamp Alternatives"

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"
Raw lines 205 to 212
213### Decision Stage
214Modifiers: "pricing," "reviews," "demo," "trial," "buy"
216Example: If pricing comes up in sales calls:
217- "Project Management Tool Pricing Comparison"
218- "How to Choose the Right Plan"
219- "[Product] Reviews"

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"
Raw lines 213 to 220
221### Implementation Stage
222Modifiers: "templates," "examples," "tutorial," "how to use," "setup"
224Example: If support tickets show implementation struggles:
225- "Project Template Library"
226- "Step-by-Step Setup Tutorial"
227- "How to Use [Feature]"
229---

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]"

Raw lines 221 to 230
231## Content Ideation Sources

Content Ideation Sources

Raw lines 231 to 232
233### 1. Keyword Data
235If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:
236- Topic clusters (group related keywords)
237- Buyer stage (awareness/consideration/decision/implementation)
238- Search intent (informational, commercial, transactional)
239- Quick wins (low competition + decent volume + high relevance)
240- Content gaps (keywords competitors rank for that you don't)
242Output as prioritized table:
243| Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |

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 |

Raw lines 233 to 244
245### 2. Call Transcripts
247If user provides sales or customer call transcripts, extract:
248- Questions asked → FAQ content or blog posts
249- Pain points → problems in their own words
250- Objections → content to address proactively
251- Language patterns → exact phrases to use (voice of customer)
252- Competitor mentions → what they compared you to
254Output content ideas with supporting quotes.

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.

Raw lines 245 to 255
256### 3. Survey Responses
258If user provides survey data, mine for:
259- Open-ended responses (topics and language)
260- Common themes (30%+ mention = high priority)
261- Resource requests (what they wish existed)
262- Content preferences (formats they want)

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)
Raw lines 256 to 263
264### 4. Forum Research
266Use web search to find content ideas:
268**Reddit:** `site:reddit.com [topic]`
269- Top posts in relevant subreddits
270- Questions and frustrations in comments
271- Upvoted answers (validates what resonates)
273**Quora:** `site:quora.com [topic]`
274- Most-followed questions
275- Highly upvoted answers
277**Other:** Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord
279Extract: FAQs, misconceptions, debates, problems being solved, terminology used.

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.

Raw lines 264 to 280
281### 5. Competitor Analysis
283Use web search to analyze competitor content:
285**Find their content:** `site:competitor.com/blog`
287**Analyze:**
288- Top-performing posts (comments, shares)
289- Topics covered repeatedly
290- Gaps they haven't covered
291- Case studies (customer problems, use cases, results)
292- Content structure (pillars, categories, formats)
294**Identify opportunities:**
295- Topics you can cover better
296- Angles they're missing
297- Outdated content to improve on

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
Raw lines 281 to 298
299### 6. Sales and Support Input
301Extract from customer-facing teams:
302- Common objections
303- Repeated questions
304- Support ticket patterns
305- Success stories
306- Feature requests and underlying problems
308---

6. Sales and Support Input

Extract from customer-facing teams:

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

Raw lines 299 to 309
310## Prioritizing Content Ideas
312Score each idea on four factors:

Prioritizing Content Ideas

Score each idea on four factors:

Raw lines 310 to 313
314### 1. Customer Impact (40%)
315- How frequently did this topic come up in research?
316- What percentage of customers face this challenge?
317- How emotionally charged was this pain point?
318- What's the potential LTV of customers with this need?

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?
Raw lines 314 to 319
320### 2. Content-Market Fit (30%)
321- Does this align with problems your product solves?
322- Can you offer unique insights from customer research?
323- Do you have customer stories to support this?
324- Will this naturally lead to product interest?

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?
Raw lines 320 to 325
326### 3. Search Potential (20%)
327- What's the monthly search volume?
328- How competitive is this topic?
329- Are there related long-tail opportunities?
330- Is search interest growing or declining?

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?
Raw lines 326 to 331
332### 4. Resource Requirements (10%)
333- Do you have expertise to create authoritative content?
334- What additional research is needed?
335- What assets (graphics, data, examples) will you need?

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?
Raw lines 332 to 336
337### Scoring Template
339| Idea | Customer Impact (40%) | Content-Market Fit (30%) | Search Potential (20%) | Resources (10%) | Total |
340|------|----------------------|-------------------------|----------------------|-----------------|-------|
341| Topic A | 8 | 9 | 7 | 6 | 7.9 |
342| Topic B | 6 | 7 | 9 | 8 | 7.1 |
344Score 1-10 per factor, multiply by the weight, sum for the total. Rank the list; make the top-scoring pieces first.
346---

Scoring Template

IdeaCustomer Impact (40%)Content-Market Fit (30%)Search Potential (20%)Resources (10%)Total
Topic A89767.9
Topic B67987.1

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


Raw lines 337 to 347
348## Calendar Split: 60/30/10
350Balance the editorial calendar so search compounds while shareable pieces keep you visible:
352- **60% searchable** — the foundation. Demand you can capture predictably (use-case content, hub/spoke, how-tos).
353- **30% shareable** — thought leadership, original data, opinion. Creates demand and earns links/mentions.
354- **10% experimental** — new formats, channels, or bets. Cheap insurance against a stale mix.
356This 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.
358---

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.


Raw lines 348 to 359
360## Per-Format Execution Discipline
362Treating content like a product means each format has a production standard, not just a topic:
364- **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**.
365- **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.
366- **Video** — script the hook first; front-load the payoff. Repurpose into short-form clips at creation time (see **social**).
367- **Podcast** — one interview yields a transcript, quote graphics, short clips, and a written recap. Design the episode knowing it will be atomized.
368- **Email** — one idea per send; the subject line is the title—write several and pick. For sequences and lifecycle, see **emails**.
370---

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.

Raw lines 360 to 371
Names a skill emails :368
372## Create Once, Distribute Twice
374Creating 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.
376Build **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.
378**The ORB Framework as a funnel** — route attention from borrowed → rented → owned, which maps to discovery → engagement → conversion:
380- **Borrowed** (other people's audiences: podcasts, guest posts, partnerships) — discovery / breakthrough reach.
381- **Rented** (social platforms, ad networks) — engagement, but you don't own the audience or the algorithm.
382- **Owned** (email list, blog, community) — conversion and the only durable asset. Everything upstream should funnel here.
384ORB 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.
386**Failure modes to avoid:**
387- **Spray-and-pray** — posting everywhere with no flagship and no repurposing plan. Effort scatters, nothing compounds.
388- **Platform dependency** — building on rented land. Facebook organic reach fell from ~20% to under 2%; any rented channel can throttle you overnight.
389- **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.
391For the full distribution spine—the Content Distribution Flywheel, platform half-lives, and the atomization checklist—see the reference below.
393---

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.


Raw lines 372 to 394
Names a skill launch :384
395## Output Format
397When creating a content strategy, provide:

Output Format

When creating a content strategy, provide:

Raw lines 395 to 398
399### 1. Content Pillars
400- 3-5 pillars with rationale
401- Subtopic clusters for each pillar
402- How pillars connect to product

1. Content Pillars

  • 3-5 pillars with rationale
  • Subtopic clusters for each pillar
  • How pillars connect to product
Raw lines 399 to 403
404### 2. Priority Topics
405For each recommended piece:
406- Topic/title
407- Searchable, shareable, or both
408- Content type (use-case, hub/spoke, thought leadership, etc.)
409- Target keyword and buyer stage
410- Why this topic (customer research backing)

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)
Raw lines 404 to 411
412### 3. Topic Cluster Map
413Visual or structured representation of how content interconnects.
415---

3. Topic Cluster Map

Visual or structured representation of how content interconnects.


Raw lines 412 to 416
417## Task-Specific Questions
4191. What patterns emerge from your last 10 customer conversations?
4202. What questions keep coming up in sales calls?
4213. Where are competitors' content efforts falling short?
4224. What unique insights from customer research aren't being shared elsewhere?
4235. Which existing content drives the most conversions, and why?
425---

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?

Raw lines 417 to 426
427## References
429- **[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
430- **[Headless CMS Guide](references/headless-cms.md)**: CMS selection, content modeling for marketing, editorial workflows, platform comparison (Sanity, Contentful, Strapi)
432---

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)

Raw lines 427 to 433
434## Related Skills
436- **copywriting**: For writing individual content pieces
437- **seo-audit**: For technical SEO and on-page optimization
438- **link-building**: For earning links to the content and the pages it supports
439- **ai-seo**: For optimizing content for AI search engines and getting cited by LLMs
440- **programmatic-seo**: For scaled content generation
441- **site-architecture**: For page hierarchy, navigation design, and URL structure
442- **emails**: For email-based content
443- **social**: For social media content, content atomization, and repurposing execution
444- **launch**: For the ORB channel-type playbook and launch-day distribution

Related Skills

  • copywriting: For writing individual content pieces
  • seo-audit: For technical SEO and on-page optimization
  • link-building: For earning links to the content and the pages it supports
  • 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
Raw lines 434 to 444
Names a skill site-architecture :441

From coreyhaines31/marketingskills at 88c79f6, 2026-10-30. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.