Skip to main content
skill CX Codex

content-strategy · rampstackco — Claude Code skill: content planning, install

The content-strategy skill plans a content program with editorial positioning, topic pillars, formats, a calendar, governance, and topical authority work.

MIT 309 installs ★ 1,107 updated 2026-10-19

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add rampstackco/claude-skills --skill content-strategy -a claude-code
Open on GitHub

What content-strategy does

content-strategy structures a content program across five layers: editorial positioning, content pillars, formats, the publishing calendar, and governance with lifecycle decisions. It connects planned topics to business goals and gives each piece a place in the wider program.

The workflow runs from idea and brief through outline, draft, edit, review, publishing, measurement, and either an update or retirement. SEO-led planning can use keyword research, while the strategy also needs brand positioning, audience, business goals, existing content, and production capacity.

If brand positioning is unclear, run brand-discovery first. That requirement shapes the strategy before the calendar is built.

What it helps with

  • plan a complete content program
  • define editorial content pillars
  • build a publishing calendar
  • organize topic clusters for SEO
  • set review and content lifecycle rules

Example prompts for the agent

  • Build a content strategy for our product with editorial positioning, audience, business goals, and content pillars.
  • Create an editorial calendar with pillar rotation, content formats, and slots for timely topics.
  • Map the workflow from idea to publication, then define when each piece should be updated or retired.

How to install content-strategy

1Skills CLI (Vercel)

npx skills add rampstackco/claude-skills --skill content-strategy -a claude-code

2Manually: put the files in place

~/.claude/skills/content-strategy/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/content-strategy/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about content-strategy

How do I install content-strategy in Claude Code?

Run npx skills add rampstackco/claude-skills --skill content-strategy -a claude-code, then check ~/.claude/skills/content-strategy/SKILL.md.

What does content-strategy do?

It plans a content program around editorial positioning, topic pillars, formats, publishing cadence, governance, and content lifecycle decisions.

What does content-strategy need before planning begins?

Prepare brand positioning, audience, business goals, an existing content inventory, and production capacity. SEO-focused planning also needs keyword research output.

Source text

SKILL.md · MIT
---
name: content-strategy
description: "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."
category: strategy-and-discovery
catalog_summary: "Editorial strategy, content calendar, topical authority planning"
display_order: 5
---

# Content 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-discovery` or `creative-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

1. **Confirm inputs.** Brand positioning, audience, business goals, capacity. If any are missing, surface that first.
2. **Draft editorial positioning.** Mission, audience, promise, distinction. Stress-test the positioning by trying to complete the "We help X" sentence.
3. **Define content pillars.** 3 to 5. Each with a theme, justification, sub-topics, and planned cornerstone content.
4. **Choose formats.** 3 to 5 formats the program returns to consistently.
5. **Build the calendar.** Cadence, pillar rotation, format mix, flex slots.
6. **Set up governance.** Roles, workflow, quality bar, lifecycle rules.
7. **Document.** Use the template in [`references/content-strategy-template.md`](references/content-strategy-template.md).
8. **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:
1. Editorial positioning
2. Content pillars (3 to 5, each detailed)
3. Formats
4. Calendar (cadence and structure, not the specific items)
5. Governance (roles, workflow, lifecycle)
6. Measurement plan (metrics, review cadence)
7. 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`](references/content-strategy-template.md) - Strategy document template.
- [`references/editorial-calendar-template.md`](references/editorial-calendar-template.md) - Spreadsheet column definitions and calendar structure.

© rampstackco · MIT · rampstackco/claude-skills

Similar skills

All skills for Marketing and content →

content-strategy by other authors comes first.

content-strategy coreyhaines31 content-strategy — a skill for Claude Code and Codex that turns customer questions and search intent into an actionable editorial plan. Evaluates topic ideas before production starts. CX Codex +1 179,600installs content-strategy official anthropics The content-strategy skill reads sales data from PayPal and QuickBooks, factors in seasonality, and builds a prioritized 30-day content brief. Use it when deciding what to promote. CX Codex +1 2,000installs content-strategy Owl-Listener content-strategy works out what content a product needs, where it lives and who owns it. Useful when the content itself is the problem, not the layout. CX Codex +1 2,100installs content-strategy kostja94 content-strategy is a Claude Code skill for planning SEO content, topic clusters, and editorial calendars. It activates for requests about content plans, pillar pages, or internal links. CX Codex +1 1,400installs content-strategy OpenClaudia content-strategy builds topic clusters, editorial calendars, and content roadmaps mapped to the buyer journey. Helps marketing teams grow organic traffic and leads. CX Codex +1 563installs content-strategy-and-planning manojbajaj95 content-strategy-and-planning organizes content pillars, editorial schedules, and AI search visibility. Generates drafts and buyer-stage messaging directly inside your project files. CX Codex +1 157installs content-marketing-strategist Maigent content-marketing-strategist turns a short interview into a content marketing plan: pillars, a 90-day calendar, distribution channels, SEO and a repurposing playbook. CX Codex +1 ★ 1,013repo stars content-strategist rohitg00 The content-strategist subagent plans SEO content, groups topics into clusters, and connects publishing work to performance metrics. It targets technical products and developer audiences. CX Codex ★ 2,858repo stars suede-content-strategy JasonColapietro suede-content-strategy plans content strategy: what to publish, refresh or stop. It turns audience questions, topic pillars, AI answer gaps and original data into priorities, cadence and KPIs. CX Codex +1 ★ 121repo stars blog-calendar AgriciDaniel blog-calendar builds a dated monthly or quarterly editorial calendar with topics, reviews, content mix, and distribution timing. Useful for planning a blog. CX Codex +1 2,700installs content-marketing kostja94 Plans content marketing across channels: content types and formats, funnel stages, and repurposing one piece into many. CX Codex +1 1,300installs

From the same set102

The whole set →
ads-performance-analytics The ads-performance-analytics skill helps interpret paid media reports, reconcile attribution, and avoid budget decisions based on a single platform metric. CX Codex +1 313installs seo-keyword seo-keyword discovers search queries worth ranking for, classifies them by intent, and groups them into topic clusters. Helps you prioritize what to write based on traffic potential and competitive difficulty. CX Codex +1 312installs form-strategy form-strategy — a skill for building forms that convert and keep spam out. Guides you through field strategy, validation rules, bot detection, and CRM integration. CX Codex +1 312installs seo-competitor seo-competitor is a Claude Code skill that compares your site with competitors across search, content, backlinks, and technical foundations. It surfaces gaps and prioritizes them. CX Codex +1 309installs analytics-strategy The analytics-strategy skill designs measurement frameworks: event taxonomy, KPI hierarchy, dashboard architecture, and attribution models. Use it to plan analytics from scratch or audit your existing tracking setup. CX Codex +1 309installs funnel-flow-architecture The funnel-flow-architecture skill maps funnel paths across audience segments and stages, connecting entry points to nurture sequences and offers. Use it when growth tools feel disconnected or everyone gets the same flow. CX Codex +1 309installs monitoring-and-alerting monitoring-and-alerting guides the design of web app monitoring architectures, SLO definitions, error budgets, and on-call paging policies to stop alert fatigue. CX Codex +1 308installs scheduler-and-booking-design scheduler-and-booking-design — a skill for designing booking flows that qualify leads and convert higher than a generic calendar link. Availability logic, qualification fields, routing by rep seniority, call prep automation. CX Codex +1 307installs

Project sponsors

Companies that keep this analytics open