content-strategy
Verifiedby coreyhaines31 · Updated Apr 16, 2026
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-content.
See It In Action
Let me explore the project files first to understand your positioning and competitor data.
Now I have the full picture — positioning, competitor analysis, keyword data, and pipeline metrics. Let me build the strategy.
doany.ai Q3 2026 Content Strategy
Strategic Summary
Goal: Grow content-attributed pipeline from 8% → 20% of total by September 30, 2026.
Core problem: doany.ai has zero consideration or decision-stage content. 60% of MQLs come from paid ads with rising CAC. The existing content library is almost entirely product announcements that generate no sustained traffic or pipeline.
The fix: Flood the funnel with searchable, high-intent content that captures buyers already evaluating AI automation tools. Prioritize comparison pages, use-case content, and bottom-of-funnel assets — the content types that directly convert to pipeline. Exploit the keyword gaps every competitor is ignoring.
Q3 output: 26 pieces (2x/week for 13 weeks), split roughly 70% searchable / 20% searchable+shareable / 10% shareable.
Content Pillars (4)
Pillar 1: AI Automation Comparisons & Alternatives
Why it matters: Zero comparison content exists today. These are the highest-intent keywords in the funnel — searchers are actively evaluating tools. Every competitor except Make ignores this content type. This pillar alone could drive the largest pipeline impact.
Target audience: Ops/RevOps leaders comparing tools, technical founders evaluating build-vs-buy.
Mix: 100% searchable
Keyword cluster:
| Keyword | Volume | KD | Priority |
|---|---|---|---|
| zapier alternative for ai | 720 | 28 | High |
| best ai automation tools 2026 | 1,600 | 45 | High |
| ai automation vs zapier | 480 | 22 | High |
| make vs zapier for ai workflows | 440 | 20 | High |
| ai automation pricing comparison | 290 | 16 | High |
| ai workflow automation tools | 1,200 | 38 | High |
Pillar 2: AI Workflow Use Cases by Persona
Why it matters: Use-case content targets long-tail, commercial-intent keywords and maps directly to buyer personas. Competitors are either too generic (Relevance AI) or too technical (n8n). doany.ai can own the "[persona] + [AI use case]" space for ops teams.
Target audience: Head of Ops, Marketing Ops leads, RevOps managers.
Mix: 90% searchable / 10% shareable
Keyword cluster:
| Keyword | Volume | KD | Priority |
|---|---|---|---|
| ai automation for marketing teams | 680 | 29 | High |
| ai document processing automation | 960 | 30 | High |
| automate lead enrichment ai | 340 | 21 | High |
| ai workflow automation for ops teams | 320 | 15 | High |
| ai powered document workflows | 420 | 24 | Medium |
| workflow automation with approval gates | 180 | 10 | Medium |
Pillar 3: ROI, Business Case & Trust
Why it matters: This is the decision-stage content that Dex specifically asked for (3 bottom-of-funnel assets minimum). No competitor publishes ROI or business-case content. This pillar directly addresses the #1 sales objection ("How do we justify the cost?") and builds the enterprise trust content that's missing across the market.
Target audience: Budget holders — VP Ops, COO, CFO, technical founders doing build-vs-buy math.
Mix: 60% searchable / 40% searchable+shareable
Keyword cluster:
| Keyword | Volume | KD | Priority |
|---|---|---|---|
| ai automation roi calculator | 210 | 12 | High |
| ai automation case studies | 280 | 14 | High |
| enterprise ai workflow automation | 510 | 40 | High |
| ai automation security compliance soc2 | 150 | 8 | Medium |
| ai workflow builder no code | 650 | 31 | Medium |
Pillar 4: Human-in-the-Loop AI (Thought Leadership)
Why it matters: This is doany.ai's strongest differentiator — every competitor either ignores HITL or bolts it on as an afterthought. Nobody ranks for these terms. Owning this narrative positions doany.ai as the trusted choice and creates shareable content that builds authority while also capturing search traffic.
Target audience: Ops leaders who don't trust fully autonomous AI, enterprise buyers with compliance concerns.
Mix: 50% searchable / 50% shareable
Keyword cluster:
| Keyword | Volume | KD | Priority |
|---|---|---|---|
| human in the loop ai automation | 390 | 18 | High |
| how to automate workflows with ai | 1,400 | 33 | Medium |
Q3 Content Calendar (26 Pieces)
Month 1: July 2026 — Capture Consideration-Stage Demand
Focus: Comparison pages and quick-win keywords. These are the fastest path to pipeline because they target buyers already evaluating solutions.
| Week | Title | Pillar | Type | Target Keyword | Buyer Stage | S/S |
|---|---|---|---|---|---|---|
| W1 | doany.ai vs Zapier: Which AI Automation Platform Is Right for You? | 1 | Comparison | zapier alternative for ai (720, KD 28) | Consideration | Searchable |
| W1 | How to Automate Lead Enrichment with AI (Step-by-Step) | 2 | Use-case | automate lead enrichment ai (340, KD 21) | Awareness | Searchable |
| W2 | doany.ai vs Make: AI Workflow Automation Compared | 1 | Comparison | make vs zapier for ai workflows (440, KD 20) | Consideration | Searchable |
| W2 | AI Workflow Automation for Ops Teams: 5 Workflows to Start Today | 2 | Use-case | ai workflow automation for ops teams (320, KD 15) | Consideration | Searchable |
| W3 | The Best AI Automation Tools in 2026 (Honest Comparison) | 1 | Listicle | best ai automation tools 2026 (1,600, KD 45) | Consideration | Searchable |
| W3 | AI Automation ROI Calculator: Measure What Your Workflows Actually Save | 3 | Interactive tool + post | ai automation roi calculator (210, KD 12) | Decision | Searchable |
| W4 | doany.ai vs Relevance AI: Human Control vs. Autonomous Agents | 1 | Comparison | — | Consideration | Searchable |
| W4 | AI Automation for Marketing Teams: From Lead Routing to Campaign Reporting | 2 | Use-case | ai automation for marketing teams (680, KD 29) | Awareness | Searchable |
July deliverables: 8 pieces — 4 comparison pages, 3 use-case articles, 1 ROI calculator (BoFu asset #1)
Month 2: August 2026 — Deepen Use Cases + Build Decision Content
Focus: Expand use-case content, publish case studies, and build the hub-spoke structure around the existing "Complete Guide" page.
| Week | Title | Pillar | Type | Target Keyword | Buyer Stage | S/S |
|---|---|---|---|---|---|---|
| W5 | How to Automate Document Processing with AI (No Code Required) | 2 | Use-case | ai document processing automation (960, KD 30) | Awareness | Searchable |
| W5 | AI Automation Pricing Compared: Zapier vs Make vs n8n vs doany.ai | 1 | Comparison | ai automation pricing comparison (290, KD 16) | Decision | Searchable |
| W6 | [Customer Name] Cut 20 Hours/Week of Manual Ops with doany.ai | 3 | Case study | ai automation case studies (280, KD 14) | Decision | Both |
| W6 | Why Trigger-Action Automation Isn't Enough for AI Workflows | 4 | Thought leadership | ai automation vs zapier (480, KD 22) | Consideration | Both |
| W7 | The No-Code AI Workflow Builder That Ops Teams Actually Use | 2 | Use-case | ai workflow builder no code (650, KD 31) | Consideration | Searchable |
| W7 | AI Workflow Automation Tools: How to Choose the Right Platform | 1 | Hub spoke | ai workflow automation tools (1,200, KD 38) | Consideration | Searchable |
| W8 | [Customer Name] Automated Lead Enrichment and Saved $4K/Month | 3 | Case study | — | Decision | Both |
| W8 | AI Workflow Automation with Approval Gates: Why Human Oversight Matters | 4 | Use-case + thought leadership | workflow automation with approval gates (180, KD 10) | Awareness | Both |
| W9 | doany.ai vs n8n: No-Code AI Automation vs. Developer-First Workflows | 1 | Comparison | n8n vs zapier ai automation (360, KD 19) | Consideration | Searchable |
August deliverables: 9 pieces — 3 comparison pages, 2 use-case articles, 2 case studies (BoFu assets #2-3), 2 thought leadership/HITL pieces
Month 3: September 2026 — Enterprise + Scale What's Working
Focus: Enterprise trust content, AI-powered document workflows, and double down on whatever's converting from July/August. Publish templates to capture implementation-stage traffic.
| Week | Title | Pillar | Type | Target Keyword | Buyer Stage | S/S |
|---|---|---|---|---|---|---|
| W10 | Enterprise AI Workflow Automation: Security, Compliance, and Scale | 3 | Enterprise trust | enterprise ai workflow automation (510, KD 40) | Consideration | Searchable |
| W10 | How to Build AI Workflows Without Writing Code | 2 | Tutorial | how to automate workflows with ai (1,400, KD 33) | Awareness | Searchable |
| W11 | AI Automation Security & SOC 2 Compliance: What Enterprise Buyers Need to Know | 3 | Enterprise trust | ai automation security compliance soc2 (150, KD 8) | Decision | Searchable |
| W11 | 10 AI Workflow Templates You Can Deploy in 5 Minutes | 2 | Template library | ai workflow templates (540, KD 25) | Implementation | Searchable |
| W12 | What 500 AI Workflows Taught Us About When Automation Fails | 4 | Data-driven thought leadership | human in the loop ai automation (390, KD 18) | Awareness | Shareable |
| W12 | AI-Powered Document Workflows: From Extraction to Action | 2 | Use-case | ai powered document workflows (420, KD 24) | Awareness | Searchable |
| W13 | How to Build an AI Automation Business Case Your CFO Will Approve | 3 | Business case guide | — | Decision | Searchable |
| W13 | The AI Workflow Automation Platform Buyers Guide (2026) | 1 | Hub spoke | ai workflow automation platform (880, KD 35) | Consideration | Searchable |
| W13 | How We Automate Our Own Marketing Ops with doany.ai | 4 | Meta/behind-the-scenes | — | Awareness | Shareable |
September deliverables: 9 pieces — 2 enterprise trust, 2 comparison/hub, 3 use-case, 1 data-driven thought leadership, 1 meta piece
Bottom-of-Funnel Assets (Dex's Requirement: 3 Minimum)
| # | Asset | Type | Target | Publish |
|---|---|---|---|---|
| 1 | AI Automation ROI Calculator | Interactive tool + blog post | Budget holders evaluating cost justification | July W3 |
| 2 | Case Study #1: [Customer] Cut 20 Hours/Week | Customer story with metrics | Ops leaders seeking proof | August W6 |
| 3 | Case Study #2: [Customer] Saved $4K/Month on Lead Enrichment | Customer story with metrics | Marketing/RevOps leaders | August W8 |
| 4 | AI Automation Business Case Template for CFOs | Downloadable guide | Enterprise buyers building internal cases | September W13 |
| 5 | AI Automation Platform Buyers Guide 2026 | Gated PDF | Mid-funnel leads evaluating tools | September W13 |
Note: Assets #4 and #5 are bonuses beyond the 3 minimum. Consider gating the Buyers Guide and Business Case Template behind email capture for direct lead gen.
Content Mix Summary
| Content Type | Count | % | Pipeline Impact |
|---|---|---|---|
| Comparison/vs pages | 7 | 27% | Highest — captures active evaluators |
| Use-case by persona | 8 | 31% | High — matches ICP search patterns |
| ROI/business case/case studies | 5 | 19% | High — decision-stage conversion |
| Thought leadership/HITL | 4 | 15% | Medium — builds authority + shares |
| Enterprise trust | 2 | 8% | Medium — unlocks enterprise pipeline |
By buyer stage:
- Awareness: 7 pieces (27%)
- Consideration: 11 pieces (42%)
- Decision: 6 pieces (23%)
- Implementation: 2 pieces (8%)
This is deliberately bottom-heavy. The current library is 100% top-of-funnel. Shifting to 65% consideration + decision stage content is what will move the pipeline needle.
Quick Wins: Publish First
These keywords have low difficulty and no competitors ranking. They should produce results fastest:
| Priority | Keyword | KD | Volume | Piece |
|---|---|---|---|---|
| 1 | ai automation roi calculator | 12 | 210 | ROI Calculator (July W3) |
| 2 | workflow automation with approval gates | 10 | 180 | Approval Gates piece (August W8) |
| 3 | ai automation security compliance soc2 | 8 | 150 | SOC 2 piece (September W11) |
| 4 | ai workflow automation for ops teams | 15 | 320 | Ops Teams piece (July W2) |
| 5 | ai automation pricing comparison | 16 | 290 | Pricing Comparison (August W5) |
| 6 | human in the loop ai automation | 18 | 390 | HITL data piece (September W12) |
Resource Allocation
Content marketer (full-time, ramped by July):
- Owns 2 pieces/week drafting and publishing
- Manages freelance assignments
- Updates and interlinks the existing "Complete Guide" hub with new spokes
- Builds CTAs and conversion paths into every piece
Dex (Head of Marketing):
- Reviews all comparison and thought leadership pieces
- Contributes byline on 2-3 thought leadership articles (HITL narrative, "What 500 Workflows Taught Us")
- Sources case study customers and conducts interviews
Freelance budget ($3,500/mo):
- July: 2 comparison page drafts ($1,200) + 1 use-case draft ($600) + ROI calculator copy ($500) = $2,300
- August: 2 case study interviews + drafts ($1,500) + 1 comparison draft ($600) = $2,100
- September: Enterprise trust pieces ($1,200) + Buyers Guide draft ($800) = $2,000
Design (5 hrs/week):
- Comparison page graphics (feature tables, side-by-side visuals)
- ROI calculator UI
- Case study layout
- Template library thumbnails
- Infographics for thought leadership pieces (1-2 per month)
Measurement Framework
Primary KPIs (report monthly)
| Metric | Current | July Target | Aug Target | Sep Target |
|---|---|---|---|---|
| Content-attributed MQLs | ~19/mo | 30 | 45 | 60+ |
| Content-attributed pipeline | $28K/mo | $50K | $80K | $100K+ |
| Content % of total pipeline | 8% | 12% | 16% | 20% |
| Organic traffic (monthly) | ~5,000 | 7,000 | 10,000 | 14,000 |
Secondary KPIs (track weekly)
- Keyword positions for target terms (track all 26 keywords from CSV)
- Comparison page conversion rate (visitor → demo request)
- ROI calculator completions
- Case study downloads / views
- Email captures from gated assets
When to expect results
- Comparison pages: Fastest impact. Low-KD terms should index and rank within 4-6 weeks. Expect first pipeline attribution from comparison pages by mid-August.
- Use-case content: 6-8 weeks to rank. Pipeline impact starts late August.
- Case studies / ROI calculator: Immediate pipeline impact when used by sales as deal collateral, even before SEO kicks in. Share with the sales team on publish day.
- Thought leadership: Slowest pipeline impact but builds the brand authority that makes everything else convert better. Expect social traction within 1-2 weeks, SEO impact within 2-3 months.
Monthly review questions
- Which pieces generated the most MQLs? Double down on that format.
- Which comparison pages have the highest conversion rate? Optimize the others to match.
- Are case studies being used by sales? If not, fix distribution, not content.
- What keywords moved into top 10? Build supporting content around them.
Internal Linking Strategy
Every new piece should link to at least 2 existing pieces. The hub structure:
AI Workflow Automation: Complete Guide (existing hub, position 4.2)
├── How to Automate Workflows with AI (spoke)
├── AI Document Processing Automation (spoke)
├── AI Workflow Automation for Ops Teams (spoke)
├── AI Automation for Marketing Teams (spoke)
└── AI Workflow Templates (spoke)
Comparison Hub: AI Workflow Automation Tools
├── doany.ai vs Zapier
├── doany.ai vs Make
├── doany.ai vs n8n
├── doany.ai vs Relevance AI
├── AI Automation Pricing Compared
└── Best AI Automation Tools 2026
ROI & Trust Hub: Enterprise AI Workflow Automation
├── AI Automation ROI Calculator
├── Case Study #1
├── Case Study #2
├── SOC 2 Compliance Guide
└── Business Case Template for CFOs
Every comparison page should CTA to the ROI calculator. Every use-case page should CTA to the relevant template and a case study. Every case study should link back to the relevant use-case and comparison pages.
Key Messaging to Weave Throughout
Use these angles consistently — they exploit competitor gaps:
- "AI workflows, not just triggers" — against Zapier/Make's simple if-this-then-that positioning
- "Human-in-the-loop by default" — against Relevance AI's fully autonomous agent framing
- "See what every workflow costs" — against everyone's opaque pricing/credit systems
- "No code required, enterprise grade" — against n8n's developer-only approach
- "200+ pre-built AI skills" — concrete number that dwarfs competitors' 20-50
Pull customer language directly into content:
- "We tried Zapier but it falls apart for anything beyond simple triggers"
- "I don't trust AI to handle this without someone checking the output"
- "My team spends half their week on reporting that should be automated"
What This Strategy Does NOT Include (Deliberately)
- Product announcements — these don't drive pipeline; save for the newsletter
- Generic "what is AI" awareness content — doany.ai already has the Complete Guide ranking; no need for more top-of-funnel fluff
- Social-first content — organic social is not the priority when content-attributed pipeline is at 8%; search-first
- Video/podcast — not enough resources; written content is the highest-leverage format right now
- Programmatic SEO — the "[app] + [app] integration" template pages are a good Q4 play once the content marketer is fully ramped and you have 40+ integration pages to generate
Permissions
| Scope | Description |
|---|---|
| filesystem:read | |
| network:outbound |
SKILL.md
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-context.md exists (or .claude/product-marketing-context.md 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?
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."
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
- Product-led: What problems does your product solve?
- Audience-led: What does your ICP need to learn?
- Search-led: What topics have volume in your space?
- 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 |
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
- What patterns emerge from your last 10 customer conversations?
- What questions keep coming up in sales calls?
- Where are competitors' content efforts falling short?
- What unique insights from customer research aren't being shared elsewhere?
- Which existing content drives the most conversions, and why?
References
- Headless CMS Guide: CMS selection, content modeling for marketing, editorial workflows, platform comparison (Sanity, Contentful, Strapi)
Related Skills
- 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
- email-sequence: For email-based content
- social-content: For social media content
FAQ
What does content-strategy do?
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-content.
When should I use content-strategy?
Use it when you need a repeatable workflow that produces text response.
What does content-strategy output?
In the evaluated run it produced text response.
How do I install or invoke content-strategy?
Ask the agent to use this skill when the task matches its documented workflow.
Which agents does content-strategy support?
Agent support is inferred from the source, but not explicitly declared.
What tools, channels, or permissions does content-strategy need?
It uses no extra tools; channels commonly include text; permissions include filesystem:read, network:outbound.
Is content-strategy safe to install?
Static analysis marked this skill as low risk; review side effects and permissions before enabling it.
How is content-strategy different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does content-strategy outperform not using a skill?
About content-strategy
When to use content-strategy
You need to decide what blog, SEO, or thought leadership content to create next. You want to turn customer research, keyword data, or competitor findings into a content roadmap. You need to organize topics into pillars, clusters, and buyer-stage content plans.
When content-strategy is not the right choice
You need the actual drafting of an individual article rather than strategic planning. You need specialized execution in external marketing platforms or analytics tools.
What it produces
Produces text response.