content-strategy

content-strategy is a skill for Claude Code, Codex from Maudeunfledged834/startup-founder-skills. It costs 41 tokens per session (1,728 once invoked), scanned A, a copy of content-strategy, MIT.

A plan for deciding what a company should publish, who it is for, and how topics fit together. It can cover content themes, the customer buying journey, formats, and an editorial calendar.

In plain words
What is it for?
Use it to build a content program, choose content types, define topic groups, plan the next 30, 60, or 90 days, or assess existing content.
Why use it?
It helps prevent random publishing and exposes gaps in the topics or stages that content should cover. It also helps choose between search-focused and social content.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to build a content program, choose content types, define topic groups, plan the next 30, 60, or 90 days, or assess existing content.

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

Made for: Claude Code, Codex.

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/maudeunfledged834/startup-founder-skills/content-strategy/github.svg)](https://agentmods.dev/skills/maudeunfledged834/startup-founder-skills/content-strategy)
Your own site
<a href="https://agentmods.dev/skills/maudeunfledged834/startup-founder-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/maudeunfledged834/startup-founder-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/maudeunfledged834/startup-founder-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/maudeunfledged834/startup-founder-skills/content-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,728 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 100% copy Near-identical to another mod 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.00041 $0.01728
Opus 5 $0.00020 $0.00864
Sonnet 5 $0.00008 $0.00346
Haiku 4.5 $0.00004 $0.00173

Measured 11d ago against content hash d654646b3efc, 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.

Origin

This is a copy

100% identical to content-strategy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

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

How it starts

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

Content Strategy

When to Use

  • Building a content program from scratch for a startup.
  • Deciding what content types to invest in first.
  • Identifying content pillars and topic clusters.
  • Planning an editorial calendar for the next 30/60/90 days.
  • Evaluating whether existing content is working and what gaps exist.
  • Choosing between searchable (SEO) and shareable (social) content investments.

Context Required

  • From startup-context: product description, ICP, value proposition, competitive positioning, stage, existing traction, team capacity.
  • From the user: current content assets (if any), distribution channels in use, business goals for content (traffic, leads, brand awareness, thought leadership), team capacity (who writes, how often), target topics or keywords of interest, customer research available (sales calls, surveys, support tickets).

Workflow

  1. Gather context before planning -- Assess four dimensions: (a) business context -- what the company does, who it serves, what problems it solves; (b) customer research -- pre-purchase questions, sales objections, support patterns, customer vocabulary; (c) current state -- existing content performance, available resources, production capabilities; (d) competitive landscape -- what competitors publish, market content gaps.
  2. Classify the content need -- Is the goal searchable content (SEO-driven, captures existing demand) or shareable content (social-native, creates demand)? Most startups need both but should weight based on stage:
    • Pre-PMF: lean toward shareable (faster feedback, builds audience)
    • Post-PMF: lean toward searchable (compounds over time, captures demand)
  3. Identify 3-5 content pillars -- Each pillar is a core topic your brand owns, spawning related content clusters. Use four identification methods:
    • Product-led: Problems your product solves
    • Audience-led: What your ICP needs to learn
    • Search-led: Topic volume in your space
    • Competitor-led: What competitors rank for (and gaps they miss)
    • Pillar criteria: aligns with product, matches audience interests, has search volume or social interest, broad enough for multiple subtopics.
  4. Map content types to pillars -- Select from proven content formats:
    • Use-case content: "[Persona] + [use-case]" targeting long-tail keywords -- bottom of funnel, high intent
    • Hub-and-spoke: Comprehensive pillar page with linked subtopic articles -- SEO authority play
    • Templates and tools: Downloadable resources that solve a micro-problem -- lead generation
    • Thought leadership: Contrarian takes, original data, founder stories -- brand and trust
    • Case studies: Customer transformation stories (Challenge, Solution, Results, Learnings) -- proof
    • Comparison pages: "[Product] vs [Competitor]" -- captures switching intent
    • Data-driven content: Product data analysis (anonymized), public data analysis, original research
    • Expert roundups: 15-30 experts answering one specific question -- built-in distribution
  5. Score and prioritize -- Rate each content idea on four weighted dimensions:
    • Customer impact (40%): Frequency in research, percentage of customers affected, emotional charge
    • Content-market fit (30%): Problem-solution alignment, unique insights available, natural path to product
    • Search potential (20%): Monthly volume, competition level, long-tail opportunities, growth trajectory
    • Resource requirements (10%): Internal expertise, research needs, required assets
  6. Map to buyer journey -- Ensure coverage across awareness stages using keyword modifiers:
    • Awareness: "what is," "how to," "guide to" -- thought leadership, educational content
    • Consideration: "best," "top," "vs," "alternatives" -- comparison pages, how-to guides
    • Decision: "pricing," "reviews," "demo," "trial" -- case studies, use-case content
    • Implementation: "templates," "examples," "tutorial," "setup" -- onboarding content, feature deep-dives
  7. Build the editorial calendar -- Assign content to a realistic publishing cadence. For early-stage: 1-2 high-quality pieces per week beats daily low-effort posts.
  8. Define distribution plan -- Every piece needs a distribution path. Budget 50% of effort for distribution. A great article with no distribution plan underperforms a good article with a strong distribution plan.

Read the full file on GitHub · 87 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 · 87 lines · 41 tokens per session scan A d654646b3efc

Subscribe to this mod's changes

content-strategy is a skill published in the GitHub repository Maudeunfledged834/startup-founder-skills (6 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 1,728 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to content-strategy, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

deploy-site

Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.

microsoft/power-platform-skills · 50 tokens

add-teams

Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.

microsoft/power-platform-skills · 31 tokens

elixir-idioms

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.

oliver-kriska/claude-elixir-phoenix · 44 tokens

tidewave-integration

Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.

oliver-kriska/claude-elixir-phoenix · 38 tokens

security

Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.

oliver-kriska/claude-elixir-phoenix · 47 tokens