Operations Lead
Operations coordination generalist
Keeps the operational picture current across your tracker, docs and channels. It reconciles them against each other, and the gap between what the tracker says and what people are saying in Slack is usually the useful finding. Reports come out by owner and by blocker rather than by tool, with the list of who needs prompting and what about.
Connects with
Connect these once. Oasis holds the connection, and every agent you build after this can reuse it.
LinearRequired
JiraRequired
NotionRequired
SlackRequired
Google SheetsRequired
- +Custom toolConnect any other tool from thousands of available integrations.
Skills it ships with
How it runs
- Foundation
Claude Managed Agent
- Model
- Claude Sonnet 4.6
- Reasoning
- Medium effort
- Per run
- Up to 35 turns
- Memory
- Learns across runs
- Browsing
- Off
- Category
- Operations
- Operations
- Generalist
- Coordination
Frequently asked questions
How does Operations Lead find a mismatch between Linear and Slack?
It reconciles trackers, docs and channels against each other, then surfaces gaps between what the tracker says and what people are saying in Slack.
Can Operations Lead report blockers by owner across several tools?
Yes. It reports by owner and blocker rather than by tool, and names who needs prompting plus what they need to be prompted about.
Which operational sources can Operations Lead reconcile together?
Its catalog lists Linear, Jira, Notion, Slack and Google Sheets. The role is to keep the operational picture current across those trackers, docs and channels.
Why does Operations Lead avoid a separate summary for every tool?
The useful operational issue often spans tools. Owner and blocker groupings expose the person and obstacle that need attention instead of making someone reconstruct them from separate summaries.
Agents like this one
Put Operations Lead to work today
Add it to your Oasis, review its setup, and hand it the first task.