seomachine: Skill for Claude Code

.claude/skills/content-strategy/SKILL.md

content-strategy is a skill for Claude Code from TheCraigHewitt/seomachine. It costs 81 tokens per session (2,556 once invoked), scanned A, original, MIT.

A planning guide for deciding what content to create, who it is for, and which topics support a business goal such as attracting visitors or generating leads.

In plain words
What is it for?
Use it to plan blog topics, searchable topic groups, content formats, customer-focused articles, and a broader publishing strategy.
Why use it?
It turns scattered content ideas into a plan based on the audience, customer questions, business needs, and available resources.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is TheCraigHewitt/seomachine's own configuration. It tells Claude Code how to work on seomachine itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything seomachine configures →

About the project

SEO Machine is a Claude Code workspace for researching, writing, analyzing, and improving long-form search-optimized business content. It is intended for marketers and content teams that need structured workflows for articles, landing pages, keyword research, conversion optimization, and performance analysis. Its catalogued skills, commands, and agents provide the workspace’s content and SEO workflow.

TheCraigHewitt/seomachine · 7,427 stars · on GitHub · seomachine.io

Reuse

Borrowing it

Nothing to install: this file belongs to TheCraigHewitt/seomachine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/TheCraigHewitt/seomachine/main/.claude/skills/content-strategy/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/TheCraigHewitt/seomachine

Made for: Claude Code.

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/thecraighewitt/seomachine/content-strategy/github.svg)](https://agentmods.dev/skills/thecraighewitt/seomachine/content-strategy)
Your own site
<a href="https://agentmods.dev/skills/thecraighewitt/seomachine/content-strategy"><img src="https://agentmods.dev/badge/skills/thecraighewitt/seomachine/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/thecraighewitt/seomachine/content-strategy"><img src="https://agentmods.dev/badge/skills/thecraighewitt/seomachine/content-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,556 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00081 $0.02556
Opus 5 $0.00041 $0.01278
Sonnet 5 $0.00016 $0.00511
Haiku 4.5 $0.00008 $0.00256

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

Copies of this mod

8 near-identical copies found in the catalogue:

.claude/skills/content-strategy/SKILL.md · 357 lines

How it starts

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

Content Strategy

You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.

Before Planning

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Business Context

  • What does the company do?
  • Who is the ideal customer?
  • What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)
  • What problems does your product solve?

2. Customer Research

  • What questions do customers ask before buying?
  • What objections come up in sales calls?
  • What topics appear repeatedly in support tickets?
  • What language do customers use to describe their problems?

3. Current State

  • Do you have existing content? What's working?
  • What resources do you have? (writers, budget, time)
  • What content formats can you produce? (written, video, audio)

4. Competitive Landscape

  • Who are your main competitors?
  • What content gaps exist in your market?

Searchable vs Shareable

Every piece of content must be searchable, shareable, or both. Prioritize in that order—search traffic is the foundation.

Searchable content captures existing demand. Optimized for people actively looking for answers.

Shareable content creates demand. Spreads ideas and gets people talking.

When Writing Searchable Content

  • Target a specific keyword or question
  • Match search intent exactly—answer what the searcher wants
  • Use clear titles that match search queries
  • Structure with headings that mirror search patterns
  • Place keywords in title, headings, first paragraph, URL
  • Provide comprehensive coverage (don't leave questions unanswered)
  • Include data, examples, and links to authoritative sources
  • Optimize for AI/LLM discovery: clear positioning, structured content, brand consistency across the web

Read the full file on GitHub · 357 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 · 357 lines · 81 tokens per session scan A 1fb9d6c57f1b

Subscribe to this mod's changes

content-strategy is a skill published in the GitHub repository TheCraigHewitt/seomachine (7,427 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 2,556 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens