agentleFS
vcxcviivcxcvii/rainmaker/skills/show-me-progress/SKILL.md

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.

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
  1. Very specific:

    Run rainmaker context --check first.

    line 21
  2. Very specific:

    Only the data/ files listed in this skill's Consumes table.

    line 29
  3. Very specific:

    If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:

    line 31
  4. Very specific:

    If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.

    line 37
  5. Distinctive:

    If it refuses, relay the refusal exactly, including the availability date.

    line 57
  6. Distinctive:

    Never render a report for a window longer than the tool allows.

    line 62
  7. Distinctive:

    All five sections are present, every number carries provenance, and the window is fully covered by real snapshot history rather than any …

    line 72

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. context/business.md in full. If absent, stop: "No business context. Run rainmaker audit, then the know-my-buyer skill."
  2. context/voice.md if this skill writes prose. If absent, stop and say so.
  3. context/glossary.md if this skill names products, features or competitors.
  4. data/strategy.json if this skill reads or writes strategy.
  5. 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

FileWhyIf missing
data/ledger.jsonl, data/state.jsonevents and current status per findingrun rainmaker audit
data/snapshots/ historythe earliest snapshot date, for the cold-start refusalrun 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

  1. Run rainmaker report --window <pulse|28d|month|quarter|half-year|strategy>.
  2. 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.
  3. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.