content-strategy · alirezarezvani — Claude Code skill: what it does, how to install
This skill plans content strategy, selects topics, and maps clusters to product goals. Use it when you need a blog plan or a clear list of content priorities.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install marketing-skills@claude-code-skillsWhat content-strategy does
content-strategy helps decide what to create, which audience questions to address, and how each topic connects to the product. It gathers business, customer, existing-content, and competitor context, then classifies ideas as searchable or shareable. Each recommendation includes a format, target keyword, buyer stage, and reason for choosing the topic.
The skill produces content pillars, priority topics, and a structured topic-cluster map. Its bundled script groups keywords from a file such as keywords.txt; JSON output is available with python3 scripts/topic_cluster_mapper.py --file keywords.txt --json. When .claude/product-marketing-context.md exists, the skill reads it before asking for more context.
Install it when the main question is what to write and how to organize the subjects. Use copywriting for an individual piece and seo-audit for an SEO review of existing content.
What it helps with
- choose priority topics for a content plan
- classify ideas as searchable or shareable
- group keywords from
keywords.txt - connect topics to buyer stages
- spot gaps in competitor content
Example prompts for the agent
- Plan a content strategy for our product and rank the priority topics.
- Run `python3 scripts/topic_cluster_mapper.py --file keywords.txt --json` and show the topic clusters.
- Review our current content and flag topics that should be searchable or shareable.
How to install content-strategy
1Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install marketing-skills@claude-code-skillsThis installs the whole marketing-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add alirezarezvani/claude-skills --skill content-strategy -a claude-code3Manually: put the files in place
~/.claude/skills/content-strategy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/content-strategy/
Manually: put the files in place
.agents/skills/content-strategy/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/content-strategy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install alirezarezvani/claude-skills content-strategy2Manually: put the files in place
.github/skills/content-strategy/SKILL.mdPlatform CLI
gemini skills install https://github.com/alirezarezvani/claude-skills --path marketing-skill/skills/content-strategyManually: put the files in place
.devin/skills/content-strategy/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set349
The whole set →Other versions of content-strategy
Similar
Questions about content-strategy
How do I install content-strategy in Claude Code?
Add the repository with /plugin marketplace add alirezarezvani/claude-skills, then install it with /plugin install marketing-skills@claude-code-skills.
What does content-strategy do?
It plans content, prioritizes topics, and groups them into clusters. The skill also connects topics with search demand, distribution, and buyer stage.
What do I need to group topics?
Use a keywords.txt file with one topic or keyword per line and Python to run scripts/topic_cluster_mapper.py. The skill can also read .claude/product-marketing-context.md for product context.
Source text
SKILL.md · MIT
--- 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,\" or \"content planning.\" For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit." license: MIT metadata: version: 1.0.0 author: Alireza Rezvani category: marketing updated: 2026-03-06 --- # 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.
© Alireza Rezvani · MIT · alirezarezvani/claude-skills