content-strategy skill
✓ VerifiedDevelops comprehensive content programs including editorial positioning, content pillars, formats, editorial calendars, and governance frameworks.
- GitHub stars
- 1,066
- Files
- 4
- Last commit
- Nov 8, 2026
- License
- MIT
- Allowed tools
- —
What does the content-strategy skill do?
content-strategy develops comprehensive content programs including editorial positioning, content pillars, formats, editorial calendars, and governance frameworks.
Summary generated from the skill's SKILL.md.
About the content-strategy skill
Developing a structured content program for blogs, newsletters, or marketing sites is what this skill enables. It serves marketing teams and brand owners who need to move beyond random publishing toward a coherent editorial strategy. By defining editorial positioning, content pillars, and governance frameworks, it ensures that every piece of content serves specific business goals like brand authority or lead generation.
An agent should load this skill when a user needs to plan a content roadmap, structure topic clusters, or establish a production workflow. It acts as a strategic layer that connects brand discovery and keyword research to actual execution. While it does not write the specific articles or landing pages, it produces a comprehensive strategy document and an editorial calendar structure. The output relies on provided inputs such as brand positioning, audience definitions, and production capacity to ensure the plan is realistic and aligned with the brand's mission.
What an agent can do with it
- 1Establish editorial positioningDefine the mission, audience, and unique promise of a new content program.
- 2Design production workflowsSet up governance frameworks including roles, review processes, and content lifecycles.
- 3Plan publishing schedulesDevelop an editorial calendar that manages cadence and pillar rotation.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the content-strategy skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the content-strategy skill in Plugin
/plugin marketplace add rampstackco/claude-skills /plugin install rampstack-skills@rampstack
Install the content-strategy skill in Claude Code
~/.claude/skills/content-strategy/SKILL.md
$ npx degit rampstackco/claude-skills/skills/content-strategy ~/.claude/skills/content-strategyInstall the content-strategy skill in Claude Code (project)
.claude/skills/content-strategy/SKILL.md
$ npx degit rampstackco/claude-skills/skills/content-strategy .claude/skills/content-strategyInstall the content-strategy skill in Codex
~/.agents/skills/content-strategy/SKILL.md
$ npx degit rampstackco/claude-skills/skills/content-strategy ~/.agents/skills/content-strategyInstall the content-strategy skill in Gemini CLI
~/.gemini/skills/content-strategy/SKILL.md
$ npx degit rampstackco/claude-skills/skills/content-strategy ~/.gemini/skills/content-strategyInstall the content-strategy skill in Claude.ai
npx degit rampstackco/claude-skills/skills/content-strategy content-strategy && zip -r content-strategy.zip content-strategy # claude.ai → Customize → Skills → + → Create skill → Upload a skill → content-strategy.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablerampstackco/claude-skills/skills/content-strategy is public and reachablegithub.com/rampstackco/claude-skills/tree/HEAD/skills/conten ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-08github.com/rampstackco/claude-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/rampstackco/claude-skills/blob/HEAD/skills/conten ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/rampstackco/claude-skills/blob/HEAD/skills/conten ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 218 linesgithub.com/rampstackco/claude-skills/blob/HEAD/skills/conten ↗Pass
SKILL.md
View on GitHubContent 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)
- Aligning content with broader brand and revenue goals
When NOT to use
- Writing specific content pieces (use
content-and-copy) - Writing landing pages or sales copy (use
landing-page-copy) - Writing email sequences (use
email-sequences) - Pure keyword research (use
seo-keyword, then return here for strategic planning) - Auditing existing content for keep/update/delete decisions (use
seo-content-audit)
Required inputs
- Brand positioning and audience (from
brand-discoveryorcreative-brief) - Business goals the content needs to serve (traffic, leads, brand authority, retention)
- Existing content inventory (if any)
- Keyword research output (from
seo-keyword) if SEO-driven - Production capacity (writers, budget, cadence)
If brand positioning is unclear, run brand-discovery first. If audience is undefined, do that work before strategy.
The framework: 5 layers
A content strategy has five layers. Skip layers and the program drifts.
1. Editorial positioning
What this content program stands for. The "why we write" statement.
Components:
- Mission. Why this content exists. One sentence.
- Audience. Who it serves. Specific.
- Promise. What readers get from us they cannot get elsewhere.
- Distinction. What makes this content different from the 50 other publications in the same space.
Example structure:
We help [audience] [achieve outcome] by publishing [content type] that [unique angle], unlike [common alternatives] that [common shortcoming].
A strong editorial positioning forces choices. If you cannot complete the sentence, the positioning is too vague.
2. Content pillars
The 3 to 5 themes the program owns. Every piece of content belongs to a pillar.
Per pillar, define:
- Theme. One sentence describing the topic territory.
- Why we own it. Audience need + brand authority + competitive opportunity.
- Sub-topics. 5 to 15 sub-topics that fit under the pillar.
- Cornerstone content. The 1 to 2 pieces that anchor the pillar (long-form, comprehensive, link-worthy).
- Supporting content. Articles, videos, tools, comparisons that reinforce and link to the cornerstone.
Pillar selection criteria:
- Audience cares about it (research-backed, not assumed)
- Brand has credibility or can earn it
- Topical authority is achievable (you can plausibly become a top-3 source)
- Connects to revenue (directly or indirectly)
- Distinguishes you from competitors
3 to 5 pillars is the sweet spot. Fewer than 3 risks brittleness. More than 5 dilutes focus.
3. Content formats and types
The shapes the content takes.
Format dimensions:
- Length. Short (under 500 words), medium (500 to 1500), long (1500 to 3000), epic (3000+)
- Depth. Surface (overview) vs. deep (comprehensive)
- Type. Article, guide, comparison, listicle, case study, interview, data study, tool, video, podcast, newsletter, social
- Originality. Aggregation (summarizing existing knowledge) vs. original research (new data or insight)
- Evergreen vs. timely. Lasting value vs. moment-driven
Format selection criteria:
- Match the audience's preferred consumption (do they read, watch, listen?)
- Match the topic (some topics demand depth; others demand brevity)
- Match production capacity
- Match distribution channels (LinkedIn favors short; YouTube favors video; SEO favors long evergreen)
A content program typically has 3 to 5 formats it returns to consistently. More than that fragments production and brand recognition.
4. Editorial calendar
When content publishes.
Cadence options:
- High frequency (3+ pieces per week): builds momentum, requires significant production capacity
- Medium frequency (1 to 2 per week): sustainable for most teams, builds steady audience
- Low frequency (1 to 4 per month): each piece must be high-impact; longer production cycles
- Burst-then-pause (10 pieces in a month, then 3 months off): launches and campaigns
Calendar structure:
- Pillar rotation. If you have 4 pillars and publish weekly, each pillar gets one piece per month.
- Content type mix. Within a month, blend types (e.g., 2 articles + 1 case study + 1 video).
- Timely opportunities. Reserve flex slots for newsjacking, seasonal content, launches.
- Updates and refreshes. Plan time for updating existing high-performing content.
Common failure: publishing whatever happens to get written. Without a calendar, the program drifts toward the topics easiest to write, not the ones the audience needs most.
5. Governance and lifecycle
How content gets made, reviewed, published, measured, and retired.
Production workflow:
Idea → Brief → Outline → Draft → Edit → Review → Publish → Measure → Update or Retire
Per stage, define:
- Who owns it
- What inputs they need
- What outputs they produce
- What the quality bar is
- How long it should take
Roles:
- Editorial lead. Owns positioning, calendar, quality bar.
- Writers. Produce drafts. May be in-house, freelance, or AI-assisted.
- Subject matter experts. Provide expertise, review for accuracy.
- Editors. Polish, ensure voice consistency, fact-check.
- SEO lead. Keyword optimization, internal linking, schema.
- Publishers. Ship the content (CMS, scheduling, distribution).
Lifecycle decisions:
- Update cadence. Top-performing evergreen content reviewed every 6 to 12 months.
- Retire criteria. Content that no longer serves the audience or hurts the site (use
seo-content-audit). - Republishing. Updated content republished as fresh, not buried as an update.
Workflow
- Confirm inputs. Brand positioning, audience, business goals, capacity. If any are missing, surface that first.
- Draft editorial positioning. Mission, audience, promise, distinction. Stress-test the positioning by trying to complete the "We help X" sentence.
- Define content pillars. 3 to 5. Each with a theme, justification, sub-topics, and planned cornerstone content.
- Choose formats. 3 to 5 formats the program returns to consistently.
- Build the calendar. Cadence, pillar rotation, format mix, flex slots.
- Set up governance. Roles, workflow, quality bar, lifecycle rules.
- Document. Use the template in
references/content-strategy-template.md. - Operationalize. Set up the editorial calendar in whatever tool the team uses (CMS, Notion, Airtable, etc.).
Failure patterns
- Strategy without capacity. A 3-piece-per-week plan with one part-time writer fails. Match strategy to actual production capacity.
- Pillars chosen for SEO alone. Pillars must serve the audience and the brand, not just keyword opportunity. SEO is a downstream filter, not the strategy itself.
- Too many pillars. 7 pillars dilute the brand. The audience cannot remember what you stand for.
- Calendar without governance. Content gets produced but quality drifts. Without a quality bar, the program loses authority.
- No update plan. Top-performing content goes stale. Competitors with fresher versions overtake.
- Vanity metrics. Pageviews and follower counts without conversion tracking. Define what success looks like in business terms.
- Strategy that lives in a doc. A strategy document that doesn't translate to the editorial calendar and the production workflow is decoration. Operationalize or it doesn't exist.
Output format
Default output is a strategy document at content-strategy.md plus an editorial calendar in whatever tool the team uses.
Strategy document structure:
- Editorial positioning
- Content pillars (3 to 5, each detailed)
- Formats
- Calendar (cadence and structure, not the specific items)
- Governance (roles, workflow, lifecycle)
- Measurement plan (metrics, review cadence)
- Production capacity and budget
Editorial calendar (separate, ongoing):
- One row per planned content piece
- Columns for: title, pillar, format, target keyword (if SEO-driven), publish date, owner, status
If required data is unavailable
This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
Reference files
references/content-strategy-template.md- Strategy document template.references/editorial-calendar-template.md- Spreadsheet column definitions and calendar structure.
Files in this skill
4content-strategy skill questions
How do I install the content-strategy skill in Claude Code?
Run npx degit rampstackco/claude-skills/skills/content-strategy ~/.claude/skills/content-strategy. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the content-strategy skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What should be included in editorial positioning?
Editorial positioning should define the mission, the specific audience, the promise to readers, and the distinction that makes the content unique.
How many content pillars are recommended for a strategy?
The ideal number is 3 to 5 pillars; having fewer than 3 risks brittleness, while more than 5 can dilute your focus.
What are the different cadence options for an editorial calendar?
Options include high frequency (3+ pieces per week), medium frequency (1 to 2 per week), low frequency (1 to 4 per month), or a burst-then-pause approach.