agent-context-audit
Audit a repo's agent context — CLAUDE.md files, codebase docs, skills, and tool/MCP designs — against Anthropic's Claude 5 context-engineering guidance…
Use when deciding WHERE to point SEO effort, not how to write a page. Triggers: a new site or brand with no rankings and no authority ("cold start", "starting from zero", "nobody knows us"), deciding what to double down on, a page or cluster that ranks but earns nothing, hunting
$ npx -y skills add AI-Builder-Club/skills --skill seo-growth --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/seo-growthContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when deciding WHERE to point SEO effort, not how to write a page. Triggers: a new site or brand with no rankings and no authority ("cold start", "starting from zero", "nobody knows us"), deciding what to double down on, a page or cluster that ranks but earns nothing, hunting
name: seo-growth
description: >
Use when deciding WHERE to point SEO effort, not how to write a page. Triggers: a new
site or brand with no rankings and no authority ("cold start", "starting from zero",
"nobody knows us"), deciding what to double down on, a page or cluster that ranks but
earns nothing, hunting emerging or newly-coined keywords before competitors arrive,
"should we build a cluster or one page", "what do we write next", "we get impressions
but no clicks", "our traffic plateaued despite publishing", whether to chase a head
term at all, or turning any of it into recurring automation. Also use when asked why
an SEO effort stalled despite consistent output. NOT for writing an article,
keyword expansion mechanics, or auditing a single tactic for penalty risk.**Core principle: the right move depends on whether you have data yet, and most bad SEO advice is given to the wrong one of those two situations.** A site with no rankings and a site with a breadwinner page need opposite behavior. Advice that ignores which you are in is how efforts stall despite consistent output.
Distilled from two content properties run in production and the Search Console reads that produced each rule. This is **a first-party method**: narrower than a general playbook, and more trustworthy for it. Every rule traces to the failure or result behind it in `references/why-these-rules.md`. Absolute traffic figures are withheld; the ratios and thresholds are as observed.
| You are here if… | Playbook | Read | |---|---|---| | No rankings, no authority, <100 clicks/mo, possibly no content | **A — Cold start** | `references/cold-start.md` | | GSC has real rows: something ranks, something earns clicks | **B — With data** | `references/with-data.md` |
**Diagnose per cluster, not per site.** A mature site opening a new territory is in Playbook A for that territory and Playbook B everywhere else — and that combination is the strongest position in the method.
**Playbook A in one line:** you cannot win an established term from zero authority, so hunt an emerging one, ship ONE page, and let day-7 / day-21 decide whether it was real.
**Playbook B in one line:** your own GSC already knows which page shapes win for you — find the breadwinner, extract the shape, diagnose whether it is position-limited or snippet-limited, compound it, and protect it while you do.
thing that works in Playbook A. Where to look, in what order, and the seven gates a candidate must pass.
families that never click, and the GSC traps that produce confident wrong conclusions.
Pull a 28-day GSC window ending **3 days back** (GSC lags 2–3 days):
1. **Total clicks** — the scale, and which playbook you are in. 2. **Breadwinner share** — what % of clicks the single best page earns. 3. **Best non-brand position** — where you rank on something you don't own by name.
If these aren't available, say so and instrument first. Advising without them is guessing, and it is the most common failure mode in this whole area.
1. **A low-authority domain can only win a term while competition is thin.** So a cold start doesn't "do SEO" — it hunts emerging terms. Validated on two separate terms, months apart. 2. **Score an emerging term on position, a mature one on clicks.** Backwards, and the metric tells you to quit the land-grab exactly as the ground becomes valuable — or leaves a page at 0.53% CTR untouched for a month because its rank looked fine. 3. **Impressions are not progress.** The trap is a page drawing a very large impression base relative to the rest of the site at 0.2% CTR. It feels like traction and converts nothing. Rank work by click opportunity from *human* queries. 4. **Concentration is the goal, not the problem.** One page earning ~45% of clicks is healthy. Compound the winner before adding breadth. 5. **What you double down on is derived, not chosen.** Read your own GSC for which *shapes* win, then repeat the shape — not just the page.
| Question | Short answer | Detail | |---|---|---| | Cold start, what now? | Instrument, then land ONE emerging term. Not a cluster. | cold-start | | Cluster or one page? | One page until the term proves itself. Cluster after. | cold-start | | How do I find emerging terms? | Your own saved stream → repo/release feeds → social listening → diff vs your pages | emerging-terms | | Is this term worth it? | Seven gates; failing one drops it, and dropping is normal | emerging-terms | | What do we double down on? | The page at ≥30% of clicks — and the archetype it belongs to | with-data | | Ranks well, no clicks? | Screen the query mix first. Most such pages are not broken. | with-data, measurement | | Traffic plateaued despite publishing | The cluster saturated. Open a new front, don't add pages to it. | with-data §7 | | When do I stop land-grabbing? | Three computable numbers, never a vibe | measurement | | How do I stop doing this by hand? | Four loop roles, never one loop | operationalize |
one verified family ranked position 4.7–5.8 for **exactly 0 clicks** and was working perfectly.
A Claude Code plugin marketplace of the skills we share at for building loop engineers: agents that get triggered on their own, pick up work, ship it, verify it, and log what they learned, so the work compounds without you prompting every step.
Repo: AI-Builder-Club/skills
Audit a repo's agent context — CLAUDE.md files, codebase docs, skills, and tool/MCP designs — against Anthropic's Claude 5 context-engineering guidance…
Scaffold an isolated CLOUD dev box per agent (via crabbox + Daytona) for any codebase — the parallel-safe counterpart to dev-local-setup. Each agent gets its…
Scaffold a one-command `dev-local` launcher for ANY codebase. Investigates the repo to find its services, ports, and infra dependencies, then generates a…
Set up an end-to-end test suite in any repo, following practices that make e2e a reliable per-PR gate: real flows over bypass, layered assertions, a reusable…
Spin up a new loop (domain) in a file-based knowledge base — bootstrap the substrate if it's missing, gather the loop's charter, scaffold…
Delegate tasks to ANY CLI agent (claude, codex, aider, ...) running in a detached tmux session, with a race-safe done-signal protocol and multi-turn iteration.…