what-actually-worked
Skill0 starsChanged 4 months agoMITView on GitHub
Answer three questions in order: what did we believe, what did we do, what actually happened: and always include a mandatory "What did nothing" section, since a retrospective containing only wins is a defect.
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
- unblock-my-money-pagesSkill
- what-changed-in-searchSkill
- what-to-target-nextSkill
- write-the-pageSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Run rainmaker context --check first.
- Very specific: line 30
Only the data/ files listed in this skill's Consumes table.
- Very specific: line 32
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
- Very specific: line 38
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.
- Very specific: line 54
What did we do?: Every ledger event with a cause in the period, grouped by cause, effort hours summed, on-site and off-site work together.
- Distinctive: line 62
Never assert causation. "Position improved after we shipped X" states timing.
- Distinctive: line 88
All five sections are present, section 4 is genuinely non-empty whenever any shipped item failed to move, and no sentence in the report …
≈ “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
what-actually-worked
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/ledger.jsonl, data/state.json | events with cause, baseline vs current | run rainmaker audit |
data/strategy.json and data/strategy-history/ | what we believed at the period's start | run know-my-buyer |
Produces
Nothing persisted directly; may recommend a decisions entry demoting a pain point, applied via say-it-their-way or know-my-buyer.
Procedure
- What did we believe? Diff the current
strategy.jsonagainst the version at the start of the period, usingstrategy-history/. Name every changed belief and thereasonrecorded for it. - What did we do? Every ledger event with a
causein the period, grouped by cause, effort hours summed, on-site and off-site work together. - What happened?
baselineagainstcurrentper finding, only for findings past their own verification window. Usesrc/ledger/query.ts pendingVerificationto exclude anything not yet due, so nothing is judged early. - What did nothing. Mandatory. Call
src/ledger/query.ts didNothing, which separates true failures (comparable metrics, no movement) fromunmeasured(no comparable metric at all, so no verdict either way). List every shipped intervention whose target metric did not move beyond its window, with the effort spent. A retrospective containing only wins is a defect and must be regenerated, not published as-is. - What we cannot attribute. Findings that moved inside a window containing an
algo_updateevent are reported as coincident and explicitly not causal, with the control: did non-matching pages move too?
Decision rules
- Section 4 is never skipped, even when every shipped item worked. State plainly that nothing in the period did nothing, if that is genuinely true.
- Never assert causation. "Position improved after we shipped X" states timing; it does not claim X caused it unless the control (non-matching pages did not move) is also shown.
- Where a belief was contradicted twice across periods, recommend demoting it in
strategy.jsonwith adecisionsentry, and nameknow-my-buyeras the next step if the drift conditions fromspec/site-blueprint.mdsection 8 or the core spec's drift rule fire.
Output
## What did we believe?
<belief>: <held / changed to X, reason: Y>
## What did we do?
<cause>: <n> events, <n>h effort
## What happened?
<finding id>: baseline <x> -> current <y>
## What did nothing
<finding id>: <n>h spent, shipped <date>, <baseline> unchanged
## What we cannot attribute
<finding id> moved inside a window containing an algo_update on <date>.
Control: non-matching pages moved <n>% over the same window, so this is
coincident, not established as causal.Done when
All five sections are present, section 4 is genuinely non-empty whenever any shipped item failed to move, and no sentence in the report asserts causation without showing its control.
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.

