Weekly status report
Pulls progress, blockers and numbers from each team's tools into one weekly update.
Jira
Google Sheets
Slack
Operations agent library
Each of these is a sub-agent of your Ops agent: built from the work your people already do, approved by its owner, and run under the vault's controls. Browse by workflow, or search for the job you have in mind.
01 · Workflow
The numbers everyone asks for, gathered from the systems that hold them.
Pulls progress, blockers and numbers from each team's tools into one weekly update.
Posts the handful of metrics leadership watches, with the change since last week and a line on why.
Watches for anything outside its normal range, such as a stuck queue or missed SLA, and tells the owner.
Compares each team's capacity with its workload from time tracking and project plans, and flags overloaded teams.
Writes up each operational incident: timeline, impact, cause and actions, from the incident channel.
Drafts the monthly operations review from the weekly reports, KPIs and incidents.
Answers "how many" and "how long" questions from the systems that hold the data, showing its working.
02 · Workflow
Knowing what you buy, from whom, on what terms, and when it renews.
Collects a new supplier's documents, insurance, security answers and bank details, and checks they're complete.
Puts supplier quotes side by side on price, terms and scope, and notes what's missing from each.
Drafts purchase orders from approved requests and routes them to the right budget holder.
Summarises a new or renewing contract: term, price, notice, auto-renewal, liability and anything unusual.
Lists contracts renewing in the next 90 days with notice periods, owners and spend.
Pulls delivery, SLA and spend data for key suppliers into a quarterly review note.
Groups spend by supplier and category and spots overlapping tools and chances to consolidate.
Keeps the vendor list current and flags changes worth knowing about, such as a new owner or a price change.
03 · Workflow
Writing down how things work, and keeping it true.
Writes up how a process runs today as steps with owners, tools and hand-offs, from interviews and existing docs.
Turns a recorded walkthrough or a thread into a step-by-step procedure in your template.
Answers questions about how things are done from your procedures, linking the one it used.
Records what changed in a process, when and why, from approved change requests.
Asks owners to confirm each procedure is still right on its review date, and flags the stale ones.
Writes a handover from a person's open tickets, docs and threads when they move role or go on leave.
04 · Workflow
Keeping projects moving without a person spending their week chasing updates.
Sets up the project space, timeline and RACI from the approved brief.
Asks each owner for their update in their own channel and writes up the replies.
Captures actions from meeting notes, assigns them and chases them before the next meeting.
Spots tasks and milestones slipping against the plan and tells the owner what depends on them.
Keeps the project risk log current from meeting notes and tickets, and flags risks with no owner.
Drafts the steering group update from status, risks, decisions needed and budget.
Drafts the closure report with outcomes, budget against plan and lessons learned.
05 · Workflow
The everyday asks that land on ops, sorted and moving within minutes.
Reads incoming IT requests, categorises them, answers the simple ones and routes the rest.
Collects an access request, checks it with the system owner and logs the approval.
Checks a requested tool against what you already pay for and the approved list before it goes to IT.
Keeps the laptop and equipment register current from orders, starters, leavers and returns.
Logs office and facilities requests and sends them to the right person or supplier.
Registers visitors, books desks and meeting rooms, and sends arrival details.
Collects travel requests, checks them against policy and prepares options for the person who books.
06 · Workflow
The evidence, registers and renewals that keep the business audit-ready, gathered as you go rather than in a panic.
Gathers evidence for ISO 27001 or SOC 2 controls from your systems and files it against each control.
Sends staff the policies they must read, tracks acknowledgements and chases the outstanding ones.
Asks risk owners to review their risks, updates the register and flags overdue actions.
Logs a subject access request, finds the person's records across your systems and tracks the one-month deadline.
Gathers headcount, revenue, claims and security answers for the insurance renewal questionnaire.
Tracks licences, certificates and registrations, and reminds owners before they expire.
No sub-agents match . Discovery finds the jobs your team actually does, so yours will likely include ones not listed here.
Examples of what discovery typically turns into. Your library is built from the work your own team does, so names, triggers and connectors will differ.
How a library agent becomes yours
01 · Discover
Read-only access to your tools' audit logs shows where AI is already doing operations work, and who is behind it. Nothing is installed on laptops.
02 · Interview
They talk or type through how the job runs today. The output is a written spec: trigger, steps, tools, data and owner.
03 · Vault
The sub-agent is test-run on real data, its owner approves it, and it joins the Ops agent under the vault's controls.
People ask the parent agent where they already work, in Slack, Teams, Claude or ChatGPT: @Ops agent send me this week's exceptions before the leadership call
Controls
Every sub-agent runs in the agent vault, with an activity log of every run, versions that need approval, and run history kept for 30 days.
FAQ
No. These are examples of what discovery typically finds in operations. Your library is built from the work your own team already does, through short interviews with the people who do it.
Each sub-agent has named owners, people who can change it and people who can use it. Owners approve new versions before they run.
If a connector disconnects or a run fails, the agent is marked down and its owners are asked in Slack to fix it. The last approved version keeps its history.
Keep reading
Book a demo
Read-only access, nothing to install, first findings in days.