Put Claude on autopilot without it breaking things.
32 production-ready routines and a 14-pattern reliability kit. Every routine verifies its own work before it reports, fails loudly instead of silently, and never sends, deletes or spends without your approval.
Get the Runbook — A$97 launch priceInstant download · ZIP + 40-page PDF guide · 14-day refund policy · Card, Apple Pay, Google Pay or PayPal · A$149 after launch week
The problem, in Anthropic’s own words
Claude can now run on a schedule while your laptop is closed. It also runs unattended, and the run list shows green whenever the session exits cleanly, whether or not the task actually happened.
“A green status in the run list means the session started and exited without an infrastructure error. It does not mean the task in your prompt succeeded.”Claude Code documentation, Routines
Unattended plus unverified is how automations go wrong quietly: connector calls that die with “requires approval” mid-run, tasks that fire hours late after a laptop wakes, reports that carry a confident number nobody actually read. The Runbook exists to close that gap.
What you get
1. The Routine Library
32 routines across 8 job families. Each is a complete, self-contained spec: what it does, what it needs, the exact prompt, a Desktop SKILL.md, a realistic sample output, a first-run checklist, a failure-modes table and variations. Every one works from a file drop, so you can start before you have a single connector set up.
2. The Reliability Kit
Self-contained prompts. Never fabricate. Verify before you report. One write per run. Kept-prior-value with honest stamps. Least-privilege connectors. Untrusted content stays data. Fail loudly on permissions, quotas and logins. Time-aware for late catch-up runs. Drafts-only outbound. Escalation protocol. Run log and weekly self-audit. Cost and cap awareness. Secrets hygiene.
3. Routines that watch your routines
An Ops Board rebuilt daily from your run logs with “not refreshed” markers; a Weekly Reliability Review that catches routines that never ran and errors that repeat; a Backup and Integrity Check; an Access and Secrets Review.
4. Setup, memory and templates
Cloud routine vs Desktop task vs /loop, chosen per routine. The folder and repository layout that gives cloud routines memory between runs. 20 starter templates. A 7-day rollout order. A 40-page PDF guide.
| Job family | Routines |
|---|---|
| Inbox and follow-through | Daily Follow-up Catcher · Weekly Promises Audit · Morning Brief · Receipts and Renewals Sweep |
| Sales and customers | Stale Deal Nudger · Inbound Lead Triage · Weekly Customer Feedback Digest · Renewal and Churn Watch |
| Content and marketing | Weekly Newsletter Draft · Article-to-Social Batch · Content Performance Digest · Repurposing Pipeline |
| Web, SEO and analytics | Weekly Traffic and Search Digest · Broken-Link and 404 Sweep · New-URL Indexing Prep · Competitor Page-Change Monitor |
| Finance and admin prep (non-advice) | Receipts-to-Ledger Prep · Overdue Invoice Reminder Drafts · Month-End Close Prep · Subscription and Spend Audit |
| Product and code | Nightly Dependency and Vulnerability Triage · PR Review Checklist · Deploy Verification · Docs Drift Weekly |
| Operations and reliability | Ops Board Refresh · Weekly Reliability Review · Backup and Integrity Check · Access and Secrets Review |
| Personal ops | Weekly Review and Plan · Learning Digest · Goals and Habits Tracker · Appointments and Travel Prep |
Read the sample runs before you buy
Six real executions of four routines are in the download, saved exactly as produced. A Weekly Reliability Review that catches an enabled routine that never ran and a connector error that repeated. A Morning Brief that reports a missing input honestly instead of inventing one. A page-change monitor with two live fetch rounds. Three of the six finish PARTIAL, on purpose, so you can see what a caught failure looks like.
Who it is for
Solo operators, freelancers, indie hackers and small teams on Claude Pro, Max or Team who want recurring work handled by Claude and want to be able to trust the result. You do not need to be a developer. Cloud routines need a GitHub repository (the guide walks you through it); Desktop tasks need only a folder.
Who it is not for
Anyone who wants Claude to send emails, post publicly, delete files or move money unattended. Version 1 does none of that by design.
How it works
- Download and unzip. Read
README.md(10 minutes). - Copy the templates into a working folder (Desktop) or a new repository (Cloud).
- Pick your first routine (the guide suggests the Morning Brief), paste its
SKILL.md, click Run now, approve tools once. - Read the transcript and the run log. Add one routine a day for a week using the rollout order.
- Let the Weekly Reliability Review tell you what to fix.
Pricing
ZIP + 40-page PDF. All 32 routines in both forms, the Reliability Kit, 20 templates, the Ops Board, 6 sample runs. Free updates to every v1.x release.
Get the RunbookDigital product, delivered instantly; all sales are final. Not sure? Take the free starter first. Prices include GST where applicable.
Not ready to buy?
The free starter has 5 complete routines (Morning Brief, Weekly Review, Traffic and Search Digest, Weekly Reliability Review, Docs Drift) in both forms, the guardrail checklist and four templates.
Get the free starterQuestions
Do I need Claude Code?
Desktop scheduled tasks run in the Claude Desktop app. Cloud Routines are part of Claude Code and are available on Pro, Max, Team and Enterprise plans. The guide covers both; every routine ships in both forms.
Does it work with Cowork?
Yes. Cowork’s scheduled tasks are the Desktop form; the SKILL.md files drop straight in.
Will these routines email my clients or post for me?
No. Every routine writes drafts and lists for you to approve. That is a design decision, not a limitation to be removed later.
Do I need connectors?
No. Every routine has a file-based fallback. Connectors make some routines richer; the guide shows how to add them with least privilege.
Can I change the routines?
Yes. They are plain text. The licence allows adapting them for your own use and your team’s; it does not allow reselling or redistributing the files.
Is this affiliated with Anthropic?
No. Claude and Anthropic are trademarks of Anthropic, used descriptively. The Runbook is an independent product built on Anthropic’s public documentation.
Refunds?
The Runbook is a digital download delivered in full at purchase, so all sales are final and no refunds are given for change of mind. Faulty or missing files are replaced. Try the free starter before you buy if you are unsure. Full refund policy.