check-before-i-publish
Skill0 starsChanged 4 months agoMITView on GitHub
Run the 10 blocking preflight gates before a page ships, and the 8 postflight gates on their own verification windows after. Never overrides a failing gate; a fail always names the specific fix.
In this repository26 other files it gives its agents.
- beat-my-competitorsSkill
- brief-my-writerSkill
- can-i-actually-rankSkill
- 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-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, 2 are distinctive, and 4 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.
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 54
Never auto-override a failing gate: Every failure states the specific fix from the gate's own reason string.
- Distinctive: line 94
Every gate reports pass, fail, or not-yet-due with its due date, and every failure names its specific remedy.
≈ “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
check-before-i-publish
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 |
| the brief and draft | preflight input | ask for the slug |
data/ledger.jsonl | shipped timestamps, for postflight windows | run rainmaker ledger --rebuild |
data/snapshots/<latest>/* | current measured values for postflight gates | run rainmaker audit |
Produces
Nothing persisted; a pass/fail report.
Procedure
- Preflight, before anything ships. Call
src/gates/preflight.ts runPreflight(brief), which runs all 10 gates: pain point provenance, cluster slot, cannibalisation, intent match against the SERP verdict, 3+ internal link sources, schema planned, E-E-A-T signals, extractability, the slop check, and the revenue argument. Print the full pass/fail table, not just the failures; a reader needs to see what already passed to trust what didn't. - Never auto-override a failing gate. Every failure states the specific fix from the gate's own reason string.
- Postflight, on a schedule after shipping. Call
src/gates/postflight.ts postflightStatus(shippedAt, now, measured)per finding, which reportspass,fail,not_yet_due, orunmeasuredper gate against its own window (indexed 14 days, canonical and internal links immediate, CWV 7 days, impressions 28 days, position trend, AI citation and conversion contribution 90 days). - A
not_yet_duegate is not a failure; report it as pending with the date it becomes due.
Decision rules
- No gate is ever skipped or overridden. A user asking to publish anyway gets the fail table and is told this skill does not have an override; the decision to ship over a failing gate belongs to the human, not to a bypass built into the tool.
- Postflight never reports pass or fail before its window elapses. Judging a metric before it has had time to move manufactures both false confidence and false alarm.
Output
## Preflight: <slug>
pain_point_provenance PASS
cluster_slot PASS
cannibalisation FAIL: an existing URL already targets this intent: /old-page
intent_match PASS
internal_links FAIL: only 1 inbound link source identified, needs 3
schema_planned PASS
eeat_signals PASS
extractability PASS
slop_check PASS
revenue_argument PASS
2 of 10 gates failing. Not ready to publish.
## Postflight: <finding id>
indexed not_yet_due (due 2026-08-15)
canonical_correct PASS
cwv_not_regressed PASS
internal_links_live PASS
impressions_appearing not_yet_due (due 2026-08-29)
position_trend not_yet_due (due 2026-10-30)
ai_citation not_yet_due (due 2026-10-30)
conversion_contribution not_yet_due (due 2026-10-30)Done when
Every gate reports pass, fail, or not-yet-due with its due date, and every failure names its specific remedy.
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.

