can-i-actually-rank
Skill0 starsChanged 4 months agoMITView on GitHub
Check whether a candidate keyword is actually winnable by reading the live SERP, then apply five commercial filters. Ends every candidate in QUALIFY, CONDITIONAL or KILL, kills freely, and never treats vendor authority scores as evidence.
- Reads credentials
In this repository26 other files it gives its agents.
- beat-my-competitorsSkill
- brief-my-writerSkill
- 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
- what-to-target-nextSkill
- write-the-pageSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 24
Run rainmaker context --check first.
- Very specific: line 32
Only the data/ files listed in this skill's Consumes table.
- Very specific: line 34
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
- Very specific: line 40
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.
- Very specific: line 60
After approval, use rainmaker serp --allow-paid "<query>".
- Very specific: line 66
Read the People Also Ask and related searches from the capture when present.
- Distinctive: line 68
Pipeline, not traffic: If this ranks and drives traffic, will any of those readers plausibly buy?
- Distinctive: line 78
Never verdict from volume and difficulty data alone.
- Distinctive: line 82
Never cite a third-party domain authority score anywhere in this skill's reasoning or output.
- Distinctive: line 107
Every candidate has a verdict traceable to a real SERP capture, every CONDITIONAL carries both a condition and a resolution path, every …
≈ “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
can-i-actually-rank
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 |
candidate queries from pick-my-battles or what-to-target-next | what to check | ask the user for a query list |
data/snapshots/<latest>/serp.json | the live SERP capture | run rainmaker serp <query> first for each candidate |
data/snapshots/<latest>/gsc.json | our own demonstrated ceiling at similar volume | continue without the ceiling signal |
context/glossary.md | category terms, for the category-match check | continue, category check assumes present |
Produces
keyword_plan[].verdict (this skill), and blueprint.nodes[].serp_verdict once a blueprint exists.
Refuses when
No SERP capture exists for a candidate. Say: "No SERP capture for '<query>'. Ask me to approve Firecrawl credits, then run rainmaker serp --allow-paid \"<query>\" and re-run this skill." Do not guess a verdict from Ahrefs-style volume data alone; the whole point of this skill is reading the actual SERP.
rainmaker serp spends Firecrawl credits. Ask for approval before running it.
After approval, use rainmaker serp --allow-paid "<query>". Never infer approval
from an ambient FIRECRAWL_API_KEY.
Procedure
- For each candidate, load its
serp.jsoncapture and call the verdict engine (src/serp/verdict.ts computeVerdict), which is the tested, deterministic half of this skill. It returns intent consistency, category presence, the rewarded format, beatability evidence, and a verdict of QUALIFY, CONDITIONAL or KILL. - Read the People Also Ask and related searches from the capture when present; feed them into cluster completeness in
map-my-site. - For every survivor (QUALIFY or CONDITIONAL), apply the five commercial filters, in order, against
context/business.md:- Pipeline, not traffic. If this ranks and drives traffic, will any of those readers plausibly buy? Fail if the keyword attracts an audience the product does not serve, or the traffic signal comes from geographies the site does not sell into.
- ICP match. Does the implied searcher match the ICP on two or more of role, industry, size, problem? Reference
strategy.json.icpandpersonas. - Honest product fit. Can the product genuinely solve the implied problem without a claim it cannot honestly support? Check against "What we will not say" in
business.md. - Alignment. Does the recommendation contradict anything the client has explicitly ruled out?
- Net new or overlap. Does an existing URL already target this intent? If so, this is a refresh or consolidation, never a new page; check
blueprint.jsonandcrawl.jsonbefore proposing anything new.
- A candidate failing any filter moves from QUALIFY or CONDITIONAL to KILL, with the failing filter named as the reason.
- Summarise the two or three kill patterns that eliminated the most candidates. If half the pool died on "wrong category dominates the SERP", that is a positioning problem upstream of content, and it belongs in the summary, not buried in a per-row note.
Decision rules
- Never verdict from volume and difficulty data alone. Read the actual SERP capture every time.
- Kill freely. This skill exists to reduce the candidate pool to only winnable, correctly targeted keywords; keeping marginal ones wastes briefing, writing and publishing effort on targets that will not rank or will not convert.
- "Beatable" requires the named evidence the verdict engine already computed: a lower-page-count competitor, an intent-mismatched result, this site's own demonstrated ceiling, a format gap, or stale top results. Optimism is not evidence and is never added as a sixth reason.
- A CONDITIONAL verdict always carries
conditionandcondition_resolved_by. A condition that cannot be resolved is reclassified as KILL, not left as a permanent soft pass. - Never cite a third-party domain authority score anywhere in this skill's reasoning or output.
Output
## SERP qualification
Checked: <n> QUALIFY: <n> CONDITIONAL: <n> KILL: <n>
<query>: QUALIFY
rewarded format: <format> evidence: <reason>, <reason>
<query>: CONDITIONAL
condition: <text>
resolved by: <text>
<query>: KILL
reason: <text>
Most common kill reasons:
<reason>: <n> candidatesDone when
Every candidate has a verdict traceable to a real SERP capture, every CONDITIONAL carries both a condition and a resolution path, every KILL states which filter or which missing evidence eliminated it, and the summary names the dominant kill pattern.
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.

