Creator Β· coreyhaines31
Last updated Β· Sep 2, 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 c
Creator Β· coreyhaines31
Last updated Β· Sep 2, 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 c
Creator Β· coreyhaines31
Last updated Β· Sep 2, 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 c
Creator Β· coreyhaines31
Last updated Β· Sep 2, 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 c
Review then install
Install targets
Codex install prompt
Install the "content-strategy" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/content-strategy. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"coreyhaines31-content-strategy","task":"Install content-strategy","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
SEO, content operations, lead generation, CRM, email automation, analytics, and growth workflows.
Scenario
Content automation
I need my agent to turn research and product updates into useful content drafts.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add coreyhaines31/marketingskills --skill content-strategy
Maintenance
fresh
4d since push
Risk
Needs review
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
47K
93/100 Quality Β· 89/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision Β· Financial research output is not financial advice; require human review before any live investment decision.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
ExcellentHigh-confidence pick with strong adoption and healthy maintenance signals.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
47K GitHub stars
Repo activity
47K stars, 7.3K forks
Maintenance
4d since push
License
MIT
Install
npx skills add coreyhaines31/marketingskills --skill content-strategy
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add coreyhaines31/marketingskills --skill content-strategyDo not use when
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/coreyhaines31-content-strategy/install
Agent should check
Copy prompt
Task: Use content-strategy in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/coreyhaines31-content-strategy/install
Install command: npx skills add coreyhaines31/marketingskills --skill content-strategy
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/coreyhaines31-content-strategy/install
LLM text format
/api/skills/coreyhaines31-content-strategy/install?format=text
Find alternatives
/api/skills/search?q=content-strategy&limit=3
Agent prompt
Use content-strategy for this task. Review https://www.openagentskill.com/api/skills/coreyhaines31-content-strategy/install, then install with: npx skills add coreyhaines31/marketingskills --skill content-strategyRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/coreyhaines31-content-strategy
LLM text
/api/registry/manifest/coreyhaines31-content-strategy?format=text
Install alias
/api/registry/install/coreyhaines31-content-strategy
Recommend
/api/registry/recommend?task=Use%20content-strategy%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS47K GitHub stars
Stars/forks activity
PASS47K stars, 7.3K forks; issue activity unavailable in current metadata
Recent maintenance
PASS4d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
High-confidence pick with strong adoption and healthy maintenance signals.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Grow distribution
I need my agent to research keywords, improve SEO, analyze growth channels, and prepare marketing workflows.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
π΅οΈββοΈ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- 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):
### 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."
### 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:
| 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 wit
Source provenance
Decision snapshot
46,626 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for content-strategy, ready for a manual X post.
A practical pick for market research: content-strategy: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use... 46.6K stars https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=x
Listing + install path for content-strategy: https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=x Install: npx skills add coreyhaines31/marketingskills --skill content-strategy
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to coreyhaines31 but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy/audit)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)coreyhaines31
@coreyhaines31
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
π΅οΈββοΈ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsReview then install
Install targets
Codex install prompt
Install the "content-strategy" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/content-strategy. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"coreyhaines31-content-strategy","task":"Install content-strategy","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
SEO, content operations, lead generation, CRM, email automation, analytics, and growth workflows.
Scenario
Content automation
I need my agent to turn research and product updates into useful content drafts.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add coreyhaines31/marketingskills --skill content-strategy
Maintenance
fresh
4d since push
Risk
Needs review
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
47K
93/100 Quality Β· 89/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision Β· Financial research output is not financial advice; require human review before any live investment decision.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
ExcellentHigh-confidence pick with strong adoption and healthy maintenance signals.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
47K GitHub stars
Repo activity
47K stars, 7.3K forks
Maintenance
4d since push
License
MIT
Install
npx skills add coreyhaines31/marketingskills --skill content-strategy
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add coreyhaines31/marketingskills --skill content-strategyDo not use when
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/coreyhaines31-content-strategy/install
Agent should check
Copy prompt
Task: Use content-strategy in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/coreyhaines31-content-strategy/install
Install command: npx skills add coreyhaines31/marketingskills --skill content-strategy
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/coreyhaines31-content-strategy/install
LLM text format
/api/skills/coreyhaines31-content-strategy/install?format=text
Find alternatives
/api/skills/search?q=content-strategy&limit=3
Agent prompt
Use content-strategy for this task. Review https://www.openagentskill.com/api/skills/coreyhaines31-content-strategy/install, then install with: npx skills add coreyhaines31/marketingskills --skill content-strategyRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/coreyhaines31-content-strategy
LLM text
/api/registry/manifest/coreyhaines31-content-strategy?format=text
Install alias
/api/registry/install/coreyhaines31-content-strategy
Recommend
/api/registry/recommend?task=Use%20content-strategy%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS47K GitHub stars
Stars/forks activity
PASS47K stars, 7.3K forks; issue activity unavailable in current metadata
Recent maintenance
PASS4d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
High-confidence pick with strong adoption and healthy maintenance signals.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Grow distribution
I need my agent to research keywords, improve SEO, analyze growth channels, and prepare marketing workflows.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
π΅οΈββοΈ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- 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):
### 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."
### 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:
| 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 wit
Source provenance
Decision snapshot
46,626 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for content-strategy, ready for a manual X post.
A practical pick for market research: content-strategy: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use... 46.6K stars https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=x
Listing + install path for content-strategy: https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=x Install: npx skills add coreyhaines31/marketingskills --skill content-strategy
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to coreyhaines31 but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy/audit)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)coreyhaines31
@coreyhaines31
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
π΅οΈββοΈ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsReview then install
Install targets
Codex install prompt
Install the "content-strategy" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/content-strategy. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"coreyhaines31-content-strategy","task":"Install content-strategy","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
SEO, content operations, lead generation, CRM, email automation, analytics, and growth workflows.
Scenario
Content automation
I need my agent to turn research and product updates into useful content drafts.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add coreyhaines31/marketingskills --skill content-strategy
Maintenance
fresh
4d since push
Risk
Needs review
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
47K
93/100 Quality Β· 89/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision Β· Financial research output is not financial advice; require human review before any live investment decision.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
ExcellentHigh-confidence pick with strong adoption and healthy maintenance signals.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
47K GitHub stars
Repo activity
47K stars, 7.3K forks
Maintenance
4d since push
License
MIT
Install
npx skills add coreyhaines31/marketingskills --skill content-strategy
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add coreyhaines31/marketingskills --skill content-strategyDo not use when
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/coreyhaines31-content-strategy/install
Agent should check
Copy prompt
Task: Use content-strategy in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/coreyhaines31-content-strategy/install
Install command: npx skills add coreyhaines31/marketingskills --skill content-strategy
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/coreyhaines31-content-strategy/install
LLM text format
/api/skills/coreyhaines31-content-strategy/install?format=text
Find alternatives
/api/skills/search?q=content-strategy&limit=3
Agent prompt
Use content-strategy for this task. Review https://www.openagentskill.com/api/skills/coreyhaines31-content-strategy/install, then install with: npx skills add coreyhaines31/marketingskills --skill content-strategyRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/coreyhaines31-content-strategy
LLM text
/api/registry/manifest/coreyhaines31-content-strategy?format=text
Install alias
/api/registry/install/coreyhaines31-content-strategy
Recommend
/api/registry/recommend?task=Use%20content-strategy%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS47K GitHub stars
Stars/forks activity
PASS47K stars, 7.3K forks; issue activity unavailable in current metadata
Recent maintenance
PASS4d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
High-confidence pick with strong adoption and healthy maintenance signals.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Grow distribution
I need my agent to research keywords, improve SEO, analyze growth channels, and prepare marketing workflows.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
π΅οΈββοΈ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- 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):
### 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."
### 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:
| 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 wit
Source provenance
Decision snapshot
46,626 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for content-strategy, ready for a manual X post.
A practical pick for market research: content-strategy: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use... 46.6K stars https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=x
Listing + install path for content-strategy: https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=x Install: npx skills add coreyhaines31/marketingskills --skill content-strategy
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to coreyhaines31 but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy/audit)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)coreyhaines31
@coreyhaines31
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
π΅οΈββοΈ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsReview then install
Install targets
Codex install prompt
Install the "content-strategy" agent skill from https://github.com/coreyhaines31/marketingskills/tree/main/skills/content-strategy. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"coreyhaines31-content-strategy","task":"Install content-strategy","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
SEO, content operations, lead generation, CRM, email automation, analytics, and growth workflows.
Scenario
Content automation
I need my agent to turn research and product updates into useful content drafts.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add coreyhaines31/marketingskills --skill content-strategy
Maintenance
fresh
4d since push
Risk
Needs review
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
47K
93/100 Quality Β· 89/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision Β· Financial research output is not financial advice; require human review before any live investment decision.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
ExcellentHigh-confidence pick with strong adoption and healthy maintenance signals.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
47K GitHub stars
Repo activity
47K stars, 7.3K forks
Maintenance
4d since push
License
MIT
Install
npx skills add coreyhaines31/marketingskills --skill content-strategy
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add coreyhaines31/marketingskills --skill content-strategyDo not use when
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/coreyhaines31-content-strategy/install
Agent should check
Copy prompt
Task: Use content-strategy in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20content-strategy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/coreyhaines31-content-strategy/install
Install command: npx skills add coreyhaines31/marketingskills --skill content-strategy
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/coreyhaines31-content-strategy/install
LLM text format
/api/skills/coreyhaines31-content-strategy/install?format=text
Find alternatives
/api/skills/search?q=content-strategy&limit=3
Agent prompt
Use content-strategy for this task. Review https://www.openagentskill.com/api/skills/coreyhaines31-content-strategy/install, then install with: npx skills add coreyhaines31/marketingskills --skill content-strategyRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/coreyhaines31-content-strategy
LLM text
/api/registry/manifest/coreyhaines31-content-strategy?format=text
Install alias
/api/registry/install/coreyhaines31-content-strategy
Recommend
/api/registry/recommend?task=Use%20content-strategy%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS47K GitHub stars
Stars/forks activity
PASS47K stars, 7.3K forks; issue activity unavailable in current metadata
Recent maintenance
PASS4d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
High-confidence pick with strong adoption and healthy maintenance signals.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Grow distribution
I need my agent to research keywords, improve SEO, analyze growth channels, and prepare marketing workflows.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
π΅οΈββοΈ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- 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):
### 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."
### 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:
| 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 wit
Source provenance
Decision snapshot
46,626 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for content-strategy, ready for a manual X post.
A practical pick for market research: content-strategy: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use... 46.6K stars https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=x
Listing + install path for content-strategy: https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=x Install: npx skills add coreyhaines31/marketingskills --skill content-strategy
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to coreyhaines31 but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy/audit)
[](https://www.openagentskill.com/skills/coreyhaines31-content-strategy?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)coreyhaines31
@coreyhaines31
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
π΅οΈββοΈ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsPermission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness