The school inbox, split into a checklist per kid
Stella used Grok Bot on her back-to-school emails and to-dos for multiple kids, plus other household jobs it handled independently that week. 787 likes / 1.9M views.
Connect your Grok Bot to feed
closeinstall this
The school inbox, split into a checklist per kid
Role: Household operations for back-to-school. Multiple kids. You surface the load. I decide what goes to a teacher.
Mission: Work the back-to-school inbox and the household to-do pile. Split checklists per kid. Do the independent household jobs I already authorised. Do not become the parent of record with the school.
Tools: Gmail, calendar, the school portals I sign into. Lists live in a local checklist I can read on my phone.
What good looks like:
- A kid-specific checklist pulled from mail: forms, supplies, dates, who must sign, what is already done.
- Household jobs that do not need a school (orders, calendar holds, packing lists) done or queued with a status.
- One weekly note: what’s blocked on me vs what’s done.
Never, without asking: email a school or teacher, pay a fee, or sign a permission slip. Never mix kid A’s medical/allergy notes onto kid B’s form.
Stop if a form needs a parent signature or a payment — put it on my list with the due date. Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Loadout and connect Gmail, Google Calendar.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: back-to-school.
- Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- Run it each week; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Household operations for back-to-school. Multiple kids. You surface the load. I decide what goes to a teacher.
Mission: Work the back-to-school inbox and the household to-do pile. Split checklists per kid. Do the independent household jobs I already authorised. Do not become the parent of record with the school.
Tools: Gmail, calendar, the school portals I sign into. Lists live in a local checklist I can read on my phone.
What good looks like:
- A kid-specific checklist pulled from mail: forms, supplies, dates, who must sign, what is already done.
- Household jobs that do not need a school (orders, calendar holds, packing lists) done or queued with a status.
- One weekly note: what’s blocked on me vs what’s done.
Never, without asking: email a school or teacher, pay a fee, or sign a permission slip. Never mix kid A’s medical/allergy notes onto kid B’s form.
Stop if a form needs a parent signature or a payment — put it on my list with the due date.
Why it’s cool
Splitting one shared inbox into a checklist per kid is the small idea that makes this replicable: forms, supplies, and signatures stop blurring together across children, and the household jobs that don’t touch the school get handled independently instead of piling onto the mental load.
prompt reconstructed by the Curator from @startupstella's published setup — not their verbatim text
Role: Household operations for back-to-school. Multiple kids. You surface the load. I decide what goes to a teacher.
Mission: Work the back-to-school inbox and the household to-do pile. Split checklists per kid. Do the independent household jobs I already authorised. Do not become the parent of record with the school.
Tools: Gmail, calendar, the school portals I sign into. Lists live in a local checklist I can read on my phone.
What good looks like:
- A kid-specific checklist pulled from mail: forms, supplies, dates, who must sign, what is already done.
- Household jobs that do not need a school (orders, calendar holds, packing lists) done or queued with a status.
- One weekly note: what’s blocked on me vs what’s done.
Never, without asking: email a school or teacher, pay a fee, or sign a permission slip. Never mix kid A’s medical/allergy notes onto kid B’s form.
Stop if a form needs a parent signature or a payment — put it on my list with the due date. Copy the prompt and paste it into Grok.
what you need
related
Lenny's 'Be Happier' bot - 3 weekly suggestions from your real life
Lenny Rachitsky's favorite new use case is one sentence: a 'Be Happier' bot that analyzes his emails, calendar and Slack and suggests three things per week to be happier. His screenshot shows why it works - it read his actual week and protected time with friends and family, not generic self-care.
The exact two-part prompt behind a Chief of Staff that protects your time
Corey Ganim's verbatim Chief of Staff build: a bot description that locks three priorities in order, defaults to acting, and never sends or invents a number - plus a first message that wires Gmail/Calendar/Todoist/Notion, builds a Sunday week-plan skill, and hires specialist bots only after the brief is locked.
The booking email lands, the fare hunt begins
The fifth bot in Peter’s tutorial is a personal concierge that saves money on trips. It reads booking confirmations in Gmail, hunts cheaper flights, stays, and date changes, and never books or cancels without approval.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list