skills/content-strategy/SKILL.md
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-content.
npx skillsauth add cenjie/skills content-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md 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):
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.
Use-Case Content Formula: [persona] + [use-case]. Targets long-tail keywords.
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.
Thought Leadership
Data-Driven Content
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."
For programmatic content at scale, see programmatic-seo skill.
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.
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
Good pillars should:
Map topics to the buyer's journey using proven keyword modifiers:
Modifiers: "what is," "how to," "guide to," "introduction to"
Example: If customers ask about project management basics:
Modifiers: "best," "top," "vs," "alternatives," "comparison"
Example: If customers evaluate multiple tools:
Modifiers: "pricing," "reviews," "demo," "trial," "buy"
Example: If pricing comes up in sales calls:
Modifiers: "templates," "examples," "tutorial," "how to use," "setup"
Example: If support tickets show implementation struggles:
If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:
Output as prioritized table: | Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |
If user provides sales or customer call transcripts, extract:
Output content ideas with supporting quotes.
If user provides survey data, mine for:
Use web search to find content ideas:
Reddit: site:reddit.com [topic]
Quora: site:quora.com [topic]
Other: Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord
Extract: FAQs, misconceptions, debates, problems being solved, terminology used.
Use web search to analyze competitor content:
Find their content: site:competitor.com/blog
Analyze:
Identify opportunities:
Extract from customer-facing teams:
Score each idea on four factors:
| Idea | Customer Impact (40%) | Content-Market Fit (30%) | Search Potential (20%) | Resources (10%) | Total | |------|----------------------|-------------------------|----------------------|-----------------|-------| | Topic A | 8 | 9 | 7 | 6 | 8.0 | | Topic B | 6 | 7 | 9 | 8 | 7.1 |
When creating a content strategy, provide:
For each recommended piece:
Visual or structured representation of how content interconnects.
development
Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.
development
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.
development
General-purpose Static Application Security Testing (SAST) skill for code vulnerability analysis. Trigger when the user asks to: "analyze code for vulnerabilities", "review code security", "find security bugs", "do a SAST scan", "check for [vulnerability type] in code", "audit source code", or requests a security code review of any language or framework. Covers 34 vulnerability classes across web, API, auth, mobile, and logic layers.
tools
Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation.