All use cases
Use case · Ops
Ops & internal tools
Morning briefs, weekly reports, scheduled cleanups. Give an agent the tools and a cron, then forget about it.
Ops & internal tools
0:24 / 1:12
Preview
What this category covers
Anything that runs on a schedule and produces a document, a notification, or a small action. Ops work tends to be repetitive, low-stakes per run, and high-value in aggregate — exactly what routines are built for.
Routines that pay rent
- Morning briefing — daily 07:30. Pull calendar, tickets, overnight mail, write
today.md. - Weekly retro — Fridays 16:30. Group the week’s notes into wins / unsolved / next-week, append to
retros/{date}.md. - Inbox sweep — every 30 minutes. Triage new messages and draft replies; never auto-send.
- Stale-ticket digest — daily 17:00. Pull tickets with no activity for 7+ days and post a list to Slack.
Skills that pair well
- `github` for PR/issue housekeeping.
- `slack` for posting summaries where the team reads.
- `linear`-flavored prompts via the
githuband browser skills if you don’t have a dedicated one yet.
Heartbeat fits here too
Proactive ops. Enable heartbeat on the assistant that owns these routines. Between scheduled runs, it can check in on its own and surface anything urgent — only when it’s actually worth surfacing.