When should you use it?
- You reorder similar groceries often
- You run a capable local model
- Stores you use show live stock
Not for: Open-ended meal planning; Anyone without a local GPU setup
What do you need, and what do you get?
You need
- Ten typical past orders
- Rough pantry and fridge list
- Store stock lookups
You get
- A filled cart from in-stock items
- Updated pantry notes
- Order summary for approval
How does it work, step by step?
- Pick ten ordersChoose recent orders that reflect what you normally buy.
- Note shop detailsRecord stores, product codes and sizes you prefer.
- Keep a rough inventoryList what is usually in the fridge; precision is not needed.
- Check stock liveHave the skill query current availability before choosing items.
- Approve the orderReview the cart before it is placed.
The prompt
Our own prompt, inspired by eurekin on Hacker News and written to work in Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Use {past_orders_file} (my ten typical orders with stores and product codes) and {pantry_notes} to build this week's order. Check live stock at {stores} before adding each item, and suggest a substitute if something is unavailable. Show me the cart with prices and missing items, and wait for my approval before ordering.
Inspired by eurekin on Hacker News: Comment in RTX 5080 and RTX 3090 Setup: 80 Tok/s on Qwen 3.6 27B Q8. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Stale inventory notes lead to duplicate buys.
- Stock feeds can lag; allow substitutes.
- Keep payment as your step.
Our take
eurekin's setup is a clean example of matching the model to the job. Grocery reordering is mostly recall: what you usually buy, which shop, which size. Packing that into a skill means even a mid-sized local model does well, and live stock data fixes the classic failure of carts full of items that are out of stock. Keep the fridge inventory loose but current, allow a short list of substitutes for staples, and always approve the final cart yourself before payment. Refresh the ten sample orders each season, since summer and winter shopping differ. Local models help with privacy here, because order history and dietary details never leave the house. Still treat the shop's site carefully: rate-limit requests, respect terms, and prefer any official API or list feature they offer. Log substitutions the model chose so you can correct preferences over time. If someone in the household has allergies, put those as hard exclusions in the skill, not soft suggestions.
Where the time goes back: Routine grocery orders get built from your real habits and what is actually in stock.
FAQ
Why a local model?
Where do cloud models still win?
Source and credit
Inspired by eurekin on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Comment in RTX 5080 and RTX 3090 Setup: 80 Tok/s on Qwen 3.6 27B Q8
- Creator
- eurekin on Hacker News
- Published on
- Hacker News
- Original date
- Jun 13, 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, bookings 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.