Independent guide to useful Bots · Across platforms
Bot Cabinet
Back to Chief of Staff
Grok Bot · guided setup

Build Chief of Staff in Grok Bot

Give it one clear job, try one small task, and judge the result before you add tools or a schedule.

Not yet tested in Grok Bot
  1. 1

    Open Grok Bot

    You need access to Grok Bot. In the app, choose New → Create new Bot, then open Edit Profile. Bot Cabinet cannot install this Bot in your account for you.

    Open Grok Bot
  2. 2

    Add the instructions

    Set its name to Chief of Staff. Copy this into its description, review the limits, and save the profile. You can refine it after the first result.

    You are Chief of Staff, an executive priority and coordination assistant. Use only confirmed priorities, decisions, commitments, owners, and dates. Keep ideas, options, planned work, and assigned work clearly separate. Surface conflicts, missing owners, blocked decisions, and capacity limits. Never turn an idea into an assignment or promise. Ask before contacting anyone, changing a shared record, assigning work, or committing a date or budget.

    Keep private data, passwords, and account access out of the description. Official profile instructions

  3. 3

    Try one task

    Provide the input it needs, then paste this message into Chief of Staff. For the first run, use sample or public material whenever possible.

    • Confirmed leadership priorities
    • Active commitments, owners, and project status
    • Deadlines, available capacity, and escalation rules
    Use sample updates from two projects to produce a one-page priority brief and a decision log for review.

Use only the material I give you or sources I approve. If required input is missing, ask me before starting. Return a current priority brief, a decision, owner, and dependency log, a meeting agenda and follow-up draft. Stop after the result and let me review it. Do not create a Skill or Routine, connect an account, send a message, publish, or change a live system.
  4. 4

    Decide if it helped

    Check whether you got a useful result, whether claims can be checked, and whether it stayed within the job you gave it. 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. If it misses, correct the job or supply the missing input and try again.

    Only after repeated manual runs work should you consider a Skill, Routine, or outside connection. Review access and approvals first.