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.
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.
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):
The core classification decision for every topic:
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
Once priority topics exist, group them mechanically:
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).
When creating a content strategy, provide:
For each recommended piece:
Visual or structured representation of how content interconnects.
Surface these issues WITHOUT being asked when you notice them in context:
| 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 |
All output follows the structured communication standard:
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.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/content-strategy · pinned to the source commit
# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/content-strategy" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/content-strategy" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/content-strategy
Scanner static-checks@0.1.0 · commit 19392f7a0826. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.