map-my-sitelisted

Turn the keyword plan into the whole intended site as a tree: one intent per URL, a parent for every node, titles and metas generated as a consistent set, permutations gated against doorway-page risk, and a publish rate bounded by what the site has demonstrated it can get indexed. Use this skill whenever the user asks to: - Plan their site structure or URL architecture - Decide how to organise services, locations, or product pages - Check whether their site is scaling permutations safely - Understand how many pages they can realistically publish per month Trigger even for casual requests like "site structure", "how should we organise the site", "map my site", "should each city get its own page", "how many pages can we publish a month".
vcxcvii/rainmaker · ★ 0 · AI & Automation · score 67

Install: claude install-skill vcxcvii/rainmaker

# map-my-site ## 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 | |---|---|---| | `data/strategy.json` keyword_plan and clusters | what the tree is built from | run `what-to-target-next` first | | `data/snapshots/<latest>/crawl.json` | existing pages, matched before planning new ones | run `rainmaker audit` | | SERP verdicts from `can-i-actually-rank` | page type follows what actually ranks | unch