Writing

Agents · Governance

How I actually get work done with Grok Bot

Agents · Governance — narrow bots, human approval, and the morning loop I run as an operator-CEO.

I run Grok Bot the same way I advise clients to run AI: narrow roles, explicit sources, human approval before anything external.

This is not a product review. It is how I use agents on the job without handing over judgement, money, or publish rights.

One bot, one job

I do not build a “do everything” hero agent. I name bots for outcomes:

  • Morning briefing — scan approved sources, summarize what leadership needs to know
  • Drafting — turn research into paste-ready copy I still edit
  • Research — pull from defined sources only; no wandering the open web unsupervised

Each bot gets four things written down: goal, permitted sources, expected output, and forbidden actions without my sign-off (send email, post, purchase, edit production systems).

Skills and routines, not one-off prompts

When a workflow works twice, I ask the bot to save it as a skill. When it works five times, I schedule it as a routine — morning digest, weekly prep, recurring scans.

The difference from ad-hoc chat: the routine belongs to a bot with a role. My “chief of staff” bot is not running random prompts. It knows what it owns and how we format results.

Governance I actually enforce

  • Read-only first — new bots start with research and drafts only
  • Approval gates — external actions wait for me
  • Approved provider list — at CIT we maintain sanctioned AI tools; personal experiments stay in sandboxes
  • No credential sharing — bots do not get passwords or 2FA codes

Shadow AI is not “someone used ChatGPT.” It is ungoverned automation with your brand on the line.

What this looks like in a week

Monday and Wednesday: news scan, short brief, no auto-post. Thursday: draft pack for review. Friday: I edit and publish myself — or decline.

The bot files and drafts. I keep judgement. That is the deal.

If you are experimenting with Grok Bot or any agent platform, start there: one narrow job, one approval step, one week of manual runs before you automate. Speed without governance is just risk with better formatting.

← All notes