can-i-actually-ranklisted

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. Use this skill whenever the user asks to: - Check whether they can rank for a keyword before building content - Qualify or kill a list of keyword candidates - Understand what format Google actually rewards for a query - Decide whether a topic is worth the effort Trigger even for casual requests like "can we rank for this", "check the SERPs for these keywords", "is this winnable", "should we bother with this keyword", "qualify this list".
vcxcvii/rainmaker · ★ 0 · AI & Automation · score 70

Install: claude install-skill vcxcvii/rainmaker

# 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: 1. `context/business.md` in full. If absent, stop: "No business context. Run `rainmaker audit`, then the `know-my-buyer` skill." 2. `context/voice.md` if this skill writes prose. If absent, stop and say so. 3. `context/glossary.md` if this skill names products, features or competitors. 4. `data/strategy.json` if this skill reads or writes strategy. 5. 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 sim