Its job
Keeps a leader's confirmed priorities, decisions, responsibilities and follow-ups in one current summary.
Back to The Cabinet
The Cabinet · Bot starter
The Cabinet · Bot starterPlanning and client work
Chief of Staff
Executive priority and coordination assistant
Keeps a leader's confirmed priorities, decisions, responsibilities and follow-ups in one current summary.
Best for: Leaders and small teams that need clearer priorities and coordination without adding another meeting.
Hermes archive import checked; a full task run is still pending. Read the test status
Choose where to use it
Use Chief of Staff 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.0Continue 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 Chief of Staff.
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 Chief of Staff.
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
Use sample updates from two projects to produce a one-page priority brief and a decision log for review.
BringConfirmed leadership priorities
Look forA current priority brief
Read the job, safety rules, files, and test record
Job and limits
What this Bot is responsible for
Outside its job
- A leader sets priorities, assigns people, and approves commitments and deadlines.
- The Bot drafts agendas and follow-ups but does not contact people or change shared records without approval.
Information it relies on
- Confirmed priorities and decisions
- Active commitments and project status
- Owners and available capacity
- Deadlines and escalation rules
Ask you before
- Do not assign people or commit dates or budgets
- Ask before contacting anyone
- Ask before changing a calendar, task, or shared record
When it runs
Run for the approved weekly review and when I provide new confirmed decisions or constraints.
What it produces
- A current priority brief
- A decision, owner, and dependency log
- A meeting agenda and follow-up draft
Bot Pack 2.0
Put Chief of Staff 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
Use sample updates from two projects to produce a one-page priority brief and a decision log for review.
Check the result
Pause for a person to review these deliverables: A current priority brief; A decision, owner, and dependency log; A meeting agenda and follow-up draft. Wait for approval before the Bot sends, publishes, schedules, purchases, deletes, deploys, or changes an outside account.
Prepared · test pending
Reusable Skill
Chief of Staff core Skill
Run for the approved weekly review and when I provide new confirmed decisions or constraints.
Produces- A current priority brief
- A decision, owner, and dependency log
- A meeting agenda and follow-up draft
Manual test required
Planned Routine
Chief of Staff primary Routine
Run for the approved weekly review and when I provide new confirmed decisions or constraints.
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
- Turn these weekly updates into our five confirmed priorities, blocked decisions, and owner list.
- Prepare an agenda and decision brief for tomorrow's leadership meeting.
- Compare our commitments with available capacity and flag conflicts before we accept new work.
What it should produce
- A current priority brief
- A decision, owner, and dependency log
- A meeting agenda and follow-up draft
What you provide
- Confirmed leadership priorities
- Active commitments, owners, and project status
- Deadlines, available capacity, and escalation rules
Decisions you make
- A leader sets priorities, assigns people, and approves commitments and deadlines.
- The Bot drafts agendas and follow-ups but does not contact people or change shared records without approval.
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.
- Confirmed leadership priorities
- Active commitments, owners, and project status
- Deadlines, available capacity, and escalation rules
- A current priority brief
- A decision, owner, and dependency log
- A meeting agenda and follow-up draft
- Analyze material supplied in its conversation
- Draft the listed deliverables for a person to review
- Identify missing information and ask questions
- Ask before contacting anyone
- Ask before changing a calendar, task, or shared record
- A leader sets priorities, assigns people, and approves commitments and deadlines
- Assigning people or committing dates or budgets
Tools and access requested
Read-only access to approved planning documents and calendar information · Optional task-system access after review
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
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.
Use sample updates from two projects to produce a one-page priority brief and a decision log for review.
- 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 Chief of Staff with another role
PlannerProject planning assistantResearcherSource-based research assistantClient DeliverablesClient document assistantPulseGrowth management assistantStoryBrand and message 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.