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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncontent-strategyExecute the skills CLI command in your project's root directory to begin installation:
Fetches content-strategy from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate content-strategy. Access via /content-strategy in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
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.
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:
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 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.
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
| 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 |
| 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 |
| 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 |
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.
| 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 |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
Useful defaults in content-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: content-strategy is focused, and the summary matches what you get after install.
content-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added content-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added content-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in content-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: content-strategy is focused, and the summary matches what you get after install.
Registry listing for content-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
content-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
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