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.
MCP get_skill({ skillId: "content-strategy-06022c0d" })Use this skill with your agent
Create a free account and connect via MCP
# 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 `.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. Gather this context (ask if not provided): ### 1. Business Context - What does the company do? - Who is the ideal customer? - What's the primary goal for content? (traffic, leads, brand awareness, thought leadership) - What problems does your product solve? ### 2. Customer Research - What questions do customers ask before buying? - What objections come up in sales calls? - What topics appear repeatedly in support tickets? - What language do customers use to describe their problems? ### 3. Current State - Do you have existing content? What's working? - What resources do you have? (writers, budget, time) - What content formats can you produce? (written, video, audio) ### 4. Competitive Landscape - Who are your main competitors? - What content gaps exist in your market? --- ## Searchable vs Shareable The core classification decision for every topic: - **Searchable** — people already query this (keyword volume exists). Goal: rank and convert. Format: use-case pages, comparisons, how-tos, hub/spoke clusters. Judged by rankings + organic conversions over 6-12 months. - **Shareable** — nobody searches it yet, but it spreads (original data, contrarian POV, strong narrative). Goal: reach + links + brand. Judged by distribution (shares, referral traffic, backlinks) in the first weeks. **Decision rule:** if the topic has meaningful search volume AND clear buyer intent → searchable (build it into a cluster). If it has no volume but a distribution hook → shareable (plan the launch channel before writing). If both → searchable structure with a shareable angle (best ROI). If neither → don't write it. Full treatment: references/content-strategy-reference.md ## Topic Cluster Mapping (bundled tool) Once priority topics exist, group them mechanically: ```bash python3 scripts/topic_cluster_mapper.py --file keywords.txt # one topic/keyword per line python3 scripts/topic_cluster_mapper.py --file keywords.txt --json # for pipelines ``` Its cluster output is the starting point for §3 Topic Cluster Map below — review cluster boundaries by intent (the tool groups lexically; you verify buyer-stage coherence). ## Output Format When creating a content strategy, provide: ### 1. Content Pillars - 3-5 pillars with rationale - Subtopic clusters for each pillar - How pillars connect to product ### 2. Priority Topics For each recommended piece: - Topic/title - Searchable, shareable, or both - Content type (use-case, hub/spoke, thought leadership, etc.) - Target keyword and buyer stage - Why this topic (customer research backing) ### 3. Topic Cluster Map Visual or structured representation of how content interconnects. --- ## Task-Specific Questions 1. What patterns emerge from your last 10 customer conversations? 2. What questions keep coming up in sales calls? 3. Where are competitors' content efforts falling short? 4. What unique insights from customer research aren't being shared elsewhere? 5. Which existing content drives the most conversions, and why? --- ## Proactive Triggers Surface these issues WITHOUT being asked when you notice them in context: - **No content plan exists** → Immediately propose a 3-pillar starter strategy with 10 seed topics before asking more questions. - **User has content but low traffic** → Flag the searchable vs. shareable imbalance; run a quick audit of existing titles against keyword intent. - **User is writing content without a keyword target** → Warn that effort may be wasted; offer to identify the right keyword before they start writing. - **Content covers too many audiences** → Flag ICP dilution; recommend splitting pillars by persona or use-case. - **Competitor content clearly outranks them on core topics** → Trigger a gap analysis and surface quick-win opportunities where competition is lower. --- ## Output Artifacts | When you ask for... | You get... | |---------------------|------------| | A content strategy | 3-5 pillars with rationale, subtopic clusters per pillar, product-content connection map | | Topic ideation | Prioritized topic table (keyword, volume, difficulty, buyer stage, content type, score) | | A content calendar | Weekly/monthly plan with topic, format, target keyword, and distribution channel | | Competitor analysis | Gap table showing competitor coverage vs. your coverage with opportunity ratings | | A content brief | Single-page brief: goal, audience, keyword, outline, CTA, internal links, proof points | --- ## Communication All output follows the structured communication standard: - **Bottom line first** — recommendation before rationale - **What + Why + How** — every strategy has all three - **Actions have owners and deadlines** — no "you might consider" - **Confidence tagging** — 🟢 high confidence / 🟡 medium / 🔴 assumption Output format defaults: tables for prioritization, bullet lists for options, prose for rationale. Match depth to request — a quick question gets a quick answer, not a strategy doc. --- ## Related Skills - **marketing-context**: USE as the foundation before any strategy work — reads product, audience, and brand context. NOT a substitute for this skill. - **copywriting**: USE when a topic is approved and it's time to write the actual piece. NOT for deciding what to write about. - **copy-editing**: USE to polish content drafts after writing. NOT for planning or strategy decisions. - **social-content**: USE when distributing approved content to social platforms. NOT for organic search strategy. - **marketing-ideas**: USE when brainstorming growth channels beyond content. NOT for deep keyword or topic planning. - **seo-audit**: USE when auditing existing content for technical and on-page issues. NOT for creating new strategy from scratch. - **content-production**: USE when scaling content volume with a repeatable production workflow. NOT for initial strategy definition. - **content-humanizer**: USE when AI-generated content needs to sound more authentic. NOT for topic selection.
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Agent Protocol
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
Agile Product Owner
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.
Board Deck Builder
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.