content-strategy
SkillDevelop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content g
Install
git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/content-strategyWhat is content-strategy?
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align content production with broader brand and SEO goals. Triggers on content strategy, content plan, editorial strategy, content pillars, content calendar, editorial calendar, topical authority, topic clusters, content governance, content roadmap, content production. Also triggers when the user is about to start producing content without a strategic plan.
What this can do
Capabilities declared in this component's own frontmatter — not inferred.
Inherit all session tools
Declares no tool restrictions — inherits every session tool
~168 tokens of context used while enabled, before you invoke anything
Documentation
README · ~6 min readContent Strategy
Plan what content to produce, why, when, and how. Stack-agnostic. Works for blogs, knowledge bases, marketing sites, newsletters, and product content surfaces.
This skill is the strategic layer. Tactical execution sits in content-and-copy, landing-page-copy, and email-sequences. SEO-driven content planning sits in seo-keyword. This skill stitches those together into a coherent program.
When to use
- Planning a new content program or relaunching an existing one
- Defining editorial positioning and content pillars
- Building an editorial calendar
- Structuring topic clusters and content hubs
- Establishing content governance (review, approval, lifecycle)
Reviews
Log in to leave a review.
No reviews yet — be the first.
Explore related
Other things in this space — across every part of the ecosystem, not just skills.
Skillssimilar to this one
All skills →ui-ux-pro-max-skill
An AI SKILL that provide design intelligence for building professional UI/UX multiple platforms
111.3K stars
claude-mem
Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
88.9K stars
obsidian-skills
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
43.6K stars
Plugins
All plugins →hookify
Easily create custom hooks to prevent unwanted behaviors by analyzing conversation patterns or from explicit instructions. Define rules via simple markdown files.
32.9K stars
desktop-commander
MCP server for terminal commands, process management, and file operations across text, code, PDF, DOCX, Excel, images, and structured data.
9K stars
awesome-agent-skills
Agent Skills 终极指南:快速入门、资源推荐、精选技能与实用工具 |The Ultimate Guide to Agent Skills: QuickStart, Resources, Features&Toolkit
4.9K stars
Subagents
All subagents →patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.
32.8K stars
agent-sdk-verifier-ts
Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.
32.8K stars
comment-analyzer
Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes (1) after generating large documentation comments or docstrings, (2) before finalizing a pull request that adds or modifies comments, (3) when reviewing existing comments fo
32.8K stars