unblock-my-money-pages
Skill0 starsChanged 4 months agoMITView on GitHub
Find what is technically stopping the pages closest to revenue from working, ordered by distance to money rather than by severity. Reads the diagnosis the core already wrote; it never re-crawls.
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
- 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
- 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
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Run rainmaker context --check first.
- Very specific: line 32
Only the data/ files listed in this skill's Consumes table.
- Very specific: line 34
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
- Very specific: line 40
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.
- Very specific: line 56
No diagnosis exists: "No diagnosis yet.
- Very specific: line 61
Read diagnosis.json. Group findings by tier, never by check type.
- Very specific: line 72
Never report a finding without its tier_source.
- Distinctive: line 73
Never recommend a fix whose effort exceeds the finding's own listed hours without saying why the table is wrong.
- Distinctive: line 90
Every line names a URL, a measured value, an effort figure and a tier source.
≈ “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
unblock-my-money-pages
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 | the findings, already scored | "No diagnosis yet. Run rainmaker audit." |
data/snapshots/<latest>/crawl.json | page-level evidence | same |
data/state.json | what is already known and what was shipped | run rainmaker ledger --rebuild |
Produces
Nothing. The diagnosis is written by src/, and a skill that re-derives a score is a defect.
Refuses when
- No diagnosis exists: "No diagnosis yet. Run
rainmaker audit. Reading a site I have not measured produces a checklist, not a finding." - The latest diagnosis predates the latest crawl: say so, and run
rainmaker audit --refresh.
Procedure
- Read
diagnosis.json. Group findings by tier, never by check type. Tier 0 leads, always. - Within each tier, keep the order the core produced. It is already score descending, id ascending, and reordering it makes two reports of the same data disagree.
- Report reachability first: noindex, canonical to an error, canonical chains, 4xx and 5xx. A page in that state cannot earn a score at all, which is the one case where ordering overrides the number.
- Then structure: orphans, click depth over 3 for tier 0 and 1, duplication.
- Then metadata and content: titles, meta descriptions, H1s, thin pages.
- Report suspicions in their own section, each with what would confirm it. Never mix them into the ranked list.
- Close with the confidence section: which capabilities were live, and what their absence weakens.
Decision rules
- A tier 0 page that is unreachable outranks any tier 1 item regardless of score.
- Never report a finding without its
tier_source. A tier fromurl_patternis a guess and a reader who cannot see that will read it as measured. - Never recommend a fix whose effort exceeds the finding's own listed hours without saying why the table is wrong.
- Say what is not broken. A reader who only ever sees problems cannot calibrate.
Output
## 1. What changed
## 2. Why it matters
## 3. What to do
<path> tier <n> <check> <effort>h score <x>
<one sentence, the measured value, the file it came from>
## 4. What we are watching
## 5. ConfidenceDone when
Every line names a URL, a measured value, an effort figure and a tier source; suspicions are separated; and the confidence section lists the capabilities that were missing.
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.

