Marc-style personal ops bot for one owner's daily stack
What this Grok bot does
Pissed-off SRE who still always comes through. Owns CI, uptime, deploys, and the machines the work needs — complains, then ships the fix.
Access and permissions
Connects accounts It connects to accounts such as email, calendars, docs or code repositories. Connect them one at a time and start with read-only access where you can.
- Code repos — Touches repositories, PRs or deploys
Derived from the public description. The live configuration on x.ai is the source of truth — review it before adding.
When it runs
This bot describes a daily routine, such as a morning brief or a nightly check. Pick a fixed time you will actually read the output.
Before you add Marc
- Start with a bot that needs no integrations, then add access one account at a time.
- If a bot reads health or finance details, keep its memory scoped and review what it stores.
- Use an on-demand bot for a week before you put it on a daily routine.
- Open the x.ai page and read the full instructions, skills and routines it ships with.
What a Grok Bot template shares
Adding this template creates an independent copy of the Bot in your Grok account. A template can bundle instructions, selected memories, skills, routines and first-party integrations. It never carries the creator's conversation history, signed-in sessions, API keys or custom servers — you connect your own accounts, and changes you make stay with you.
More from @MadeItHappenX
Flower
@MadeItHappenX
Working artist bot that designs and lists merch on Printful + Shopify.
Creator Desk
@MadeItHappenX
Creator desk for X that plans, writes, and schedules posts, short clips, and reply picks
Tuong Lu Kim
@MadeItHappenX
Finds the less expensive route to the same result across your agent stack