Agent skill

Content Strategy

by rampstackco in rampstackco/claude-skills

Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.

MITAuto-check passedWriting & Content

Install Content Strategy

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rampstackco/claude-skills content-strategy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-strategy .claude/skills/content-strategy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
content-strategy
GitHub stars
935
Token cost
~2.6k tokens
SKILL.md length
1,248 words
Files
4 (incl. references)
Skills in repo
103
Repo updated
First seen
Licence
MIT

At a glance

Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.

  • Works in 5 steps: Editorial positioning → Content pillars → Content formats and types → …
  • The user wants to plan a content program
  • SKILL.md covers When to use, When NOT to use, Required inputs and The framework: 5 layers, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Content Strategy is an agent skill from rampstackco/claude-skills. 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…

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `README.md`, `references/content-strategy-template.md` and `references/editorial-calendar-template.md`).

It sits in Writing & Content, covering Content strategy. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.

When your agent uses it

  • The user wants to plan a content program
  • Define content pillars
  • Build an editorial calendar
  • Structure topic clusters

Example prompts

  • “/content-strategy”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Editorial positioning
  2. Content pillars
  3. Content formats and types
  4. Editorial calendar
  5. Governance and lifecycle

What it can do on your machine

Read from SKILL.md and the folder at commit 482c9bf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Content Strategy loads about 2.6k tokens when it runs, and up to ~6.3k if it reads all its reference files. Until then it costs about 173 tokens; SKILL.md has 1,248 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~173
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 1,248 words, ~2,629 tokens.

Download SKILL.mdSave it as .claude/skills/content-strategy/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
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.

Show full SKILL.md (546 more words)Show less
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.
  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

© rampstackco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/content-strategy of rampstackco/claude-skills.

  • SKILL.md
  • README.md
  • references/content-strategy-template.md
  • references/editorial-calendar-template.md

Open the folder on GitHubat commit 482c9bf

Compare with similar skills

Content Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Content Strategy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Content Strategy this skillrampstackco/claude-skills935—~2.6kAutomated safety check: PassMIT
Blogger Distillerotter1101/blogger-distiller692—~3.8kAutomated safety check: NotesMIT
Blog Post Draftingluongnv89/claude-howto42k—~2.1kAutomated safety check: PassMIT
Linkedin Content Plannersergebulaev/linkedin-skills4.3k1 repos~2.1kAutomated safety check: PassMIT
WeChat Hot Article AnalysisSpaceZephyr/creator-buddy1.6k—~847Automated safety check: PassNone
Ralph Copywritermuratcankoylan/ralph-wiggum-marketer778—~2.4kAutomated safety check: PassNone

Similar skills

  • Blogger Distiller

    otter1101/blogger-distiller

    A skill your agent uses when the user wants to analyze or distill a blogger/account on Xiaohongshu or Douyin, benchmark a target creator, or diagnose their own content strategy.

    692 GitHub stars~3.8k tokensUpdated 14 days ago
    Writing & ContentAuto-check: notes
  • Blog Post Drafting

    luongnv89/claude-howto

    Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.

    42k GitHub stars~2.1k tokensUpdated 7 days ago
    Writing & ContentAuto-check passed
  • Linkedin Content Planner

    sergebulaev/linkedin-skills

    Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.

    4.3k GitHub starsUsed in 1 repo~2.1k tokens
    Writing & ContentAuto-check passed
  • WeChat Hot Article Analysis

    SpaceZephyr/creator-buddy

    Fetches hot WeChat Official Account articles by sector or keywords and produces a data file and an HTML report with rankings, style patterns and writing references.

    1.6k GitHub stars~847 tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Ralph Copywriter

    muratcankoylan/ralph-wiggum-marketer

    A skill your agent uses when the user asks to "analyze my content", "learn my writing style", "research competitors", "find content angles", "improve my blog", "write like me", "embody my brand…

    778 GitHub stars~2.4k tokensUpdated 6 mo ago
    Writing & ContentAuto-check passed
  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    32k GitHub starsUsed in 2 repos~1.9k tokens
    Writing & ContentAuto-check passed

More from rampstackco/claude-skills

All 103 skills in this repo
  • After Action Report

    rampstackco/claude-skills

    Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.

    935 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Analytics Strategy

    rampstackco/claude-skills

    Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.

    935 GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check passed
  • Brand Style Guide

    rampstackco/claude-skills

    Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.

    935 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Brand Voice

    rampstackco/claude-skills

    Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.

    935 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Content And Copy

    rampstackco/claude-skills

    Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.

    935 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Cro Optimization

    rampstackco/claude-skills

    Run conversion rate optimization through hypothesis-driven testing including audit, hypothesis generation, test design, statistical analysis, and rollout decisions.

    935 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Questions about Content Strategy

What does Content Strategy do?

Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Content Strategy is an agent skill from rampstackco/claude-skills. Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.

When should I use Content Strategy?

Content Strategy fits situations like: the user wants to plan a content program; define content pillars; build an editorial calendar; structure topic clusters.

How do I install Content Strategy in Claude Code?

Run `npx skills add rampstackco/claude-skills --skill content-strategy -a claude-code`. Or copy the skill folder (skills/content-strategy in rampstackco/claude-skills) into .claude/skills/content-strategy in your project. Claude Code loads it when a task matches its description.

How do I install Content Strategy in Codex?

Run `npx skills add rampstackco/claude-skills --skill content-strategy -a codex`. Or copy the skill folder (skills/content-strategy in rampstackco/claude-skills) into .agents/skills/content-strategy in your project. Codex loads it when a task matches its description.

Can I use Content Strategy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rampstackco/claude-skills --skill content-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-strategy, .gemini/skills/content-strategy, .github/skills/content-strategy and .opencode/skills/content-strategy in your project.

What does Content Strategy need to run?

SKILL.md names no scripts, command-line tools or credentials: Content Strategy is instructions for the agent only.

Does Content Strategy access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Content Strategy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Content Strategy use?

Content Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Content Strategy use?

About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.7k tokens, read only when the agent opens those files.

What are the alternatives to Content Strategy?

Skills that share tags, products or a category with Content Strategy: Blogger Distiller (otter1101/blogger-distiller, 692 stars), Blog Post Drafting (luongnv89/claude-howto, 42k stars), Linkedin Content Planner (sergebulaev/linkedin-skills, 4.3k stars) and WeChat Hot Article Analysis (SpaceZephyr/creator-buddy, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Content Strategy?

rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 935 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.

Source: rampstackco/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.