content-strategy▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Guides content strategy for SEO: topic clusters, pillar pages, cluster articles, and editorial planning. For content marketing across all channels (blog, email, social, video), see content-marketing. For translation workflow and multilingual content, see translation.
SEO Content: Content Strategy
Guides content strategy for SEO: topic clusters, pillar pages, cluster articles, and editorial planning. For content marketing across all channels (blog, email, social, video), see content-marketing. For translation workflow and multilingual content, see translation.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and proof points.
Identify:
- Keywords: From keyword research — see keyword-research for discovery and clustering
- Existing content: What already exists
- Resources: Content capacity, tools
- Goals: Traffic, conversions, authority
Product-Led SEO: Do SEO around product/users, not around industry/search engines. See seo-strategy for Product-Led SEO principle, products suited for SEO, and workflow order.
Topic Clusters
Topic clusters organize content by topic rather than isolated keywords. A pillar page covers a broad core topic; cluster articles cover subtopics; all connect via internal links. This signals topical authority to search engines and AI systems.
Structure
Pillar page (broad topic, 2,000-5,000+ words)
<-> internal links
Cluster 1 (subtopic, 800-2,500 words)
Cluster 2 (subtopic)
...
Cluster 6-12 (subtopics)
<-> cluster to cluster links
Pillar Page
| Attribute | Guideline |
|---|---|
| Length | 2,000-5,000+ words; comprehensive guide |
| Keyword | Broad head term with search volume |
| Role | Hub; links to all cluster articles; targets primary topic |
| Conversion | Link to product/feature pages where relevant |
Cluster Articles
| Attribute | Guideline |
|---|---|
| Count | 6-12 articles per pillar (minimum 6 for authority) |
| Length | 800-2,500 words each; focused on one subtopic |
| Keyword | Long-tail, specific intent per article |
| Links | Each cluster links to pillar; pillar links back; related clusters link to each other |
Internal Linking Model
| Link type | Purpose |
|---|---|
| Pillar to Cluster | Hub distributes authority; users discover subtopics |
| Cluster to Pillar | Signals relationship; passes equity to hub |
| Cluster to Cluster | Related subtopics; strengthens topical coverage |
Structure and Content Equally Important
Framework and body quality both matter: TOC, chapter logic, and content depth are all essential for SEO and UX. Weak structure undermines strong writing; weak writing undermines strong structure. Plan both from the start.
Why Topic Clusters Work
- Topical authority: Rank for multiple variations; comprehensive coverage signals expertise
- Avoid cannibalization: One page per topic/keyword; no competing pages
- Better internal linking: Clear logic; crawlers understand structure
- AI citations: Clustered content gets ~42% more AI citations than standalone
- Traffic: ~30% more organic traffic; rankings hold ~2.5x longer
Implementation Steps
- Choose 3-7 core topics -> business relevance, search demand, competitive opportunity
- Map subtopics -> People Also Ask, competitor analysis, keyword tools
- Content audit -> Identify existing pages that can become pillar or cluster; find gaps
- Build clusters first (optional) -> Cluster pages often rank first; add pillar after
- Create pillar -> Comprehensive guide; link to all clusters
- Establish links -> Pillar <-> cluster; cluster <-> cluster
- Update quarterly -> Maintain freshness and authority
Example
- Pillar: "SEO Guide" (targets "SEO")
- Clusters: "Technical SEO," "On-Page SEO," "Link Building," "Content SEO," "Local SEO," "E-E-A-T"
Content Types
| Type | Use | SEO Fit |
|---|---|---|
| How-to guides | Informational intent; high share potential | High -> matches search intent |
| Comparisons | Commercial intent; "X vs Y" | High |
| List posts | "Top 10," "Best X" | High |
| Glossaries | Definition queries; internal link hub | High |
| Tools/calculators | Linkable assets; engagement | High |
| Case studies | Proof; conversion support | Medium -> supports conversion |
| Funding / PR | Funding rounds, acquisitions | Low -> brand/PR, not search-driven |
| Product updates | Feature launches, release notes | Low -> internal audience |
| News / Trending | Industry news, hot topics | Medium -> quick spikes, short shelf life |
Evergreen vs Timely Content Mix
- Evergreen (70-75%): Pillar guides, how-tos, comparisons, glossaries. Drives long-term traffic, backlinks, authority. Refresh every 6-12 months.
- Timely (25-30%): Seasonal, trending, news. Generates quick traffic, shows topical relevance. Link timely pieces into evergreen pillars.
- Balance: Too much evergreen = blog feels stale; too much timely = irregular traffic, constant content churn.
Editorial Calendar
- Map keywords to content pieces
- Prioritize by opportunity (volume -> intent -> feasibility)
- Schedule by capacity
- Include update schedule for existing content
Output Format
- Topic cluster map (pillar + 6-12 clusters)
- Content calendar (topics, keywords, deadlines)
- Internal linking plan
- Update plan for existing content
Related Skills
- content-marketing: Content types, formats, channels, repurposing; SEO content is one channel
- translation: Multilingual content; translation workflow, glossary; avoid thin translations
- seo-strategy: SEO workflow order, Product-Led SEO, audit approach; use when planning SEO from scratch
- website-structure: Plan which pages to build; structure informs content clusters and pillar placement
- keyword-research: Keywords drive content plan
- programmatic-seo: Programmatic SEO for scaling pages with template + data; complements topic clusters
- content-optimization: Word count, H2 keywords, keyword density, multimedia, lists -> on-page content optimization
- internal-links: Clusters need internal linking
- link-building: Content strategy creates linkable assets
- heading-structure: Content structure uses headings
How to use content-strategy on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add content-strategy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches content-strategy from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate content-strategy. Access the skill through slash commands (e.g., /content-strategy) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★62 reviews- ★★★★★Kwame Abbas· Dec 16, 2024
Useful defaults in content-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Shikha Mishra· Dec 8, 2024
Solid pick for teams standardizing on skills: content-strategy is focused, and the summary matches what you get after install.
- ★★★★★Michael Iyer· Dec 8, 2024
content-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Nikhil Martinez· Dec 4, 2024
We added content-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Rahul Santra· Nov 27, 2024
We added content-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Xiao Chawla· Nov 27, 2024
Useful defaults in content-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Charlotte Bansal· Nov 23, 2024
Solid pick for teams standardizing on skills: content-strategy is focused, and the summary matches what you get after install.
- ★★★★★Ama Garcia· Nov 15, 2024
Registry listing for content-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kwame Ramirez· Nov 7, 2024
content-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Henry Diallo· Oct 26, 2024
Keeps context tight: content-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 62