Agent Role
Operations Manager
The machine that keeps the machine running.
What they own
Status tracking, team coordination, reporting, and process management. Your ops agent handles the recurring machinery — standups, invoices, status reports, anomaly detection — so your week starts at decision-making, not status-checking.
Most operations work is coordination, not judgment — pulling status, sending reports, following up on open items, flagging what changed. That work has to happen, but it doesn't have to be you doing it. Your agent keeps the rhythm. You step in for the decisions.
What changes for you
3:00 AM
Error spike in production logs.
Anomaly detected. Root cause identified. Alert sent to your phone with context and a suggested fix.
You fixed it before users noticed.
8:00 AM
Daily standup compiles automatically.
Status pulled from Linear, GitHub, and Slack. Two blockers surfaced. One item needs your decision. Summary delivered before the morning call.
The meeting took five minutes instead of thirty.
End of month
"Generate invoices for this month's active clients."
Invoices generated from tracked hours and agreed rates. Sent to clients with payment links. Follow-up reminders scheduled for overdue accounts.
Cash flow management on autopilot.
What they can do
How to bring them on board
Provision your vessel
Operational data on dedicated infrastructure. Secure by default.
Set your LLM provider key
Add your Anthropic, OpenAI, or Google API key. This is what powers the agent — without it, nothing runs. Takes 30 seconds in the Studio.
Connect your project tools
GitHub, Linear, Slack, Notion — the tools your team already uses.
Define your operational rhythm
Daily standups, weekly reports, monthly invoices. Set the cadence, the agent keeps it.
Run your first standup
Let the agent compile today's status. Review it. Adjust the format. Tomorrow's will be better.
Skills to install
These ClawHub skills unlock the capabilities above. Scan each before installing — the trust scanner catches known malicious skills.
GitHub
Pull PR/issue status for standups, surface blockers
clawhub install githubScan before installing →Linear
Project tracking, blocker detection, sprint status
clawhub install linearScan before installing →Slack
Team coordination, status delivery, escalation
clawhub install slackScan before installing →Web Search
Research vendors, look up solutions for flagged issues
clawhub install web-searchScan before installing →Notion
Document runbooks, recurring checklists, meeting notes
clawhub install notionScan before installing →Common questions
Which project tools does it integrate with for standups?
GitHub (PR and issue status), Linear (sprint tracking, blockers), Slack (team coordination and delivery), and Notion (runbooks and recurring checklists) — via installable skills.
Does it send reports and standups automatically?
Yes. You define the cadence — daily, weekly, or monthly — and the agent compiles and sends on schedule. You only intervene when something needs a decision.
Can it detect production incidents and alert me?
Yes. It monitors error logs and anomaly patterns, then alerts your phone with context and a suggested fix — typically before users notice the issue.
How does invoice generation work?
The agent generates invoices from tracked hours and agreed client rates, sends them with payment links, and schedules follow-up reminders for overdue accounts. You review before anything goes out.
Your agent coordinates. You make the calls.
Standups, reports, and alerts your agent surfaces are inputs for your decisions — not autonomous actions. When a blocker needs resolution or a conflict needs judgment, your agent escalates to you. Operational continuity runs automatically. Strategic decisions stay yours.
