pick-my-battles
Skill0 starsChanged 4 months agoMITView on GitHub
Turn account intelligence into content clusters across seven signal types, not just pain points, with a balance check and a completeness gate that refuses a fourth simultaneous cluster while any existing one is under 40 percent covered.
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
- 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
- what-to-target-nextSkill
- write-the-pageSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 23
Run rainmaker context --check first.
- Very specific: line 31
Only the data/ files listed in this skill's Consumes table.
- Very specific: line 33
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
- Very specific: line 39
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.
- Very specific: line 56
Never refuses outright. With no strategy, clusters cannot cite a pain point and this skill should not run.
- Distinctive: line 83
No cluster without a pain point id or a named signal.
- Very specific: line 84
Completeness gate: Before proposing a new cluster, check the completeness of every existing cluster per spec/site-blueprint.md section 8.
- Distinctive: line 102
Every cluster maps to a pain point or a named signal, has an intent and a gap classification, the balance check ran, and the completeness …
≈ “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
pick-my-battles
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 | pain points, personas, competitors as cluster signals | run know-my-buyer first |
data/snapshots/<latest>/gsc.json | head queries and existing coverage | continue, clusters get impressions: 0 |
data/competitors.json | competitor-led and gap signals | run beat-my-competitors first for full coverage |
data/snapshots/<latest>/crawl.json | existing URLs, so gaps are measured against reality | run rainmaker audit |
Produces
clusters (owner). target_tier is shared with follow-the-money.
Refuses when
Never refuses outright. With no strategy, clusters cannot cite a pain point and this skill should not run; direct the user to know-my-buyer first.
Opportunity typology
Clusters come from seven signal types. A system that derives clusters only from pain points misses the fastest commercial content there is.
| Type | Signal source | Typical format |
| Competitor-led | named in interviews or in competitors.json | alternatives, comparison |
| Objection-led | objections in business.md | guide, proof, pricing explainer |
| Feature-led | capabilities that gate plans or recur in sales | feature page, integration page |
| Use-case-led | jobs customers hire the product for | use-case page |
| Vertical-led | industries named in the ICP | vertical landing page |
| Pain-led | buyer_language before they knew the category existed | solution article |
| Winner expansion | pages already ranking, from gsc.json | adjacent page in the same cluster |
Procedure
- One cluster per validated pain point, minimum. Pain points marked
hypothesisproduce clusters markedgap: 'missing', ordered below validated ones. - Work through the other six signal types against
strategy.json,competitors.jsonandcontext/business.md. Every cluster must trace to at least one pain point id or one named signal; a cluster that exists only because a keyword has volume is exactly what this skill exists to prevent. - For each cluster: choose a head query from GSC where an existing query matches the pain or signal language; otherwise propose one and mark
impressions: 0. - Attach existing URLs from
crawl.jsonby matching normalised path and title tokens. Setgap:nonewhen a tier-appropriate page exists,thinwhen it exists under 600 words or without schema,missingotherwise. - Set
intentfrom the query-intent table inskills/_shared/revenue-tiers.md. - Balance check: if any one signal type is more than half of all clusters, name the imbalance explicitly. Competitor-led content alone does not build topical authority; it trades on authority the site does not yet have.
Decision rules
- No cluster without a pain point id or a named signal.
- Completeness gate. Before proposing a new cluster, check the completeness of every existing cluster per
spec/site-blueprint.mdsection 8. Refuse to open a fourth simultaneous cluster while any existing one sits below 40 percent covered. Three half-covered clusters beat nothing; six quarter-covered clusters beat nothing at all. - Where completeness cannot be computed because no SERP capture has run, say so; the gate reports "cannot evaluate" rather than silently passing or blocking.
Output
## Clusters
<cluster id>: <head query>, intent <x>, target tier <n>, gap <none|thin|missing>
Signal: <type>, <specific evidence>
Existing: <url or "none">
Balance: <type> is <n>% of clusters (<flag if over 50%>)
Completeness gate: <passed / refused a new cluster, naming which existing cluster is under 40%>Done when
Every cluster maps to a pain point or a named signal, has an intent and a gap classification, the balance check ran, and the completeness gate either passed or named the blocking cluster.
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.

