content-strategy

content-strategy is a skill for Claude Code from bromso/metapowers. It costs 69 tokens per session (822 once invoked), scanned A, original, MIT.

A plan for a sustained content program, including topics, formats, publishing timing, and distribution. It organizes content around stages of the buyer journey, from initial awareness to action.

In plain words
What is it for?
Use it to choose content themes, build an editorial calendar, and plan owned, earned, and paid distribution. It is for an overall content program, not individual social posts.
Why use it?
Teams can publish disconnected pieces without knowing what purpose each serves or how it will reach people. This provides a coordinated publishing plan.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the marketing plugin — 29 skills shipped together

Good fit Use it to choose content themes, build an editorial calendar, and plan owned, earned, and paid distribution. It is for an overall content program, not individual social posts.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add bromso/metapowers
Claude Code
/plugin install marketing

Made for: Claude Code.

Or install marketing, the plugin that ships this one along with the rest of its 29 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/bromso/metapowers/content-strategy/github.svg)](https://agentmods.dev/skills/bromso/metapowers/content-strategy)
Your own site
<a href="https://agentmods.dev/skills/bromso/metapowers/content-strategy"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/content-strategy/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for content-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/bromso/metapowers/content-strategy"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/content-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 822 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.00069 $0.00822
Opus 5.5 $0.00028 $0.00329
Sonnet 5.5 $0.00014 $0.00164
Haiku 4.5 $0.00007 $0.00082

Measured 3d ago against content hash b91996cb695d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 3d 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.

plugins/marketing/skills/content-strategy/SKILL.md · 64 lines

How it starts

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

Content Strategy

Develop a comprehensive content strategy for "$ARGUMENTS". Define content pillars, plan an editorial calendar, and map distribution channels.

Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/marketing/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.

Prerequisites

Read .metapowers/marketing/<project>/00-strategy.md. If this file does not exist, tell the user:

Phase 0 (Strategy) has not been completed for "". Run /marketing:customer-research <project> first, or use --skip-checks to bypass.

Process

  1. Read context:

    • Read .metapowers/marketing/<project>/00-strategy.md for audience, positioning, and competitive context
    • Read ${CLAUDE_PLUGIN_ROOT}/shared/race-framework-guide.md for Reach phase guidance
  2. Define content pillars:

    • Identify 3-5 core topics that align with the product positioning and audience needs
    • Each pillar should map to a key search intent or audience pain point
    • Validate pillars against competitor content gaps
  3. Content audit (if applicable):

    • Use WebSearch to audit existing content from "" (if a URL is provided)
    • Identify what's performing, what's missing, and what needs updating
    • Map content gaps against the pillar strategy
  4. Plan content types and formats:

    • Blog posts, guides, case studies, videos, podcasts, newsletters, social
    • Map formats to funnel stages (awareness, consideration, decision)
    • Identify the 80/20: which formats deliver the most value with least effort?
  5. Build editorial calendar framework:

    • Publishing cadence recommendation (frequency per channel)
    • Content mix across pillars and formats
    • Seasonal or event-driven content opportunities
    • Repurposing strategy (one piece → multiple formats)

Read the full file on GitHub · 64 lines

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. 3d ago First seen · 64 lines · 69 tokens per session scan A b91996cb695d

Subscribe to this mod's changes

content-strategy is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 3d ago), licensed MIT. It adds 69 tokens to every session and 822 once invoked, about $0.0003 per session on Opus 5.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-10-21.