explain-this-numberlisted

Explain what a search, analytics or AI-visibility metric actually means, how it is commonly misread, and what to say instead. Reference only: it decides nothing and writes nothing, and every other Rainmaker skill cites it rather than restating a definition. Use this skill whenever the user asks to: - Understand what a metric means: sessions, impressions, average position, INP, key events - Work out why two tools disagree, most often GA4 against Search Console - Check whether a number in a report is being read correctly - Sanity-check a claim someone made using a metric - Understand an AI-search term: citation, extractability, entity, llms.txt Trigger even for casual requests like "what does average position actually mean", "why doesn't GA4 match Search Console", "is domain authority real", "what's INP", "our CTR dropped, is that bad", or when a user pastes a number from a dashboard and asks whether it is good.
vcxcvii/rainmaker · ★ 0 · AI & Automation · score 67

Install: claude install-skill vcxcvii/rainmaker

# Explain this number ## 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." **This skill is the one exception to the stop rules above.** A user asking what a metric means is entitled to an answer whether or not a context exists. Skip straight to the procedure, and mention the missing context only if the question is about their own numbers rather than about the metric. ## Consumes | File | Why | If missing | |---|---|---| | `skills/_share