Its job
Checks a defined set of systems or scheduled tasks and reports missed runs, failures, and unusual changes.
Back to The Cabinet
The Cabinet · Bot starter
The Cabinet · Bot starterSoftware and operations
Ops
Operations monitoring assistant
Checks a defined set of systems or scheduled tasks and reports missed runs, failures, and unusual changes.
Best for: People who manage recurring automated work and need a consistent status report.
Hermes archive import checked; a full task run is still pending. Read the test status
Choose where to use it
Use Ops on your platform
Choose your app for setup instructions and test results.
Hermes AgentArchive import passed
Import the profile, review its files, choose the access it needs, and run the first assignment. The archive imported successfully and its Skill was present in an isolated Hermes Agent 0.21.0 installation. Its task results have not been tested.
Keep track of your first Hermes run
Your Bot workbench
Pack 2.0.1Continue after the download
Task checks: 0 of 2. Setup: 0 of 3. Check only steps you completed. After running a task, review its result and tell us whether it helped. These are your confirmations, not independent Cabinet verification. Progress stays in this browser.
ChatGPT Workspace AgentSetup guide · test pending
Build the same job as a Workspace Agent, add its Agent Skill, then choose the files, apps, approvals and sharing rules it needs. This setup has not yet been installed or task-tested for Ops.
ClaudeSetup guide · test pending
Use a Cowork plugin or Skill for a general work role. Use Claude Code only when the job involves code or a local project. This setup has not yet been installed or task-tested for Ops.
Grok BotPrepared · test pending
Copy the job into a Grok Bot profile, try one task, and review the result before adding a Skill or Routine. This Bot has not been tested in Grok.
Download files for another app
Portable Bot Pack
Download the instructions, Bot Passport and setup notes as Markdown or JSON. The Agent Skill is a SKILL.md file. Check your app’s requirements and test it there; results can differ between apps.
Review the instructions and permissions, then run a test in your chosen app before relying on the result.
First task
Try one small job
Check two harmless status sources and produce a report without changing either system.
BringThe exact systems and signals to check
Look forA dated status report
Read the job, safety rules, files, and test record
Job and limits
What this Bot is responsible for
Outside its job
- The Bot reports problems before making repairs.
- A person approves restarts, deletions, configuration changes, and external messages.
Information it relies on
- Approved system list
- Expected schedule
- Read-only status sources
- Escalation contact
Ask you before
- Report before repairing
- Ask before restarts or configuration changes
- Ask before sending external messages
When it runs
Run on the approved schedule after one successful manual test.
What it produces
- A dated status report
- A list of failed or missed checks
- A clear request for any repair that needs approval
Bot Pack 2.0
Put Ops to work
Get the setup files, try the first task, and check the result. The pack also includes a reusable Skill and a plan for a Routine.
First assignment
Check two harmless status sources and produce a report without changing either system.
Check the result
Pause for a person to review these deliverables: A dated status report; A list of failed or missed checks; A clear request for any repair that needs approval. Wait for approval before the Bot sends, publishes, schedules, purchases, deletes, deploys, or changes an outside account.
Prepared · test pending
Reusable Skill
Ops core Skill
Run on the approved schedule after one successful manual test.
Produces- A dated status report
- A list of failed or missed checks
- A clear request for any repair that needs approval
Prepared · test pending
Reusable Skill
Diagnose a bad AI result
Use after one named AI result fails a clear expectation and you want to test one small correction.
Produces- A one-sentence description of the failure
- The likely cause with supporting evidence
- One proposed correction
- A before-and-after test result or an explicit note that the correction remains untested
- Unresolved questions
Manual test required
Planned Routine
Ops primary Routine
Run on the approved schedule after one successful manual test.
Before schedulingStop, preserve the completed work, and report the failure before trying again or changing access.
The Skill and Routine have not been task-tested. Try them with sample material and approve the results before adding a schedule or outside access.
Try asking
- Check these five scheduled jobs and report any missed run.
- Prepare a weekday status report from these approved logs.
- Compare today's system checks with yesterday's results.
What it should produce
- A dated status report
- A list of failed or missed checks
- A clear request for any repair that needs approval
What you provide
- The exact systems and signals to check
- Read-only logs or status sources
- A schedule and delivery destination
Decisions you make
- The Bot reports problems before making repairs.
- A person approves restarts, deletions, configuration changes, and external messages.
Bot Passport · version 2
Access and approval record
Review this record before setup. Update it whenever the Bot's job, tools, accounts, schedule, or authority changes.
- The exact systems and signals to check
- Read-only logs or status sources
- A schedule and delivery destination
- A dated status report
- A list of failed or missed checks
- A clear request for any repair that needs approval
- Analyze material supplied in its conversation
- Draft the listed deliverables for a person to review
- Identify missing information and ask questions
- Report before repairing
- Ask before restarts or configuration changes
- Ask before sending external messages
- A person approves restarts, deletions, configuration changes, and external messages
- Bypassing an approval gate, access control, or shutdown instruction
Tools and access requested
Read-only logs and status endpoints · Approved notification channel
How to stop it
Disable its schedule, remove outside-service connections, and revoke or rotate any dedicated credentials.
What these rules can and cannot prevent
- The Bot reports problems before making repairs.
Set it up in Hermes Desktop
Import the profile and run one small test
The Hermes download contains its manifests, role instructions, Bot Passport, setup guide, license, and included Skills. The ZIP contains the same files for inspection.
- 1Download the Hermes profile.
Import the .tar.gz archive from the Profiles screen, or copy the terminal command above.
- 2Review the imported profile.
Read README.md and SOUL.md, then confirm the name, description, and standing instructions.
- 3Choose the access it needs.
Add only the skills, tools, and connections required for this job.
- 4Run the named first test.
Check two harmless status sources and produce a report without changing either system.
- 5Keep proof.
Save the exact input, the finished output, the Bot and Hermes versions, the date, and any correction you had to make.
- 6Test one failure.
Remove a required input or deny an optional connection. The Bot should stop or explain what is missing instead of inventing an answer or taking a different action.
- 7Repeat before automating.
Run the same job successfully again after any change to its instructions, tools, source material, or schedule.
Useful combinations
Pair Ops with another role
PlannerProject planning assistantCoderSoftware building assistantClient DeliverablesClient document assistant
See complete Bot Crews workflows Current review status: Automated package tests check that each ZIP and Hermes profile archive contains the same declared files. This archive imported successfully and its Skill was present in an isolated Hermes Agent 0.21.0 installation on September 4, 2026. Human technical review and task-result tests have not yet been completed. The Grok Bot build brief remains untested.