show-me-progress
Skill0 starsChanged 4 months agoMITView on GitHub
Render the mandatory five-section report for a chosen window, refusing any window longer than available snapshot history rather than extrapolating a partial period into a full one.
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-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
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Run rainmaker context --check first.
- Very specific: line 29
Only the data/ files listed in this skill's Consumes table.
- Very specific: line 31
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
- Very specific: line 37
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.
- Distinctive: line 57
If it refuses, relay the refusal exactly, including the availability date.
- Distinctive: line 62
Never render a report for a window longer than the tool allows.
- Distinctive: line 72
All five sections are present, every number carries provenance, and the window is fully covered by real snapshot history rather than any …
≈ “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
show-me-progress
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 and current status per finding | run rainmaker audit |
data/snapshots/ history | the earliest snapshot date, for the cold-start refusal | run rainmaker audit |
Produces
reports/<window>-<date>.md, via rainmaker report --window <window>.
Refuses when
The requested window exceeds available snapshot history. This is enforced in code by src/report/windows.ts checkWindowAvailability, not by judgment: a full window compared against a partial one is not a comparison, and the refusal names the exact date the window becomes honest.
Procedure
- Run
rainmaker report --window <pulse|28d|month|quarter|half-year|strategy>. - If it refuses, relay the refusal exactly, including the availability date. Do not attempt to render a smaller, unrequested version of the report as a consolation; offer the smaller window explicitly and let the user choose.
- Present all five sections in order: what changed (numbers only, no adjectives), why it matters (framed in tiers, never "rankings improved" without the tier and the conversion consequence), what to do (ranked by revenue score), what we are watching (leading indicators with numeric thresholds and due dates), and confidence (which capabilities were live).
Decision rules
- Never render a report for a window longer than the tool allows. There is no manual override.
- Section 1 is numbers only, maximum 5 lines.
- Section 5 is never omitted, even when every capability was live; say so explicitly rather than leaving the section blank.
Output
The five-section spine, verbatim from rainmaker report's output, with no additional commentary layered on top that the tool did not itself produce.
Done when
All five sections are present, every number carries provenance, and the window is fully covered by real snapshot history rather than any part of it being extrapolated.
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.

