New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Content Strategy

by unifapi-agent in unifapi-agent/agents

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover.

MITAuto-check passedWriting & Content

Install Content Strategy

skills CLI
$ npx skills add unifapi-agent/agents --skill content-strategy -a claude-code

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

GitHub CLI
$ gh skill install unifapi-agent/agents 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/unifapi-agent/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-strategy-agent/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
587
Token cost
~2.5k tokens
SKILL.md length
1,007 words
Files
2
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover.

  • Works in 7 steps: Gather context. If… → Draft and validate candidate pillars.… → Mine community questions per pillar. Run… → …
  • Wants to plan a content strategy
  • SKILL.md covers Use UnifAPI for live evidence, The framework: searchable vs.…, Workflow and Output: content strategy, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Content Strategy is an agent skill from unifapi-agent/agents. When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce — grounded in real public demand, not guesswork. For a single…

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

It sits in Writing & Content, covering Content strategy. It works with Reddit. The repository describes itself as: Open-source marketing agents for Claude, ChatGPT, Codex, OpenClaw & Hermes. One plugin: SEO audits, GEO / AI-visibility, local SEO, KOL pricing, social listening & competitive… The licence is MIT.

When your agent uses it

  • Wants to plan a content strategy
  • Decide what content to create
  • Figure out what topics to cover
  • The user mentions content strategy

Example prompts

  • “content strategy,”
  • “what should I write about,”
  • “content ideas,”
  • “/content-strategy”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Gather context. If .agents/product-marketing.md (or .claude/product-marketing.md) exists, read it first. Establish: what the company does…
  2. Draft and validate candidate pillars. Draft 3–5 pillars across the four archetypes. For each, expand with seo/keywords/ideas +…
  3. Mine community questions per pillar. Run seo/serp for site:reddit.com , open promising threads with reddit/posts/{id}/comments, and…
  4. Map clusters and tag by stage. Group the questions into spokes under each pillar; tag each with seo/keywords/intent…
  5. Score every piece with the prioritization rubric below and sort.
  6. Schedule into a cadence the team can hold — hub pages before their spokes, decision/consideration pieces early, awareness backfilled for…
  7. State sources and dates so the plan is reproducible.

What it can do on your machine

Read from SKILL.md and the folder at commit fb53247. 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 (its code samples are markdown).

    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.5k tokens when it runs. Until then it costs about 162 tokens; SKILL.md has 1,007 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~162
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

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 unifapi-agent/agents at commit fb53247, republished under its MIT licence (© unifapi-agent). 1,007 words, ~2,538 tokens.

Download SKILL.mdSave it as .claude/skills/content-strategy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
content-strategy
description
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce — grounded in real public demand, not guesswork. For a single ranked opportunity list, see content-opportunity-brief. For the audience language behind it, see customer-research.
license
MIT
metadata.author
UnifAPI
metadata.version
1.0.0
metadata.adapted_from
https://github.com/coreyhaines31/marketingskills
metadata.adapted_author
Corey Haines

Content Strategy

You are a content strategist. Your goal is to plan content that drives traffic, builds authority, and generates leads — by being searchable, shareable, or both. Every pillar, cluster, and cadence decision is grounded in live public demand pulled via UnifAPI, not in what feels like a good idea.

This is an enhanced skill: it reads live public data through UnifAPI.

Use UnifAPI for live evidence

The original framework was strong but ideation was manual — the strategist guessed which pillars would land. Here, no pillar earns a slot without demand behind it, and clusters are built from the exact questions people repeat. Use the unifapi skill to connect (OAuth MCP), then call:

  • Size search demand per pillar — seo/keywords/ideas, seo/keywords/related (expand each candidate pillar into the head/long-tail it implies), seo/keywords/overview (volume + CPC + competition to size the pillar against real demand) — a pillar with no volume and no community pull gets cut.
  • Tag clusters by buyer stage — seo/keywords/intent (classify each cluster keyword as informational / commercial / transactional, which maps to awareness → consideration → decision) so every spoke lands in the right journey stage.
  • See the SERP shape — seo/serp per pillar head term (which result types own it, how strong the ranking pages are) so you plan formats that can actually win, not pieces that bounce off entrenched incumbents.
  • Community questions (Reddit has no keyword search) — run seo/serp for site:reddit.com <topic> to find threads, then open each with reddit/posts/{id}/comments to capture the recurring questions and exact phrasing that become cluster spokes. Note thread score and comment count.
  • Shareable demand — youtube/search (which angles already pull views — read titles, descriptions, view/like counts and youtube/videos/{id}/related; there is no comment endpoint, do not promise comment mining), news/search (current and emerging angles for timely hooks, with publish dates), tiktok/search (rising framings before search reflects them, with view/like counts).

UnifAPI reads public data only — it never publishes or touches any account. Keep any billing metadata so the output can state record cost. The strategy is the deliverable; the operator's own assistant writes and ships the pieces.

When you need a single ranked opportunity list rather than a full strategy, hand off to the content-opportunity-brief skill, then roll those briefs into the structure below.

The framework: searchable vs. shareable, pillars and clusters

Classify every piece as searchable, shareable, or both, and prioritize in that order. Searchable captures existing demand (target a keyword, match intent, comprehensive coverage). Shareable creates demand (novel insight, original data, counterintuitive take, story). A strategy is three layers, each validated against live demand:

  • Pillars (3–5) — the broad topics the brand can credibly own. Pick across four archetypes: product-led (the problem your product solves), audience-led (the job/role of the ICP), search-led (high-volume head terms from seo/keywords/overview), competitor-led (terms competitors rank for that you don't). A pillar earns its place only when search + community demand back it.
  • Clusters (spokes under each pillar) — the specific, answerable topics, each tied to a verbatim question (from reddit/posts/{id}/comments or a seo/keywords/ideas question variant) and tagged by buyer stage via seo/keywords/intent: awareness (what/how/guide) → consideration (best/vs/alternatives) → decision (pricing/reviews/demo) → implementation (templates/tutorial/setup). Build the pillar hub page before its spokes so internal links flow.
  • Cadence — the realistic publishing rhythm. Don't plan more than the team can hold. Sequence decision/consideration pieces early (closest to revenue), then backfill awareness for compounding traffic.
Show full SKILL.md (465 more words)Show less

Workflow

  1. Gather context. If .agents/product-marketing.md (or .claude/product-marketing.md) exists, read it first. Establish: what the company does, the ICP, the primary content goal (traffic / leads / authority), and the formats and cadence the team can actually sustain.
  2. Draft and validate candidate pillars. Draft 3–5 pillars across the four archetypes. For each, expand with seo/keywords/ideas + seo/keywords/related, size with seo/keywords/overview, and read the SERP shape with seo/serp. Keep pillars showing real, repeated demand; cut or merge ones that don't.
  3. Mine community questions per pillar. Run seo/serp for site:reddit.com <pillar topic>, open promising threads with reddit/posts/{id}/comments, and harvest the recurring questions and verbatim phrasing that become cluster spokes.
  4. Map clusters and tag by stage. Group the questions into spokes under each pillar; tag each with seo/keywords/intent (awareness/consideration/decision/implementation) and mark searchable/shareable. Cross-check shareable angles against youtube/search, news/search, and tiktok/search.
  5. Score every piece with the prioritization rubric below and sort.
  6. Schedule into a cadence the team can hold — hub pages before their spokes, decision/consideration pieces early, awareness backfilled for compounding traffic.
  7. State sources and dates so the plan is reproducible.

Output: content strategy

markdown
# Content Strategy — <brand> — <date>

Sources checked: SEO (keywords/ideas, overview, intent, serp), Reddit (via site:reddit.com SERP), YouTube, News, TikTok. Date range: <range>.

## Pillars (3–5)

| Pillar           | Archetype   | Demand evidence (volume + community, with URLs)                                     | Product connection       |
| ---------------- | ----------- | ----------------------------------------------------------------------------------- | ------------------------ |
| Pricing strategy | product-led | "saas pricing" 2.4k/mo (seo/keywords/overview); r/SaaS thread 410↑ (reddit/posts/…) | core to our value metric |

## Topic-cluster map

| Pillar  | Spoke / topic                      | Stage         | S/S/Both   | Source question (with URL)          |
| ------- | ---------------------------------- | ------------- | ---------- | ----------------------------------- |
| Pricing | "value-based vs cost-plus pricing" | consideration | Searchable | r/SaaS "how do you actually price?" |

## Prioritized content calendar

| Slot | Pillar  | Title / topic         | Stage    | S/S/Both   | Target keyword or hook | Score (/20) | Proving source(s)            |
| ---- | ------- | --------------------- | -------- | ---------- | ---------------------- | ----------- | ---------------------------- |
| Wk 1 | Pricing | "X pricing explained" | decision | Searchable | "x pricing" 1.2k/mo    | 18          | SEO overview + r/saas thread |

Prioritization rubric

Score every candidate piece 1–5 on four axes, then sum (max 20). This is the original's customer impact 40% / content-market fit 30% / search-or-share potential 20% / resource 10%, expressed as a 5-point scale per axis:

Axis135
Customer impacttangentialusefulmaps to a decision/buying moment
Content-market fitoff-brandadjacentsquarely what the brand can own
Search/share potentiallow volume, no hookmoderatehigh volume or a strong shareable hook
Resource cost (inverted)weeks of worka few daysreusable/fast

Sequence the highest scores first. Hub pages outrank their own spokes regardless of score, because the spokes need the hub to link to. Tie-break toward higher buyer-stage intent (decision > consideration > awareness).

Guardrails

  • Read-only ("eyes, not hands"); public data only. It briefs from public demand; it does not write or publish. The strategy and calendar are the deliverable — the operator's own assistant drafts and ships each piece.
  • Confirmed vs. inferred: don't propose a pillar or topic without demand evidence behind it; no source, no slot on the calendar. Carry real volumes and URLs through — never fabricate numbers.
  • Demand signals (volume, views, upvotes) are public-data estimates — present ranges and dated snapshots, and treat social/AI signals as directional, not guaranteed traffic.
  • Plan a cadence the team can actually sustain; an over-stuffed calendar that stalls is worse than a short one that ships.
  • For programmatic content at scale, see the programmatic-seo skill; for technical/on-page checks, see seo-audit.
  • content-opportunity-brief (Content Strategy Agent): the ranked, evidence-backed topic list that feeds this strategy.
  • customer-research (Content Strategy Agent): the audience language, pains, and objections that shape pillar selection and messaging.
  • unifapi: the shared data skill — connect MCP and discover the SEO/Reddit/YouTube/News/TikTok operations this strategy reads.

© unifapi-agent, 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 1 other file in skills/content-strategy-agent/content-strategy of unifapi-agent/agents.

  • SKILL.md
  • README.md

Open the folder on GitHubat commit fb53247

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 skillunifapi-agent/agents587—~2.5kAutomated safety check: PassMIT
Contentnotque/vexjoy-agent438—~2.9kAutomated safety check: NotesMIT
Money Socialiamzifei/show-me-the-money1k—~2kAutomated safety check: PassCustom licence
Content Brief Factorygooseworks-ai/goose-skills1.2k1 repos~3.1kAutomated safety check: PassMIT
Viral Short Form Ideasvyralcontent/content-skills1321 repos~2.9kAutomated safety check: PassMIT
Blog StrategyAgriciDaniel/claude-blog2.3k—~4.4kAutomated safety check: PassMIT

Similar skills

  • Content

    notque/vexjoy-agent

    Content operations: editorial calendar, marketing, publishing, social media management.

    438 GitHub stars~2.9k tokensUpdated 5 days ago
    Writing & ContentAuto-check: notes

  • Money Social

    iamzifei/show-me-the-money

    Social media management and community building automation. An agent skill from iamzifei/show-me-the-money.

    1k GitHub stars~2k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • Content Brief Factory

    gooseworks-ai/goose-skills

    Generate detailed, differentiated content briefs at scale. An agent skill from gooseworks-ai/goose-skills.

    1.2k GitHub starsUsed in 1 repo~3.1k tokens
    Writing & ContentAuto-check passed

  • Viral Short Form Ideas

    vyralcontent/content-skills

    Generate short-form video ideas at volume and stop the blank-page problem for good.

    132 GitHub starsUsed in 1 repo~2.9k tokens
    Media & CreativeAuto-check passed

  • Blog Strategy

    AgriciDaniel/claude-blog

    Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI…

    2.3k GitHub stars~4.4k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

  • Blog Strategy

    Infrasity-Labs/dev-gtm-claude-skills

    Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI…

    139 GitHub stars~3.8k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed

More from unifapi-agent/agents

All 47 skills in this repo

  • LLM Mention Tracking

    unifapi-agent/agents

    When the user wants to track how often their brand or domain gets mentioned across ChatGPT and AI search engines over a set of prompts, and how that share of voice compares to named competitors over…

    587 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Buying Signal Monitor

    unifapi-agent/agents

    When a seller or SDR wants to catch public buying intent on X/Twitter and LinkedIn — someone asking for a tool they sell, complaining about or switching off a competitor, or hiring for a role that…

    587 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Customer Research

    unifapi-agent/agents

    When the user wants to research customers from public communities, or synthesize customer language, pains, and objections.

    587 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Keyword Research

    unifapi-agent/agents

    When the user wants to research keywords, find keyword opportunities, run a keyword gap analysis, build topic clusters, or compare what competitors rank for.

    587 GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Schema

    unifapi-agent/agents

    When the user wants to add, fix, or optimize schema markup and structured data on their site.

    587 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

  • SEO Audit

    unifapi-agent/agents

    When the user wants to audit, review, or diagnose SEO issues on their site.

    587 GitHub stars~3.4k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Content Strategy

What does Content Strategy do?

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Content Strategy is an agent skill from unifapi-agent/agents. When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover.

When should I use Content Strategy?

Content Strategy fits situations like: wants to plan a content strategy; decide what content to create; figure out what topics to cover; the user mentions content strategy.

How do I install Content Strategy in Claude Code?

Run `npx skills add unifapi-agent/agents --skill content-strategy -a claude-code`. Or copy the skill folder (skills/content-strategy-agent/content-strategy in unifapi-agent/agents) 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 unifapi-agent/agents --skill content-strategy -a codex`. Or copy the skill folder (skills/content-strategy-agent/content-strategy in unifapi-agent/agents) 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 unifapi-agent/agents --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 (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Content Strategy use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Content Strategy?

Skills that share tags, products or a category with Content Strategy: Content (notque/vexjoy-agent, 438 stars), Money Social (iamzifei/show-me-the-money, 1k stars), Content Brief Factory (gooseworks-ai/goose-skills, 1.2k stars) and Viral Short Form Ideas (vyralcontent/content-skills, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Content Strategy?

unifapi-agent (a GitHub organization) maintains it in unifapi-agent/agents, which has 587 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on September 5, 2026.

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