Personal Grok Bot
team setup
Calendar, home, goals, money, travel, and daily tasks — written into named Bots, so follow-through is not stuck in your head.
Set up my personal team
So follow-through is written down, not stuck in one person’s head. Start from a full questionnaire, a hobby team, or one mission skill. Grok Bot is a separate desktop app; this site only builds the files. No account. Answers stay in this tab.
These two questionnaires build a ZIP in your browser. You install those files in the Grok Bot desktop app — named Bots, written jobs, a first task you can check. Blueprint, Method and the earlier intake quiz are examples or older tools.
grok-bot-personal-setup.zip or grok-bot-business-setup.zip. No account. Answers stay in this tab.Calendar, home, goals, money, travel, and daily tasks — written into named Bots, so follow-through is not stuck in your head.
Set up my personal teamCustomers, sales, projects, money, and daily work — written into named Bots, so the operation is not stuck in one person’s head.
Set up my business teamYour answers stay in this tab. Save a draft if you want to come back. No account is required to generate files.
Read the operator manual ↗Each kit is the smallest team that can run that interest: two named Bots, two jobs, a first task you can check. Split when the words differ. Add a third Bot only when you catch yourself correcting context.
Meals that match what you already eat.
Kitchen Ops · Recipe Scout
Open the cooking team 02 BotsSessions that fit the week you actually have.
Movement Planner · Planning Bot
Open the movement team 02 BotsAn itinerary you can check, not a booking Bot.
Travel Planning Bot · Papers Bot
Open the travel team 02 BotsA session you will do, plus a library of references.
Practice Coach · Taste Librarian
Open the practice teamMore kits in the catalog, including growing, learning, family logistics and bills. Starter files, not live Bots.
See every interest team ↗A mission is a focused skill: inputs, steps, done-when, stop-when. Start with one task. Save a skill after you accept the trial. Add a routine only after that.
What moved, what is stuck, next three actions.
A brief with sources. Unknowns stay unknown.
Useful writing. Send stays a human action.
One accepted trial, then a skill, then maybe a routine.
Sourced itinerary. You still book.
This week, from stated priorities and sources.
Also purchase research and a community interview brief. Copy the skill or download a one-Bot ZIP.
See every mission ↗Grok Bot changes fast. Read sourced notes here instead of trusting last month’s memory. Every fact keeps its source and the date we checked it.
So a test cannot quietly open sites, change files, or use connected accounts you did not mean to share. Set those rules before you connect anything.
A test can open websites, change files, and use connected tools. Start with a small task you can check.
Your Bots can share files, browser logins, and connected accounts. A Bot name does not keep those things private from your other Bots.
An approval lets the Bot do the action it shows you. Read the action before you say yes.
The manual, an example roster, and sourced records — so you can operate the team and check a claim without relying on stale chat memory.
Install, jobs, access, and how to check the work — written down so you do not reconstruct it from memory. This is reference, not the setup questionnaire.
Open the manualLook up a claim with its source and date, instead of trusting model memory.
Sample Bots and jobs for a business like yours. Use a setup questionnaire if you want files for your own team.
The older 86-question scoring quiz. Kept for reference; it does not make the current setup ZIP.