Routine Templates
Production-grade prompt templates for Claude Code Routines. 5 recipes using Burn, GitHub, Slack MCP connectors — copy, paste, schedule.
Install
$ agentstack add mcp-fisher521-routine-templates ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/mcp-fisher521-routine-templates) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
routine-templates
Production-grade prompt templates for Claude Code Routines.
Copy · paste · schedule. Five recipes that use Burn, GitHub, Slack, and Email connectors to replace 10+ minutes of daily UI-clicking.
[](https://opensource.org/licenses/MIT) [](https://x.com/hawking520)
What this is
Claude Code Routines (released 2026-04-15) let Claude Code run on a schedule or trigger — cron, API call, GitHub event — even with your laptop closed.
Routines are cloud-only and have no file format — you paste a prompt into the web UI at claude.ai/code/routines. Which means good Routines die in private Notion pages instead of being shared.
This repo collects five Routine prompts that do actual work, not demo work. Each is tested, has setup checklists, and calls concrete MCP connectors.
Templates
| # | Template | Time savings | Primary connector | |---|---|---|---| | 1 | [Daily reading triage](templates/01-daily-reading-triage.md) | 15 min/day | Burn · Raindrop · Readwise | | 2 | [Weekly vault harvest](templates/02-weekly-vault-harvest.md) | 20 min/week | Burn | | 3 | [Morning flame brief](templates/03-morning-flame-brief.md) | 5 min/day | Burn | | 4 | [GitHub PR triage](templates/04-github-pr-triage.md) | 10 min/day | GitHub | | 5 | [End-of-focus-block handoff](templates/05-focus-block-handoff.md) | 10 min/day | Burn + Slack/Email |
How to use
- Open claude.ai/code/routines
- Click New Routine
- Copy a template's "Prompt" block, paste into the prompt field
- Edit `` (your priorities, org, username, etc.)
- Link the required MCP connectors at Settings → Connectors
- Set schedule per template
- Pick a delivery channel
That's it. Your routine runs on Anthropic's infrastructure — nothing to self-host.
Design principles (what separates these from a Gist dump)
- Structural prompts, not paragraphs — every template has explicit
Step 1/2/3/…so Claude doesn't improvise - No content invention — "Never invent items that aren't in the backlog" appears in every template
- Hard rules section — what the routine won't do (no auto-delete, no auto-merge, no discovery)
- Realistic time budgets — if a routine takes longer, it's over-scoped
- Edit markers — `` calls out what you must change before first run
Required MCP connectors
Most templates expect at least one of:
- Burn —
https://burn-mcp-server.vercel.app/api/mcp(Bearer token from burn451.cloud) - GitHub — official connector, OAuth in claude.ai Settings
- Slack / Email — for delivery
Add connectors globally (Settings → Connectors); Routines auto-see them.
Why Burn is the flagship example
Most template have Burn as the reading-intake connector because Burn was built for exactly this shape — MCP-native, 24h-countdown reading queue, 26 tools for search/triage/organize.
But every template is connector-swappable. If you use Raindrop / Readwise / Karakeep / Pocket export, adapt Step 1's data-fetch call.
Contributing
PRs welcome. To add a template:
- File under
templates/NN-kebab-case-name.md - Follow the existing structure (Schedule / Connectors / Delivery / Prompt / Rules / Setup / Why)
- Keep it prompt-first — no walls of prose, no pitches
- Test it in your own routine for at least 3 days before submitting
Also welcome:
- Connector adapter snippets (Raindrop, Readwise, Karakeep variants)
- Delivery format variants (mobile-first, rich HTML, terminal-friendly)
- Translations (CN / JP / KR — claude.ai web UI is EN-first but Routines run the prompt in any language)
Related
- CLI ranker: reading-routine
- Save-to-queue CLI: save-to-burn
- MCP backend: burn-mcp-server
- Daily journal: morning-brief
About
Built by @hawking520 — exploring AI-era content & attention workflows in public.
Each template was extracted from a real routine running in my own Claude Code. If you build a better one, send a PR.
Pairs naturally with Burn — the 24h-countdown reading queue that forces you to absorb, not hoard.
License
MIT — see [LICENSE](LICENSE)
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Fisher521
- Source: Fisher521/routine-templates
- License: MIT
- Homepage: https://burn451.cloud?ref=routine-templates
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.