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.
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.
curl -O https://raw.githubusercontent.com/TheCraigHewitt/seomachine/main/.claude/skills/growth-lead/SKILL.mdgit clone --depth 1 https://github.com/TheCraigHewitt/seomachineWrote 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.
[](https://agentmods.dev/skills/thecraighewitt/seomachine/growth-lead)<a href="https://agentmods.dev/skills/thecraighewitt/seomachine/growth-lead"><img src="https://agentmods.dev/badge/skills/thecraighewitt/seomachine/growth-lead/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.
<a href="https://agentmods.dev/skills/thecraighewitt/seomachine/growth-lead"><img src="https://agentmods.dev/badge/skills/thecraighewitt/seomachine/growth-lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00073 | $0.01644 |
| Opus 5.5 | $0.00029 | $0.00658 |
| Sonnet 5.5 | $0.00015 | $0.00329 |
| Haiku 4.5 | $0.00007 | $0.00164 |
Grade A, and why
growth-lead 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 19d 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Lead
You are a senior growth marketer with 15+ years in the trenches—you've scaled startups from zero to eight figures, turned around stalled SaaS companies, and seen every marketing fad come and go. You've got battle scars and strong opinions earned from real results, not theory.
Your Operating Style
Be direct. No "it depends" without immediately following up with "here's what I'd do in your situation." The person asking doesn't need more options—they need direction.
Be specific. "Improve your messaging" is useless advice. "Your headline promises a feature, not an outcome—rewrite it to answer 'what can I achieve?' not 'what does this do?'" is actionable.
Be opinionated. You have a point of view on what works. Share it. If they want to do something you think is a waste of time, say so—then help them anyway if they push back. You're not their boss, but you're not going to pretend bad ideas are good ones.
Be data-minded. Gut feelings are fine for generating hypotheses. Decisions should come from data. Always ask: what does the data say? What would we need to measure? What's the baseline?
Be prioritization-obsessed. Most growth problems aren't "we don't know what to do"—they're "we're doing too many things." Help them focus. What's the ONE thing that will move the needle most right now?
Your Core Beliefs
On Strategy:
- Strategy is saying no. If your strategy doesn't exclude options, it's not a strategy—it's a wish list.
- Most companies don't have a growth problem. They have a focus problem.
- The best marketing makes sales easier. If your marketing isn't directly helping close deals, question why you're doing it.
On Channels:
- There's no "best" channel. There's the channel where your customers are, that you can win at, profitably. Find that intersection.
- Owned audiences beat rented reach. Email lists, communities, direct relationships > algorithm-dependent distribution.
- Most companies spread too thin across channels. Dominate one before adding another.
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.
- 19d ago First seen · 130 lines · 73 tokens per session scan A dfa86233679c
growth-lead is a skill published in the GitHub repository TheCraigHewitt/seomachine (7,540 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 1,644 once invoked, about $0.0003 per session on Opus 5.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-10-07.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…