Every Grok Bot Hack I Know (Aug 2026)｜Matt Van Horn
输入“/”快速插入内容
Every Grok Bot Hack I Know (Aug 2026)｜Matt Van Horn
Every Grok Bot Hack I Know (Aug 2026)｜Matt Van Horn
用户3931用户3931今天修改
导读
如果你正打算把 Grok Bot 接入日常的日程、邮箱与调研，同时希望避免建了一堆 Bot 却陷入维护混乱，这篇文章很实用。作者给出的核心解法很具体，包括用独立 AgentMail 邮箱隔开每个 Bot 的发送信誉与故障影响，以及设立单一入口 Bot 对内分派任务，让人不用在多个会话间来回倒手。读完后最容易立刻落地的一步，是把文中的安装提示词直接发给 Bot，装上 Compound Engineering 规范，强制它每次接活都先出规划再开工。想进一步理顺多个 Bot 之间的分工配合与共享机器机制，可以搭配阅读库内的「4.2 团队编排」。
Three months ago I posted "Every Agentic Engineering Hack I Know." It hit 1M views. Then I wrote up what people were using Grok Bot for, which was a ranking of strangers. This one is mine.
Grok Bot is two weeks old and it already runs my inbox, my research, my meeting notes, my kids' calendar, my grocery cart, and as of this morning it tries to make my phone calls for me in Portuguese. I build last30days (59K stars), Printing Press (6.3K stars), and Agent Cookie, and all three are installed inside a bot that works while I sleep. These are my hacks.
HACKS
The YOLO TL;DR Hack: paste this entire article into your bot and tell it to make a plan to set up everything in it, then work that plan one hack at a time. That is my whole stack, no reading required.
1. Install Compound Engineering, and Make It Plan First
Rule number one in June, rule number one now. Agents perform better when they write a plan first. Not sometimes. Every time. A bot with a plan finishes the job. A bot without one cuts corners and stops early, then tells you it is done.
So the first thing I did to my Grok Bot was install Compound Engineering into it, globally, and then start every non-trivial job with a plan. ce-plan to think, ce-work to build. All day long.
The install is not in the plugin catalog, which stops most people. It should not. The skills are just folders, and Grok Bot can install them itself if you tell it to stop asking and go.
HACKS
Paste this into your bot:
代码块
Install Compound Engineering globally in Grok Bot from
https://github.com/everyinc/compound-engineering-plugin (EveryInc/compound-engineering-plugin).
Do this now. Do not wait for more confirmation.
If it is in the Grok Bot / Cursor plugin catalog, install that. If SearchPlugins / the
catalog has no match (this is common), do NOT stop and do NOT ask me to install it in
Cursor desktop. Download the repo (zip is fine; no persistent clone needed) and install
every skill under skills/ as a Grok Bot user workflow:
- Each skills/<name>/ folder (ce-plan, ce-work, ce-brainstorm, lfg, etc.) becomes a
workflow named after that folder.
- Copy SKILL.md plus any sidecar files the skill needs (references/, scripts/, assets).
A SKILL.md-only copy is broken for skills that load bundled references.
- Register each workflow so @ce-plan, @ce-work, @ce-brainstorm, @lfg, and the rest
actually invoke.
- Overwrite/update if an older copy already exists.
- Skip secrets, API keys, and any skill that requires a token I did not provide.
Done when:
1. You list the installed skill names.
2. @ce-plan, @ce-work, and @lfg are invocable from this chat.
3. You say so in one short message.
Do not clone this into a project repo. Do not open a PR. This is a Grok Bot skill install,
not application code.
2. Give Your Bot an Inbox
I have been giving my agents email addresses with AgentMail for a while now, well before Grok Bot existed. I liked it enough that I begged Adi to let me invest, and he let me. Then Grok Bot shipped and it turned out to be the best fit the thing has ever had.
The reason is the one Adi makes himself, and it is not "email is convenient." The default move is to plug your bot into your own Gmail, which means every bot shares your inbox and sends as you. Your outreach bot annoys one prospect, your domain gets flagged, and now your personal mail stops delivering. One bot's mistake takes the whole fleet down. Give each bot its own real address and it gets its own sending reputation, its own threads, and its own blast radius.