content-strategy

content-strategy is a skill for Claude Code from DariuszCiesielski/polish-agent-skills. It costs 84 tokens per session (2,222 once invoked), scanned A, original, MIT.

A planning guide for deciding what a SaaS company should publish, including related topic groups, a publishing calendar, and content gaps compared with competitors.

In plain words
What is it for?
Use it to audit existing content, find missing topics, group related articles, and plan blog publishing for a quarter or longer.
Why use it?
It replaces random blog-topic choices with a structured plan tied to traffic, leads, and authority.

Skill for Claude Code

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

Part of the polish-content-skills plugin — 4 skills shipped together

Good fit Use it to audit existing content, find missing topics, group related articles, and plan blog publishing for a quarter or longer.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dariuszciesielski/polish-agent-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 DariuszCiesielski/polish-agent-skills --skill content-strategy
Clone the repo
git clone --depth 1 https://github.com/DariuszCiesielski/polish-agent-skills

Made for: Claude Code.

Or install polish-content-skills, the plugin that ships this one along with the rest of its 4 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/dariuszciesielski/polish-agent-skills/content-strategy/github.svg)](https://agentmods.dev/skills/dariuszciesielski/polish-agent-skills/content-strategy)
Your own site
<a href="https://agentmods.dev/skills/dariuszciesielski/polish-agent-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/dariuszciesielski/polish-agent-skills/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/dariuszciesielski/polish-agent-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/dariuszciesielski/polish-agent-skills/content-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,222 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.00084 $0.02222
Opus 5 $0.00042 $0.01111
Sonnet 5 $0.00017 $0.00444
Haiku 4.5 $0.00008 $0.00222

Measured 11d ago against content hash 0016642e94e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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.

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

How it starts

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

Content Strategy Planner

Planuje strategię contentową dla projektów SaaS — od audytu istniejącej treści, przez topic clusters, po konkretny kalendarz publikacji z priorytetami.

Kiedy używać

  • Rozpoczynasz blog / content marketing w projekcie SaaS
  • Masz blog ale brakuje strategii (losowe tematy, brak spójności)
  • Chcesz zaplanować content na kwartał/pół roku
  • Potrzebujesz analizy luk contentowych vs konkurencja
  • Użytkownik mówi: "co pisać na blog", "zaplanuj content", "strategia treści"

Zależności

  • Wymagane: product-marketing-context — pliki target-keywords.md, competitor-analysis.md, features.md
  • Opcjonalne: seo — do walidacji keywordów, content — do pisania artykułów

Jeśli kontekst marketingowy nie istnieje → zaproponuj najpierw uruchomienie product-marketing-context.

Komendy

/content-strategy audit              — audyt istniejącej treści
/content-strategy clusters           — wygeneruj topic clusters
/content-strategy calendar [Q1/Q2..] — kalendarz publikacji
/content-strategy gaps               — analiza luk vs konkurencja
/content-strategy plan               — pełny plan (audit → clusters → calendar)

Proces

Faza 1: Audyt istniejącej treści

  1. Skanuj projekt — znajdź wszystkie strony z treścią:

    • Blog posts: src/app/blog/, content/, posts/
    • Landing pages: src/app/(marketing)/, src/app/lp/
    • Docs: docs/, src/app/docs/
  2. Dla każdej strony oceń:

    Metryka Jak sprawdzić
    Word count Policz słowa w treści (bez kodu/nav/footer)
    Target keyword Czy H1/title zawiera keyword?
    Aktualność Data ostatniej modyfikacji (git log)
    Linki wewnętrzne Ile linków do innych stron projektu?
    CTA Czy jest call-to-action?
  3. Kategoryzuj:

    • 🟢 Evergreen — aktualne, dobrze zoptymalizowane
    • 🟡 Do odświeżenia — >6 mies. bez aktualizacji LUB thin content (<800 słów)
    • 🔴 Do przepisania — brak keyword focus, brak CTA, <400 słów
    • Do usunięcia — duplikat, nieaktualne, cannibalizing inny artykuł

Read the full file on GitHub · 208 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. 11d ago First seen · 208 lines · 84 tokens per session scan A 0016642e94e5

Subscribe to this mod's changes

content-strategy is a skill published in the GitHub repository DariuszCiesielski/polish-agent-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 84 tokens to every session and 2,222 once invoked, about $0.0004 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-31.