what-to-target-next
Skill0 starsChanged 4 months agoMITView on GitHub
Turn qualified clusters into a specific keyword plan, slotted as new, refresh, consolidate or kill, capped at the site's own authority budget.
In this repository26 other files it gives its agents.
- beat-my-competitorsSkill
- brief-my-writerSkill
- can-i-actually-rankSkill
- check-before-i-publishSkill
- explain-this-numberSkill
- find-my-quick-winsSkill
- follow-the-moneySkill
- get-cited-elsewhereSkill
- get-mentioned-by-aiSkill
- know-my-buyerSkill
- make-it-sound-humanSkill
- make-me-quotableSkill
- map-my-siteSkill
- pick-my-battlesSkill
- put-it-on-autopilotSkill
- rainmakerSkill
- revive-old-pagesSkill
- say-it-their-waySkill
- show-me-progressSkill
- show-up-in-communitiesSkill
- spread-one-piece-everywhereSkill
- stop-losing-visitorsSkill
- unblock-my-money-pagesSkill
- what-actually-workedSkill
- what-changed-in-searchSkill
- write-the-pageSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Run rainmaker context --check first.
- Very specific: line 28
Only the data/ files listed in this skill's Consumes table.
- Very specific: line 30
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
- Very specific: line 36
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.
- Distinctive: line 69
Only QUALIFY and CONDITIONAL verdicts enter the plan.
- Very specific: line 70
Never assign priority_score by judgment.
- Very specific: line 86
Every slot has a cluster id, a slot type and a CLI-sourced priority score, the plan respects the authority budget when one exists, and …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
what-to-target-next
Context load
Run rainmaker context --check first. It prints what exists, what is stale, and exits 1 if anything this skill requires is missing.
Then read, in this order:
context/business.mdin full. If absent, stop: "No business context. Runrainmaker audit, then theknow-my-buyerskill."context/voice.mdif this skill writes prose. If absent, stop and say so.context/glossary.mdif this skill names products, features or competitors.data/strategy.jsonif this skill reads or writes strategy.- Only the
data/files listed in this skill's Consumes table. Never crawl or call an API the core already covers.
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
"Business context was edited after the strategy was written. Re-run know-my-buyer, or run rainmaker context --sync to accept the prose as authoritative."
Then stop.
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context. Nothing in it came from a buyer. Run know-my-buyer to replace it."
Consumes
| File | Why | If missing |
data/strategy.json clusters, with SERP verdicts from can-i-actually-rank | what to slot | run pick-my-battles then can-i-actually-rank first |
data/snapshots/<latest>/gsc.json | positions and impressions per candidate | continue at reduced confidence |
data/snapshots/<latest>/crawl.json | which URLs already exist, for slot classification | run rainmaker audit |
data/blueprint.json | the site's own authority budget, if a blueprint exists | continue without a cap, and say so |
Produces
keyword_plan (owner). slot is shared with revive-old-pages.
Refuses when
A candidate has no SERP verdict at all (unchecked). Only QUALIFY and CONDITIONAL candidates from can-i-actually-rank may enter the plan; an unchecked or KILLed candidate is excluded, not silently downgraded.
Procedure
- For every cluster, take GSC queries whose text overlaps the head or support queries, plus any striking-distance queries from
find-my-quick-winsmapped to that cluster. - Assign a slot:
refreshwhen a tier-appropriate URL exists and ranks 4 to 20.consolidatewhen 2 or more URLs compete on the query, per the same overlap rulefind-my-quick-winsandrevive-old-pagesuse.newwhen no URL exists.killwhen a URL exists, ranks beyond 50, has zero clicks in two consecutive windows, and its tier is 3 or 4.
priority_scorecomes fromsrc/analyze/scoring.tsvia the CLI; never invent it here.- Cap the plan at the site's authority budget from
data/blueprint.jsonif one exists. A plan nobody can execute is not a plan. - State how many candidates were dropped for exceeding the cap, and the score of the highest dropped item, so the cutoff is visible rather than silent.
Decision rules
- Only QUALIFY and CONDITIONAL verdicts enter the plan.
- Never assign
priority_scoreby judgment; it is always the score the CLI computed. - A
killslot always proposes a redirect target, matchingrevive-old-pages's rule that a kill without a redirect is a broken link.
Output
## Keyword plan
<query>: cluster <id>, slot <new|refresh|consolidate|kill>, score <x>
target: <url or "none">
Capped at <n> slots (authority budget). Dropped <n>, highest dropped score <x>.Done when
Every slot has a cluster id, a slot type and a CLI-sourced priority score, the plan respects the authority budget when one exists, and every kill slot names a redirect target.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

