explain-this-number
Skill0 starsChanged 4 months agoMITView on GitHub
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.
In this repository26 other files it gives its agents.
- beat-my-competitorsSkill
- brief-my-writerSkill
- can-i-actually-rankSkill
- check-before-i-publishSkill
- 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
11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 26
Run rainmaker context --check first.
- Very specific: line 34
Only the data/ files listed in this skill's Consumes table.
- Very specific: line 36
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
- Very specific: line 42
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.
- Very specific: line 62
Read the entry in skills/_shared/metric-definitions.md.
- Very specific: line 63
If the question is about the user's own number, read the relevant snapshot and quote the actual value with full provenance per …
- Distinctive: line 64
If two tools disagree, name the structural reason rather than calling it a bug.
- Distinctive: line 65
If the term is missing from the definitions file, say so, answer carefully from first principles, and flag that the file needs the term …
- Distinctive: line 69
Never say a number is good or bad without its comparison basis.
- Distinctive: line 70
Never compare a metric across tools without naming the definitional gap first.
- Distinctive: line 71
Never quote a vendor authority score as an input to ranking.
≈ “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
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:
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."
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/_shared/metric-definitions.md | the canonical definitions | this skill cannot run; the file is part of the package |
data/snapshots/<latest>/*.json | only when the user asks about their own number | answer the general question and say the site data is absent |
Produces
Nothing. This skill decides nothing and writes nothing. It exists so that no other skill has to carry a definition, and so that every number in every report traces back to one agreed meaning.
Procedure
- Identify which term is actually in play. Users often name a different metric from the one they are looking at: "traffic" might be sessions, users, clicks or impressions, and the answer differs for each.
- Read the entry in
skills/_shared/metric-definitions.md. Give all three parts: what it is, how it is usually misread, and what to say instead. The second part is usually the one they needed. - If the question is about the user's own number, read the relevant snapshot and quote the actual value with full provenance per
skills/_shared/evidence-rules.md. Never invent an illustrative figure when a real one is available. - If two tools disagree, name the structural reason rather than calling it a bug. Most disagreements are definitional: different identity models, different windows, different attribution, different sampling, or bot filtering applied at different points.
- If the term is missing from the definitions file, say so, answer carefully from first principles, and flag that the file needs the term added. Do not quietly invent an entry.
Decision rules
- Never say a number is good or bad without its comparison basis. Good against what: the site's own prior window, the CTR curve at that position, or the threshold published by the tool.
- Never compare a metric across tools without naming the definitional gap first.
- Never quote a vendor authority score as an input to ranking. Say what it is: a third-party prediction.
- Where a metric is an average of averages, say so before anything else. Average position is the common case and the most consequential.
Output
Short. Three parts, then the user's actual number if there is one.
Average position is the average rank of your URL for that query across every
impression in the window, blended across devices and countries.
Commonly misread as a rank. A page sitting at 3 in the UK and 30 in the US
reports around 16, a position it has never actually held.
Say instead: "average position 16, blended across markets", and filter by
market before drawing any conclusion.
Yours: /pricing averages 8.4 for "clm pricing" (gsc.json, 28d to 2026-08-09,
confidence 0.7). You sell into the UK and the US, and those two markets are
not separated in that number.Done when
The user knows what the metric measures, the most likely way they were about to misread it, and the sentence to use instead. If their own number was involved, it carries file, field, window and confidence.
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.

