saas-content-strategy

saas-content-strategy is a skill for Claude Code from jonbishop1/saas-marketing-skills. It costs 209 tokens per session (5,420 once invoked), scanned A, original, MIT.

A content-strategy guide for developers and technical founders building software products, APIs, or SaaS businesses. SaaS means software delivered as an online service rather than installed and managed entirely by the customer.

In plain words
What is it for?
Use it for content planning, editorial roadmaps, content audits, topic prioritisation, channel choices, and content-market-fit questions; specialised skills handle SEO research, copywriting, production, and promotion.
Why use it?
It helps choose content topics, formats, channels, and priorities based on the product, audience, and available resources.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents).

Part of the saas-marketing-skills plugin — 16 skills shipped together

Good fit Use it for content planning, editorial roadmaps, content audits, topic prioritisation, channel choices, and content-market-fit questions; specialised skills handle SEO research, copywriting, production, and promotion.

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

Made for: Claude Code.

Or install saas-marketing-skills, the plugin that ships this one along with the rest of its 16 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 saas-content-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonbishop1/saas-marketing-skills/saas-content-strategy/github.svg)](https://agentmods.dev/skills/jonbishop1/saas-marketing-skills/saas-content-strategy)
Your own site
<a href="https://agentmods.dev/skills/jonbishop1/saas-marketing-skills/saas-content-strategy"><img src="https://agentmods.dev/badge/skills/jonbishop1/saas-marketing-skills/saas-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 saas-content-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonbishop1/saas-marketing-skills/saas-content-strategy"><img src="https://agentmods.dev/badge/skills/jonbishop1/saas-marketing-skills/saas-content-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 209 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,420 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.00209 $0.05420
Opus 5 $0.00105 $0.02710
Sonnet 5 $0.00042 $0.01084
Haiku 4.5 $0.00021 $0.00542

Measured 12d ago against content hash 43d9ed3abfab, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

saas-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 12d 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.

.agents/skills/saas-content-strategy/SKILL.md · 414 lines

How it starts

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

Content Strategy for Software Products

Audience: developers and technical founders. You are an expert content strategist and coach — not a content calendar generator. Your job is to understand the founder's situation thoroughly, then coach them through what to create, why, for whom, and when — calibrated to their actual resources, not an ideal scenario. Produce strategy deliverables only when asked or when demonstrating a framework.

Before advising, read references/background.md from the saas-marketing-background skill at saas-marketing-background/references/background.md and gather missing background. Then layer on the content-strategy-specific intake below.

Skill handoffs:

  • For SEO keyword research, topic research, or competitive SEO analysis → hand off to saas-seo-research
  • For copywriting (headlines, messaging, meta descriptions, email copy) → hand off to saas-copywriting
  • For actual content writing, editing, and publishing workflows → hand off to saas-content-production
  • For content distribution and promotion strategy → hand off to saas-marketing-plan

Table of Contents

  1. Your Role
  2. Situation Analysis — Do This First
  3. Resource Tiers — Match Strategy to Reality
  4. Pre-Launch: Speed to Live
  5. Channel Strategy
  6. Editorial Planning
  7. Content Audits — Post-Launch Sites
  8. Competitor Content Analysis
  9. Content-Market Fit
  10. Measuring Content Strategy
  11. Common Mistakes
  12. Reference Files

Your Role

You are a senior content strategist who speaks engineer. Your process:

  1. Understand — the product, the audience, the stage, the resources, and the competitive landscape before suggesting anything
  2. Diagnose — what's the content situation today? What's missing, what's working, what's wasted?
  3. Strategize — recommend what content to create, on which channels, in what order, and why
  4. Coach — give frameworks and reasoning; the founder who understands why will make better ongoing decisions than one handed a calendar
  5. Plan — produce editorial calendars and content roadmaps when asked, calibrated to the founder's tier
  6. Route — hand off to the right skill when the work shifts from strategy to execution

Read the full file on GitHub · 414 lines

Files

What ships with it

1 file 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. 12d ago First seen · 414 lines · 209 tokens per session scan A 43d9ed3abfab

Subscribe to this mod's changes

saas-content-strategy is a skill published in the GitHub repository jonbishop1/saas-marketing-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 209 tokens to every session and 5,420 once invoked, about $0.0010 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

chief-revenue-officer

Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…

cbrock84/headcount · 80 tokens

seo-strategy

Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…

cbrock84/headcount · 74 tokens

financial-statement-analysis

Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…

cbrock84/headcount · 93 tokens

youtube-producer

Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…

cbrock84/headcount · 86 tokens

scenario-planning

Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold…

cbrock84/headcount · 78 tokens

ai-ml-governance

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory…

cbrock84/headcount · 83 tokens