put-it-on-autopilot
Skill0 starsChanged 4 months agoMITView on GitHub
Generate GitHub Actions workflows for the recommended cadence, calling `rainmaker routine` and `rainmaker report`, and print the exact secrets the user needs to set before the workflow can run.
- Reads credentials
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
- 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
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
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
Never assume the cadence; present the recommendation and let the user confirm or override before writing any workflow.
- Very specific: line 59
Verify every secret the workflow needs is documented in the README's credentials section, and print the exact gh secret set commands.
- Distinctive: line 66
Never re-check anything faster than its own verification window.
- Distinctive: line 67
Never schedule a workflow whose secrets are undocumented.
- Distinctive: line 68
Never activate a paid provider because its secret exists.
- Very specific: line 69
Never emit if: ${{ secrets.NAME != '' }}.
≈ “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
put-it-on-autopilot
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 |
rainmaker.config.yml | site shape (URL count, publish rate), to recommend a cadence | required |
.env.example | which secrets the workflow will need | present in every install |
Produces
.github/workflows/weekly.yml, .github/workflows/monthly.yml.
Procedure
- Determine site shape from the latest crawl and GSC snapshot: URL count, clicks per month, and recent publish rate.
- Recommend a cadence from
spec/agent.mdsection 5:- Under 50 URLs or under 100 clicks/month: no weekly job, monthly audit and report, quarterly strategy review only if drift fires.
- 50 to 500 URLs: weekly pulse (
fetchplusaudit --refresh), monthly full audit, report, off-site scan, AI probes. - Over 500 URLs or publishing 4+ pages a month: full
routineweekly, monthly report and off-site scan,ledger --compact.
- Never assume the cadence; present the recommendation and let the user confirm or override before writing any workflow.
- Generate the workflow calling
rainmaker routine(weekly) andrainmaker report --window monthplusrainmaker ledger --compact(monthly). - Verify every secret the workflow needs is documented in the README's credentials section, and print the exact
gh secret setcommands. Never write a workflow depending on a secret the user has not been told to create. - AI citation probes are scheduled monthly, never weekly: they cost money per run and the answers are non-deterministic, so a weekly line would mostly measure sampling variance.
- Built-in crawl is the workflow default. Include
--provider firecrawlor--provider contextdevonly after the user explicitly approves that provider and its quota or cost. - GitHub Actions does not allow
secrets.*directly in a stepif:. Map an optional secret into job-levelenv, then testenv.NAME != ''in the condition.
Decision rules
- Never re-check anything faster than its own verification window. A weekly ranking report on a 40-page site reports noise as news.
- Never schedule a workflow whose secrets are undocumented.
- Never activate a paid provider because its secret exists.
- Never emit
if: ${{ secrets.NAME != '' }}. Use a job-level environment variable andif: env.NAME != ''. - The cadence is a recommendation the user confirms, never a default silently applied.
Output
## Recommended cadence
Site shape: <n> URLs, <n> clicks/month, publishing <n> pages/month
Recommendation: <weekly / monthly-only / full weekly>, because <reason>
Confirm, or tell me what to change.
## Workflows written
.github/workflows/weekly.yml
.github/workflows/monthly.yml
## Secrets still needed
gh secret set FIRECRAWL_API_KEY --repo <repo>
gh secret set GOOGLE_APPLICATION_CREDENTIALS --repo <repo>Done when
The cadence was confirmed by the user before anything was written, both workflow files validate, and every required secret was printed with its exact gh secret set command.
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.

