content-strategy

content-strategy is a skill for Claude Code from ranjeeetvimal/growth-skills. It costs 91 tokens per session (734 once invoked), scanned A, original, MIT.

A focused content-planning skill for businesses including software companies, business services, and consumer products. It chooses a small number of channels, search-content groups, free tools, and a detailed 90-day publishing schedule.

In plain words
What is it for?
Use it to plan search-focused article clusters, comparison pages, problem or fear-based content, free engineering-based marketing tools, distribution, and week-by-week content for three months.
Why use it?
Broad content backlogs can spread a team too thin and produce disconnected articles. This turns strategy into a limited set of connected topics and practical distribution work, while identifying what to leave out.

Skill for Claude Code

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

Part of the plg-architect plugin — 7 skills shipped together

Good fit Use it to plan search-focused article clusters, comparison pages, problem or fear-based content, free engineering-based marketing tools, distribution, and week-by-week content for three months.

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

Made for: Claude Code.

Or install plg-architect, the plugin that ships this one along with the rest of its 7 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/ranjeeetvimal/growth-skills/content-strategy/github.svg)](https://agentmods.dev/skills/ranjeeetvimal/growth-skills/content-strategy)
Your own site
<a href="https://agentmods.dev/skills/ranjeeetvimal/growth-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/ranjeeetvimal/growth-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/ranjeeetvimal/growth-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/ranjeeetvimal/growth-skills/content-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 734 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.00091 $0.00734
Opus 5 $0.00046 $0.00367
Sonnet 5 $0.00018 $0.00147
Haiku 4.5 $0.00009 $0.00073

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

PLG-Architect/skills/content-strategy/SKILL.md · 58 lines

How it starts

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

Content Strategy — Sacrifice-First

You are a content operator who knows doing everything = doing nothing. You draft the clusters and tools yourself — the founder reacts, they don't brainstorm.

Reference library (read on demand)

  • references/content-playbook.md — channel concentration, SEO cluster patterns (switcher / fear / JTBD / programmatic), comparison pages, engineering-as-marketing free tools, the 90-day calendar, distribution.

Start: read context, then draft

Read .claude/founder-context.md and .claude/strategy-snapshot.md (obey its principles). Then propose the channels, clusters, and free tools yourself — pick the 1-2 channels where the ICP is, draft the SEO clusters with real example titles, suggest 1-3 free-tool ideas. Founder confirms, doesn't generate.

Rules

  1. Elaborate — don't summarize. Each cluster gets real example post titles and the angle; each free tool gets its mechanic and why it spreads; the calendar is week-by-week with specific pieces. "Do a fear cluster" is a failure — write the actual titles and the plan.
  2. Connected + self-contained. Build on the strategy; be ruthless about what NOT to do and why. Confidence tags throughout.

Process

  1. Channel test — pick 1-2 by evidence; ignore the rest 90 days.
  2. SEO clusters — draft by pattern (switcher = decaying, fear = compounding moat, JTBD, programmatic), with real example titles. Only recommend SEO if the ICP actually searches.
  3. Engineering-as-marketing — 1-3 free-tool ideas, each elaborated.
  4. Content bet — channel + format + outcome + confidence + effort + 30-day read.
  5. 90-day cadence — week by week, specific pieces.

Output format

Open with the real headline (the one channel that fits, or the honest "content is wrong for you now"). Then, as connected sections:

  1. Channel bet — 1-2 channels, quantified, with what's ruled out and why.
  2. SEO clusters — with real example titles, prioritized.
  3. Free-tool ideas — each elaborated (mechanic + why it spreads).
  4. 90-day calendar — week by week.
  5. Sacrifices — 5+ channels/formats we're NOT doing and why.
  6. Recommendations — a short numbered list of what to ship first, in order.

Read the full file on GitHub · 58 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. 10d ago First seen · 58 lines · 91 tokens per session scan A 4924a95e6bdb

Subscribe to this mod's changes

content-strategy is a skill published in the GitHub repository ranjeeetvimal/growth-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 734 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

research-seo-demand

A Chinese-language process for researching SEO opportunities, where SEO means improving pages so they can appear in search results. It studies user needs, keyword demand, search-result pages, and competing pages using Bing data.

tsingyuai/growth-lab · 102 tokens

create-seo-page

A Chinese-language workflow for creating and implementing search-focused pages in an existing product repository. SEO means improving a page so it can be found and understood through search engines.

tsingyuai/growth-lab · 93 tokens

review-seo-performance

A review process for evaluating search visibility and AI citations using Bing Webmaster data. It examines whether pages are indexed, how they appear in searches, and when AI-generated answers cite them.

tsingyuai/growth-lab · 85 tokens

run-seo-page-loop

Run an SEO page observation-action-review loop with persistent Memory by coordinating demand research, page creation, adversarial review, image generation, IndexNow submission, and performance review. Use when taking an SEO page from opportunity discovery through publication, measurement, iteration, or continuing a…

tsingyuai/growth-lab · 65 tokens

xiaohongshu-mcp

A browser-based, read-only process for researching posts on Xiaohongshu, a Chinese social platform for user-created lifestyle and product content. It can collect search results, candidate cover images, selected post details, and sanitized evidence.

tsingyuai/growth-lab · 78 tokens

generate-image

Generate, edit, or batch-create SEO, marketing, social, and document images with Gemini or OpenAI through the repository-owned Growth Lab image client. Use when a page or content loop needs illustrations, diagrams, covers, reference-image edits, multiple candidates, or verified image text and composition. This is the…

tsingyuai/growth-lab · 73 tokens