content-strategy

content-strategy is a skill for Claude Code from rampstackco/claude-skills. It costs 120 tokens per session (2,301 once invoked), scanned A, original, MIT.

A plan for deciding what content an organization should create, for whom, and when. It covers topics, formats, publishing schedules, review rules, and how related subjects fit together.

In plain words
What is it for?
It helps build content programs, define topic groups, create editorial calendars, set review and approval processes, and connect content to brand and business goals.
Why use it?
It prevents content work from becoming a disconnected series of articles with no clear audience, purpose, or ownership.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the rampstack-skills plugin — 103 skills shipped together

Good fit It helps build content programs, define topic groups, create editorial calendars, set…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rampstackco/claude-skills/content-strategy
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add rampstackco/claude-skills --skill content-strategy
Clone the repo
git clone --depth 1 https://github.com/rampstackco/claude-skills

Made for: Claude Code.

Or install rampstack-skills, the plugin that ships this one along with the rest of its 103 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for content-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/rampstackco/claude-skills/content-strategy.svg)](https://agentmods.dev/skills/rampstackco/claude-skills/content-strategy)
Your own site
<a href="https://agentmods.dev/skills/rampstackco/claude-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/content-strategy.svg" alt="Measured on agentmods" height="20"></a>
Per session 120 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,301 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00120 $0.02301
Opus 5 $0.00060 $0.01151
Sonnet 5 $0.00024 $0.00460
Haiku 4.5 $0.00012 $0.00230

Measured 7d ago against content hash a4babe955d18, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

content-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

skills/content-strategy/SKILL.md · 218 lines

How it starts

The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Read the full file on GitHub · 218 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 218 lines · 120 tokens per session scan A a4babe955d18

Subscribe to this mod's changes

content-strategy is a skill published in the GitHub repository rampstackco/claude-skills (822 stars, last pushed 9d ago), licensed MIT. It adds 120 tokens to every session and 2,301 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.