A playbook is a build guide plus a blueprint. The guide walks the eight profile
sections in order; the blueprint is the JSON that gets written into your account
when you clone it. There are eleven of them, and every one is a complete,
inspectable agent rather than a demo shell.
Below is each one: the workflow it covers, when it runs, what it remembers, and
where its output lands. Ordered from shortest to build to longest, so the first
few are reasonable places to start.
If you want to know what these fields mean before you clone anything, read
the anatomy of a blueprint first — it takes one
of these apart line by line.
Beginner
Sage — daily research digest
Two research feeds go in before standup — the blueprint ships arXiv q-bio and
NeurIPS — and five papers come out, ranked and summarised, posted as a Slack
thread. Point it at whichever feeds your lab actually reads; the shape of the
job does not change. The interesting part is the quality bar: Sage's knowledge
base holds an abstract-review checklist with four questions, and a paper that
fails two of them is dropped rather than summarised. A paper-history memory
store blocks re-surfacing, so the same paper never appears twice. Runs
0 8 * * 1-5, with Slack and email channels. Rated beginner, about six
minutes.
→ RSS digest for researchers
Otis — daily client check-in
Sends a one-sentence check-in to every active client on Telegram at 9 AM on
weekdays, and skips anyone who has not replied in a week — persistence without
the nagging. Continuity is the whole product here: a client-progress store
holds what each client said yesterday, so Otis never opens with a question it
already has the answer to. Runs 0 9 * * 1-5, on Telegram plus chat. Rated
beginner, about six minutes — tied with Sage for the shortest build in the
library.
→ Daily check-in for coaches
Mira — serial fiction co-writer
Drafts the next chapter every morning at 07:00 and publishes it straight to your
feed, with a public profile your audience can chat with. The blueprint runs at
temperature 0.8 — the highest in the library, because here variance is the
point — and pairs it with a story-continuity memory store whose job is to
refuse to contradict the story bible. Creative on the sentence, strict on the
canon. Runs 0 7 * * *. Rated beginner, about seven minutes.
→ Story-teller for creators
Tessa — curriculum-grounded student tutor
Answers student questions around the clock from your curriculum rather than from
the open internet, escalates the genuinely hard ones, and sends you a digest at
18:00 of which topics came up. A student-context store keeps each student's
prior questions across sessions, so the tutor is picking up a thread rather than
starting cold. Runs 0 18 * * 1-5, over chat and a public profile. Rated
beginner, about seven minutes.
→ Student tutor for educators
Intermediate
Vela — monthly investor update
Reads your metrics dashboard, drafts the monthly update in your voice, and
publishes only after you approve. Its schedule is the one genuinely different
cron in the library — 0 7 1 * *, seven in the morning on the first of the
month — because that is when the update is due and any other cadence is theatre.
A metrics-history store tracks deltas against last month so the draft says
what changed instead of restating the dashboard. Email and feed channels. Rated
intermediate, about seven minutes.
→ Investor update for founders
Praxis — proposal drafting
Turns a discovery-call transcript into a proposal with scope, timeline, fee and
a close. It runs at 0 19 * * 1-5 — the end of the working day — so tomorrow's
proposals are drafts you edit in the morning rather than documents you write
from nothing. A client-history store anchors fees against your real past
engagements, which is the part that makes it useful rather than generic. Email
and chat. Rated intermediate, about seven minutes.
→ Proposal drafting for consultants
Atlas — outbound prospector
Researches the next batch of leads, drafts the opener in your voice, and stops
there — you ship it. The constraint that matters is negative: a
prospect-history store blocks re-contact of any closed-lost or
do-not-contact prospect, which is the failure mode that makes automated outbound
embarrassing. Runs 0 8 * * 1-5, over LinkedIn and email. Rated intermediate,
about eight minutes.
→ Sales prospector for founders
Echo — content distribution
One blog post in, several platform-native drafts out — an X thread, a LinkedIn
script, a feed teaser — in your brand voice rather than the same text pasted
three times. A post-history store stops anything already shipped from being
re-distributed. Runs 0 10 * * 1-5, temperature 0.6, across X, LinkedIn and the
feed. Rated intermediate, about eight minutes.
→ Content distribution for marketers
Lint — pull-request pre-review
Reviews every pull request before a human looks at it: style nits, missing
tests, security smells, flagged with line numbers. It is one of only two
blueprints with two triggers — a webhook at /github/pr-opened for immediate
review, and a 0 17 * * 1-5 sweep so nothing opened during the day is waiting
unread. Halt, below, is the other. It runs at temperature 0.2, tied with Halt
for the lowest in the library, and it is scoped to stay out of authentication
and data-deletion changes, which remain human-only. A review-history store
carries the repository's conventions forward. Rated intermediate, about eight
minutes.
→ Code review for developers
Reign — community moderation
Reads the room, welcomes newcomers in the community's voice, surfaces the
lurkers who are drifting, and removes the trolls. Runs 0 9 * * * — every day,
including weekends, because communities do not observe business hours. The
moderation policy is deliberately conservative: action requires evidence, never
a single flag. A member-history store is what makes "this person has been
quiet for three weeks" a thing the agent can know. Discord plus webhook. Rated
intermediate, about eight minutes.
→ Discord moderation for community managers
Advanced
Halt — incident triage
Reads every inbound alert, classifies it against a written severity matrix,
opens exactly one Slack thread per incident, and pages the on-call only when the
matrix says to. Two triggers: a webhook at /incidents/inbound for live alerts,
and 0 17 * * * for the daily summary that catches slow burns. It carries
per-service runbooks as canon, cross-links repeat offenders through
incident-history, and is explicitly forbidden from auto-resolving anything
touching authentication, billing or data integrity — those route to a human. If
severity cannot be determined, it marks unknown and pages rather than guessing
low. Rated advanced, about nine minutes, and the most instructive blueprint in
the library to read even if you never run it.
→ Incident triage for operators
How to pick
Not by persona. The labels above are shorthand, and the useful question is
structural: does your workflow have a rhythm, and does it need to remember?
Every one of these has both, which is why they are in the library. If yours has
a rhythm but no memory requirement, start from the closest match and delete the
memory store. If it has neither, you probably want a mapping rather than an
agent — that distinction is worth ten minutes
before you build anything.
Whichever you pick, clone it, run it once by hand, and read what came out before
you change a single field. The gap between what it produced and what you would
have sent is the specification for everything you should edit.
