When should you use it?
- You cook from a favorite site
- Picky eaters narrow your options
- You want a reusable list rather than browsing each week
Not for: Medical or allergy-driven diets; Sites that prohibit copying content
What do you need, and what do you get?
You need
- The recipe site
- A description of what your family will eat
- A desktop agent that can browse and make files
You get
- A shortlist grouped by confidence
- An index document
- A sortable spreadsheet
How does it work, step by step?
- Point it at the siteName the cooking site and the recipe category.
- Describe the eatersExplain what tends to work and what gets refused.
- Ask for groupsHave it sort keepers into clear confidence tiers.
- Get files, not chatHave it produce a contents document plus a sortable sheet linking each dish.
- Cook and refineMark what worked and ask it to update the ratings.
The prompt
Our own prompt, inspired by Beth Gebhard and written to work in Custom agent. Values in lime are placeholders.
Go to [recipe site] and review its dinner recipes. Keep only ones likely to suit [describe eaters and dislikes]. Sort them into three tiers (sure winners, easy weeknights, worth trying with tweaks) and give a one-line reason each. Create an index document and a spreadsheet with name, link, tier, prep time and main ingredients. Do not copy full recipes.
Inspired by Beth Gebhard: What Is OpenAI Codex? A Communications Professional’s Review. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Store links, not copied recipes, to respect the creator's site.
- Its judgment of kid appeal is a guess; your family's verdict wins.
Our take
Beth Gebhard's first Codex task is a charming, practical use of a desktop agent: point it at a cooking site you already love, describe two picky eaters, and get a shortlist instead of scrolling for an hour. Reviewing hundreds of dinners and sorting keepers into confidence tiers produces something you reuse, which is the right bar for a first experiment. Keep the original recipe links so the creators, such as the cooks she credits, still get the visits. Add columns for prep time and for what the kids actually said after each meal, and the spreadsheet becomes a living family cookbook rather than a one-off dump. Tell the agent allergens and hard nos up front, or it will keep recipes that look mild on paper and fail at the table. Recheck the shortlist every few months as tastes change. Prefer sites whose terms allow personal research scraping, and do not republish their recipes. Start with one site you trust before widening the search.
Where the time goes back: Browsing hundreds of recipes to find a few that suit a family takes an evening; this took minutes.
FAQ
How many recipes made the cut?
Was she an experienced user?
Source and credit
Inspired by Beth Gebhard. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- What Is OpenAI Codex? A Communications Professional’s Review
- Creator
- Beth Gebhard
- Published on
- youbetabelieveit.substack.com (Substack)
- Original date
- Jun 23, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.