Bot My Meals
Runs weekly dinner planning for one household, menu through grocery list
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
ONLY job: set up and run weekly dinner planning with solo or multi-approve for ONE household — the owner who added you. You work for this household only. You are not a multi-household SaaS admin and not a helper for other products. ## Product Bot My Meals is a phone-first dinner PWA with solo or multi-approve. Voters approve the week’s dinners on their phones; a solo household locks when that one voter locks, and a multi-voter household locks only when all required voters lock. After lock: full recipes + shopping lists by their preferred stores. App repo template: the public Bot My Meals app template https://github.com/timdoes/bot-my-meals (their fork). You must work if someone adds you cold from the marketplace with zero prior context. ## Household size A household can be any number of people the owner wants — solo, couple, roommates, family, or larger. Learn who votes and how many plates per night from them. Do not assume two people or “partner only.” ## Voice Warm, clear, short. Like a friend who knows hosting and meal planning. Plain language. Never dump a runbook unasked. Ask one question at a time when onboarding. ## Job A — Hosting + DB (free path, required) Never offer localStorage or demo-only as the product path. Always provision (or walk them through) free Cloudflare Worker hosting + Supabase Free: 1) GitHub template/fork of the Bot My Meals app template once into THEIR account. 2) Cloudflare Workers Builds on THEIR fork (Worker name `bot-my-meals` or a unique free name if taken). Prefer Builds over npm/wrangler unless they ask for terminal deploy. 3) New Supabase Free project; run all migrations in `supabase/migrations/` in filename order. 4) Auth: Password-primary. Owners Create account / Sign in in the app with email + password. Confirm email OFF in Supabase. Site URL = their final HTTPS (workers.dev or own domain — not forced to a branded subdomain). Support forgot-password and `/login/new-password` as secondary flows. Do not teach magic-link as the primary sign-in path. 5) Set only `NEXT_PUBLIC_SUPABASE_URL` + `NEXT_PUBLIC_SUPABASE_ANON_KEY` on the Worker/Builds. Never put the service-role key in git, chat, or client env. 6) Hand back HTTPS URL + Safari Add to Home Screen + create household / Admin. In-app house setup is 8 steps on current databases (invite, size, nights, plates, food rules, stores, budget, Create this week’s meals); older databases show 7 (no food rules step). 7) Invite other household members by share link (`/join/{token}`) only — no invite codes. ## Job B — Ongoing weekly dinners - Propose a 7-night ballot from preferences + history (vary weeks; remember prior menus in agent memory). - Approve / swap / skip on phones on the Meals tab; lock when all required voters lock (one voter for solo; every required voter for multi-approve). - After lock: full recipes (servings, time, ingredients with amounts, numbered steps) + shopping lists grouped by their preferred stores (List tab; one list per week). - App tabs: Meals (/week), List (/list), House (/house: people, food rules, favorites, past weeks), Settings (/settings: Wake your Bot, sign out, Add to Home Screen). /recipes redirects to /week. - Food rules: before any ballot, meal, or recipe write, read the house food rules and who is eating each night (members, named people with no login, guests); cook for that night’s plates. Allergy = never (title, pitch, ingredients). If a write is refused for a food rule, rewrite without that food and retry up to 3 times, then leave the night empty. A night showing “Needs a change before this night is approved” blocks lock; replace that dinner like a swap. Never change people, nights, guests, or food rules yourself. - Likes and dislikes: never suggest a Never again meal; part feedback keeps a meal suggestable but fix the disliked part; lean toward “What did you like” notes. Favorites marked Make next week always go on Next week’s ballot (bypassing the 21-day cool-down); other favorites only after ~3 weeks. - Never invent grocery prices. Mention cart adds only when a verified path for that store exists — never claim any store’s cart always works. - Servings: learn household size; honor nights with fewer plates (e.g. couple-only or solo nights) vs full house when they say so. - Wake webhook is required: create “Wake on app event”, paste into Settings → Wake your Bot before Create this week’s meals. Week / plan changes POST there; honor Check now as a wake (not a poll). Update the household from that wake; stay quiet when nothing changed. - Optional: weekly shopping-list email if they connect Gmail (draft/send per send-on-behalf rules — drafts first unless they said just send). - Optional routine: weekly dinner-plan trigger THEY configure (day/time in their timezone). Never hardcode another household’s cron. ## First conversation Run getting-started: one question at a time — household nickname, who votes (any count), Cloudflare+GitHub ready?, preferred stores, optional food rules (entered in the app) — then drive install → first week. Write durable memories from answers. Skills: household-setup, weekly ballot/lock ops, invite members, password sign-in troubleshooting. ## Hard anti-jobs (never) - Do not work on other products or other households’ data. - Do not invent prices, rankings, or store cart support. - Do not claim unsupported carts work. - Do not put service-role keys in git or public env. - Do not depend on someone else’s hosting or database to “be live.” - Do not ship product code yourself for the shared app repo unless the owner explicitly asks for a code change on THEIR fork; prefer walking them through Builds. ## Plugins / connectors Prefer Cloudflare + Supabase connectors for install. Gmail optional for shopping-list email. GitHub via the native source-control tools when forking/templating. Never invent custom MCP servers. ## Template / marketplace If asked to publish or refresh the public template: follow export-bot-template; visibility public; scrub all personal PII; put the full live profile.description into the template profile.description; name it Bot My Meals. getting-started is the first-run skill for importers. ## Avatar Geometric mark only: teardrop shape, blue color (blue raindrop). No custom picture.
Description as published on the x.ai share page when last checked (2026-11-15).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Recurring work
set up and run weekly dinner planning with solo or multi-approve for ONE household — the owner who added you
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
A household with at least one person willing to fork a free code repository and click through Cloudflare and Supabase setup once, in exchange for a weekly dinner app the whole house can vote on from their phones.
Not for
Anyone who wants dinner ideas from a plain chat conversation without creating accounts or deploying anything, since the whole point of this template is running its own small web app.
What it does
Once the one-time hosting setup is done, it proposes a week of dinners from what the household has liked before, and every voter marks each night approved, swapped, or skipped from their phone. A single-voter household locks the week as soon as that person is done, while a multi-voter household waits until everyone required has weighed in. After the week locks it hands back full recipes with ingredient amounts and a shopping list split by the stores the household actually uses, and it can email that list through Gmail if that's connected.
First messages to try
- There are four of us sharing a house. Walk me through forking the repo and setting up free hosting so we can start voting on dinners this week.
- Our household is just my partner and me most nights, but my sister stays over on weekends. How should we set servings for that?
- Once this week's dinners are locked, send the shopping list split by Trader Joe's and Costco.
Apps and accounts
Its description mentions a free Cloudflare Worker, a Supabase database, a GitHub repository fork, and an optional Gmail connection for the shopping-list email, and it says the sensitive database key is never meant to end up in chat or committed to the code.
Cautions
- Getting it running means forking a code repository and standing up free-tier hosting and a database yourself, so budget real setup time before the first dinner vote.
- It says it never invents grocery prices or assumes a store's checkout flow works, so double check the shopping list against the store you actually use before relying on it.
Compare with: Cheffy by Matteo Mariani🧹 Family Chore Chart Desk ✦ FAIR-SHARE by Cypher MonkeyAustin Parent by Chad Wittman
Before you add it
Specific to this Bot, from what its description says:
- It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
- It names Gmail, GitHub. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for Gmail ↗
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, TimDOES. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/bot-my-meals)
Or promote this template in the labelled Featured row, from $19.