20 GROKBOT TIPS from @poteto Founder Session If you missed Lauren Tan's founder session on Grok Bot Galaxy here are my top 20: 1. start with a mission, not roles. "compare 3 competitors' pricing by friday" beats "make a research bot". 2. first hire: a chief of staff bot. it hands out tasks and keeps context between bots. 3. starter team: coordinator, engineering owner, independent reviewer. more only once those 3 work. 4. day 1: teach it your top 3 priorities. ban sending, paying, publishing. 5. day 2: hand off one repetitive task. day 3: make it a skill. week 1: add 2-3 specialists. 6. show a flow once and it becomes a skill. no perfect prompt needed. 7. trust in stages: bots draft, you approve. full autonomy comes later. 8. approvals per action. external emails and calendar changes wait for your "yes". 9. "done" isn't proof. ask for screenshots, videos, data checks. 10. verify the actual behavior. bug was duplicates → proof is no duplicates, not "tests passed". 11. the builder never approves its own work. a fresh reviewer bot checks the final version. 12. overnight jobs need: a checkable finish condition, an isolated worktree, a decision log. push, never auto-merge. 13. write briefs like tickets: problem, repro steps, owner, acceptance criteria. 14. no guessing. bots run the app, take traces, use simulators. 15. give bots a feature map: tabs, selectors, shortcuts. fewer wasted tokens. 16. evals = unit tests. coordinator writes the rubric, sub-agents run blind in separate folders. 17. put your taste in CI, not prompts. Lauren bans useEffect and code comments there. 18. package methods as skills. her pstack plugin: /add-plugin pstack → /setup-pstack 19. verify locally before scaling in the cloud. 50 agents without checks = 50 expensive wrong answers. 20. count accepted work, not PRs: fixes accepted, review time, rework, escaped bugs, cost per change. save this. give your chief of staff its first mission tonight.