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 when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.

26 stars

Best use case

content-strategy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.

Teams using content-strategy should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/content-strategy/SKILL.md --create-dirs "https://raw.githubusercontent.com/TerminalSkills/skills/main/skills/content-strategy/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/content-strategy/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How content-strategy Compares

Feature / Agentcontent-strategyStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Content Strategy

## Overview

You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both. You guide users through context gathering, content pillar selection, topic ideation, prioritization, and editorial planning.

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

## Instructions

### Gather Context First

Ask for what's not already provided:

1. **Business Context** - What does the company do? Who is the ideal customer? Primary goal for content? What problems does the product solve?
2. **Customer Research** - Questions customers ask before buying? Sales objections? Support ticket patterns? Language customers use?
3. **Current State** - Existing content and what's working? Resources (writers, budget, time)? Content formats possible?
4. **Competitive Landscape** - Main competitors? Content gaps in the market?

### Searchable vs Shareable Content

Every piece must be searchable, shareable, or both. Prioritize search — it's the foundation.

**Searchable content** captures existing demand:
- Target a specific keyword or question
- Match search intent exactly
- Structure with headings that mirror search patterns
- Provide comprehensive coverage
- Optimize for AI/LLM discovery: clear positioning, structured content, brand consistency

**Shareable content** creates demand:
- Lead with novel insight, original data, or counterintuitive take
- Challenge conventional wisdom with well-reasoned arguments
- Tell stories that make people feel something
- Connect to current trends or emerging problems

### Content Types

**Searchable Types:**
- **Use-Case Content**: [persona] + [use-case] targeting long-tail keywords (e.g., "Project management for designers")
- **Hub and Spoke**: Hub = comprehensive overview, spokes = related subtopics. Most content works under `/blog`; only use dedicated hub URL structures for major topics with layered depth.
- **Template Libraries**: High-intent keywords + product adoption. Provide standalone value, show how product enhances it.

**Shareable Types:**
- **Thought Leadership**: Articulate concepts everyone feels but hasn't named. Challenge conventional wisdom.
- **Data-Driven Content**: Product data analysis, public data patterns, original research.
- **Case Studies**: Challenge → Solution → Results → Key learnings.
- **Meta Content**: Behind-the-scenes transparency ("How We Got Our First $5k MRR").

### Content Pillars and Topic Clusters

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

**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?

Good pillars align with your product, match audience interests, have search volume, and are broad enough for many subtopics.

### Keyword Research by Buyer Stage

- **Awareness**: "what is," "how to," "guide to" — e.g., "What is Agile Project Management"
- **Consideration**: "best," "vs," "alternatives" — e.g., "Asana vs Trello vs Monday"
- **Decision**: "pricing," "reviews," "demo" — e.g., "Project Management Tool Pricing Comparison"
- **Implementation**: "templates," "tutorial," "how to use" — e.g., "Step-by-Step Setup Tutorial"

### Content Ideation Sources

1. **Keyword Data** (Ahrefs, SEMrush, GSC): Group into clusters, identify buyer stage, find quick wins (low competition + decent volume).
2. **Call Transcripts**: Extract questions, pain points, objections, language patterns, competitor mentions.
3. **Survey Responses**: Mine open-ended responses, common themes (30%+ = high priority), resource requests.
4. **Forum Research**: Reddit (`site:reddit.com [topic]`), Quora, Indie Hackers, HN — extract FAQs, misconceptions, debates.
5. **Competitor Analysis**: `site:competitor.com/blog` — top posts, gaps, outdated content to improve on.
6. **Sales and Support Input**: Common objections, repeated questions, ticket patterns, success stories.

### Prioritizing Content Ideas

Score each idea on four factors:

| Factor | Weight | What to Assess |
|--------|--------|----------------|
| Customer Impact | 40% | Frequency in research, % of customers affected, emotional charge, LTV of audience |
| Content-Market Fit | 30% | Alignment with product, unique insights available, customer stories, natural product interest |
| Search Potential | 20% | Monthly volume, competition, long-tail opportunities, trend direction |
| Resource Requirements | 10% | Expertise available, research needed, assets required |

### Output Format

Provide:
1. **Content Pillars** - 3-5 pillars with rationale, subtopic clusters, product connection.
2. **Priority Topics** - For each: topic/title, searchable or shareable, content type, target keyword, buyer stage, customer research backing.
3. **Topic Cluster Map** - How content interconnects.

## Examples

### Example 1: B2B SaaS Content Strategy

**User prompt:** "We're Opsline, a DevOps observability platform for mid-market engineering teams. Our ICP is VP of Engineering at 50-200 person companies. We have zero blog content and want to build organic traffic. Competitors are Datadog, New Relic, and Grafana."

The agent will:
- Propose 4 content pillars: Observability Fundamentals, Incident Management, DevOps Culture, and Tool Comparisons.
- Create a prioritized list of 15-20 topics mapped to buyer stages, starting with high-intent consideration content ("Datadog alternatives for mid-market teams," "Datadog vs New Relic vs Opsline") and awareness content ("Guide to observability vs monitoring").
- Recommend starting with 3 comparison pages (targeting competitor search terms) and 2 hub-and-spoke guides (observability, incident management) in the first quarter.
- Provide a topic cluster map showing how articles interlink.

### Example 2: E-commerce Content Strategy from Customer Research

**User prompt:** "I run GreenPaws, an organic pet food DTC brand. Here are our last 20 customer support tickets and 5 sales call transcripts. Our customers keep asking about ingredient sourcing, how to transition their dog's food, and whether organic actually matters. Help me plan content."

The agent will:
- Analyze the transcripts and tickets to extract key themes: ingredient transparency (mentioned in 14/20 tickets), food transition anxiety (8/20), organic vs conventional debate (6/20), breed-specific nutrition (5/20).
- Propose 3 pillars: Organic Pet Nutrition (search-led), Ingredient Transparency (brand-led, shareable), Dog Health by Life Stage (audience-led).
- Prioritize "How to Switch Your Dog's Food Without Stomach Issues" as the #1 article (high customer impact, strong search volume, addresses the most common support question).
- Map 12 initial topics with exact customer language from transcripts used in titles and angles.

## Guidelines

- **Always prioritize search-first content** for the first 6-12 months — shareable content is harder to predict and search traffic compounds over time.
- **Don't create content pillars around your product features** — pillars should map to problems your audience has, not solutions you sell.
- **Use customer language, not company language** — if customers say "tracking hours" and you say "time management optimization," use their words.
- **Start with consideration-stage content** if you need leads fast — "best X for Y" and comparison content captures buyers closer to a decision.
- **Every piece needs a clear "so what"** — before writing anything, answer: "Why would our ICP care about this more than the 10 other articles on this topic?"
- **Don't spread too thin** — 4 excellent articles per month beats 12 mediocre ones. Depth and quality build topical authority faster than volume.
- **Refresh content on a schedule** — set quarterly reviews for high-performing pages. Search engines reward freshness, and outdated stats or broken links erode rankings.

Related Skills

social-content

26
from TerminalSkills/skills

When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies.

product-strategy

26
from TerminalSkills/skills

Expert guidance for product strategy, helping product leaders define product vision, craft positioning, analyze competitive landscapes, choose pricing models, and build outcome-driven roadmaps. Applies frameworks from Marty Cagan (Empowered), April Dunford (Obviously Awesome), Gibson Biddle (DHM Model), and Reforge.

pricing-strategy

26
from TerminalSkills/skills

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.

launch-strategy

26
from TerminalSkills/skills

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

free-tool-strategy

26
from TerminalSkills/skills

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.

contentful

26
from TerminalSkills/skills

You are an expert in Contentful, the API-first content platform for enterprise teams. You help developers integrate Contentful's Content Delivery API (CDN-backed, read), Content Management API (write), and Content Preview API (draft content) into websites and apps — using typed content models, localization, rich text rendering, image transformations, and webhooks for build triggers.

content-writer

26
from TerminalSkills/skills

Research topics and write content like blog posts, articles, and marketing copy. Use when a user asks to write a blog post, create an article, draft marketing copy, write website content, create a newsletter, produce thought leadership content, or write any long-form or short-form copy.

cache-strategy

26
from TerminalSkills/skills

Design and implement caching layers for APIs and web applications using Redis or Memcached. Use when you need to reduce database load, improve response times, or handle traffic spikes. Covers cache-aside, write-through, and write-behind patterns, TTL strategies, cache invalidation, and stampede prevention. Trigger words: cache, Redis, Memcached, TTL, cache invalidation, response time, throughput, rate limiting.

ai-content-monetization

26
from TerminalSkills/skills

Automate online content creation and monetization with AI — blog posts, videos, social media, affiliate marketing, and digital products. Use when: building passive income streams with AI, automating content marketing, scaling content production.

ai-content-detection

26
from TerminalSkills/skills

Detect AI-generated text using rule-based analysis, LLM-as-judge scoring, and optional external APIs. Use when: auditing content for AI authorship, academic integrity checks, editorial review, SEO content audits.

zustand

26
from TerminalSkills/skills

You are an expert in Zustand, the small, fast, and scalable state management library for React. You help developers manage global state without boilerplate using Zustand's hook-based stores, selectors for performance, middleware (persist, devtools, immer), computed values, and async actions — replacing Redux complexity with a simple, un-opinionated API in under 1KB.

zoho

26
from TerminalSkills/skills

Integrate and automate Zoho products. Use when a user asks to work with Zoho CRM, Zoho Books, Zoho Desk, Zoho Projects, Zoho Mail, or Zoho Creator, build custom integrations via Zoho APIs, automate workflows with Deluge scripting, sync data between Zoho apps and external systems, manage leads and deals, automate invoicing, build custom Zoho Creator apps, set up webhooks, or manage Zoho organization settings. Covers Zoho CRM, Books, Desk, Projects, Creator, and cross-product integrations.