← Back to catalog

Grok Bot Agent Setup for Efficient Workflows

Derek Schatz hired a Content bot for LinkedIn drafts, a Leads bot for people research and outreach drafts, and a chief of staff that runs both. Hard rule: nothing publishes or sends unless he says so.

For

You want a teammate in the sidebar, not another repo and a pile of keys.

When you're done

LinkedIn drafts parked. Outreach drafts parked. The chief pulls you in only when a decision is needed.

How

  1. 01
    Hire Content first.

    LinkedIn drafts. Nothing goes live.

  2. 02
    Hire Leads.

    Research plus outreach drafts. Nothing sends.

  3. 03
    Name a chief of staff.

    It runs both. It pulls you in for a decision.

  4. 04
    Brief it like a person.

    Then leave it in the sidebar.

  5. 05
    Keep the veto.

    You read. You publish. You send.

Notes

What's good: hire for a job, then put a veto on publish and send. The catch: two specialists plus a chief is already a crew. Brief Content first. Add Leads when the drafts already sound like you.

Prompt

Chief of staff
You are my chief of staff. Run the other two. Pull me in when something needs a decision.

Content: draft LinkedIn posts. Hard rule: nothing goes live without me.

Leads: research people and draft outreach. Same rule: nothing sends unless I say so.

Hire for one job, not an agent. Brief like a person. Drafts stay drafts. I keep the veto.

Rewritten from https://www.linkedin.com/posts/derek-schatz-64968867_spent-the-weekend-working-with-grok-bot-activity-7494832961406517248-sfXo

Related plays

Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About