follow-the-money
Skill0 starsChanged 4 months agoMITView on GitHub
Show where effort has actually gone versus where money is actually made, by comparing the share of pages, sessions and key events per tier, and assign every cluster the tier its content should occupy.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- buriedsignals/spotlighttheir own version, first seen Aug 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- buriedsignals/spotlight★ 60same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- beat-my-competitorsSkill
- brief-my-writerSkill
- can-i-actually-rankSkill
- check-before-i-publishSkill
- explain-this-numberSkill
- find-my-quick-winsSkill
- 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
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Run rainmaker context --check first.
- Very specific: line 31
Only the data/ files listed in this skill's Consumes table.
- Very specific: line 33
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
- Very specific: line 39
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.
- Very specific: line 55
Never refuses outright; degrades.
- Distinctive: line 68
Never assert the imbalance is a mistake.
≈ “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
follow-the-money
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 |
data/snapshots/<latest>/diagnosis.json | tier distribution across all pages | run rainmaker audit |
data/snapshots/<latest>/ga4.json | sessions and key events per tier | continue at confidence 0.5, ranking on sessions only |
data/state.json | which findings are open, so this is grounded in current state | run rainmaker audit |
Produces
clusters[].target_tier (shared owner with pick-my-battles), the revenue narrative section of context/business.md.
Refuses when
Never refuses outright; degrades. With key_events_configured empty, state so in the confidence section, skip every step depending on key events, and rank on sessions with confidence 0.5.
Procedure
- Build the tier distribution table from
state.json: how many pages sit in each tier. - Join sessions and key events per tier from
ga4.json. - Compute, per tier: share of pages, share of sessions, share of key events. The gap between those three shares is the entire point of this skill.
- State the imbalance in one sentence with numbers: for example, "Tier 3 is 78 percent of pages and 6 percent of key events."
- Map every URL in
config.primary_conversionto its measured key events. A declared conversion page with zero key events over the window is the single highest-value finding available here, and it is reported first, above any tier-distribution commentary. - Assign each cluster in
strategy.json.clustersatarget_tier: the tier its content should occupy, which is often not the tier its existing pages currently sit in.
Decision rules
- Never assert the imbalance is a mistake. State the numbers and let the reader draw the conclusion; a 78/6 split might be a deliberate content-marketing strategy with a long payback, and this skill's job is to make the tradeoff visible, not to declare it wrong.
- A zero-key-event declared conversion page is only reported as a finding when
key_events_configuredis non-empty and the page carries no outbound link to a host inconfig.offsite_conversion_hosts. Otherwise it is unmeasured, not broken, perspec/false-positives.mdsection 3.5. target_tieron a cluster may also be set bypick-my-battles; where the two disagree, the more recent write wins and adecisionsentry must explain why.
Output
## Revenue map
Tier 0: <n>% of pages, <n>% of sessions, <n>% of key events
Tier 1: ...
...
Declared conversion pages with zero measured key events:
<url>: 0 key events over <window>d (ga4.json, confidence <c>)
Cluster tier reassignments:
<cluster id>: currently tier <n>, should be tier <n>, because <reason>Done when
The output states, in one sentence with numbers, where effort has gone and where money is made, every cluster has a target_tier, and the confidence section states plainly whether key events were configured.
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.

