Matt Palmer's eight Grok Bot templates

Matt Palmer wrote up eight Grok Bot templates after shareable bots shipped. They are bots he uses, packaged so someone else can start from the same work without inheriting his files or logins.

A template is a public copy of a bot's identity, skills, and routines. You get the recipe. You still connect your own X, GitHub, Notion, Cursor, Cloudflare, or Bland accounts, and you still approve anything that posts, buys, or calls.

Each template is built for a narrow job. Often one bot gathers context and drafts the next step; another writes code, generates an image, or places a call.

The eight listings

These are the bots from that post, listed on grokdir with the names they use on their public x.ai pages:

• Tech Demos — weekday bookmark scout that picks one library and, after approval, plans a demo with a coding agent
• loops — outer-loop engineering bot that writes /goal-style prompts and launches coding agents
• X Algo — posting advisor that reads public ranking code and live metrics
• Writing Bot — prose partner for drafts and revisions without flattening the writer's voice
• Connections — personal CRM that files X mutuals by place in a Notion board you own
• Image Gen Bot — Imagine prompts, stills or clips, then background cleanup
• skippy — San Francisco street-sweep lookup from a pin, address, or intersection
• dial bot — outbound Bland calls on request, then a report of what happened

The same sharing format covers a daily DevRel loop, an engineering outer loop, social timing, editing, a travel CRM, media, a civic-data chore, and a phone call.

How sharing works

In the Grok Bot app, a bot's settings include Share as template. Publishing produces a public link. Anyone with it can preview the configuration and add a copy. Palmer's argument is that this passes along the workflow without publishing the private context that made the original bot useful to him.

That is also the risk. The link exposes whatever is still in the configuration. Keys, internal URLs, and customer data have to come out before you publish. On the receiving side, a third-party bot can act through connectors you attach. Treat these the way grokdir treats any listing: read the job, open the real x.ai/bot/ page, reconnect only what you need, and keep irreversible actions behind a confirmation.

The original post is on X. The listings above are the directory entries for those eight templates.