Skip to content

Grocery reorder with running low check

Works out what you are about to run out of from past grocery orders, then builds the cart and asks before anything is placed. A weekly read only ping lists what is due.

PersonalWorks with Claude Code · Claude Desktop with MCP+1Community example
Build your promptSee requirements

What it does

  • Reads your order history and works out each item's reorder rhythm
  • Lists what is due this week, including slow movers like detergent
  • Builds a cart from your staples file and offers priced substitutes for out of stock items
  • Shows the full cart and the delivery slot options
  • Sends a weekly read only reminder of what is running low

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Placing the order
  • Choosing substitutes and the delivery slot

You decide what happens next.

More about this workflow

This setup is for busy people who want their own day to run a little smoother. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it reads your order history and works out each item's reorder rhythm. Next, it lists what is due this week, including slow movers like detergent. Then it builds a cart from your staples file and offers priced substitutes for out of stock items. After that, it shows the full cart and the delivery slot options. Finally, it sends a weekly read only reminder of what is running low. It works with your web fetch and chat, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before placing the order and choosing substitutes and the delivery slot, and says plainly if a step cannot be undone.

“never places an order without showing you the full cart and getting a yes”
josthkko josthkko on GitHub · Oct 10, 2026
Before you startWeb fetch · Chat accessScoped permissionsClaude Code or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • Web fetch

    Handles the web fetch part of this job. Grant public pages, no logged-in sessions.

    API required: No. Built into most agent harnesses. It reads public pages with no login.

    No sign-up needed

  • Slack

    Handles the chat part of this job. Grant a bot token in the channels it needs.

    API required: Yes. Needs a Slack app created in your workspace. It gets a bot token with the scopes you approve.

    Sign up: Create a Slack app

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Fast and careful with your inbox and calendar.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Haiku 5.5

Cheapest Claude option for daily sorting.

From $0.10 per million input tokens and from $0.50 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

usual items, brands to avoid

2Your prompt

4 of 4 still empty
Fill these in before you run it: [STORE ACCOUNT] [STAPLES LIST: usual items, brands to avoid] [DELIVERY ADDRESS] [REMINDER DAY AND CHANNEL] You are the Grocery reorder with running low check agent. Works out what you are about to run out of from past grocery orders, then builds the cart and asks before anything is placed. A weekly read only ping lists what is due. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Reads your order history and works out each item's reorder rhythm - Lists what is due this week, including slow movers like detergent - Builds a cart from your staples file and offers priced substitutes for out of stock items - Shows the full cart and the delivery slot options - Sends a weekly read only reminder of what is running low What you must never do without a yes from a person: - Placing the order - Choosing substitutes and the delivery slot Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Claude Desktop with MCP, n8n

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Set up Web fetch. Keep it to public pages, no logged-in sessions.
  2. 2Connect Slack with its own login, not yours. Grant a bot token in the channels it needs.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: placing the order, choosing substitutes and the delivery slot.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope18 / 20

Runs on its own login across 2 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Scope: Run it on one tool only, with its own login that can see just what this job needs +2

Do all of these to reach 91, up from 83.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Grocery reorder with running low check](https://trustcase.dev/badge/grocery-reorder-with-running-low-check.svg)](https://trustcase.dev/use-cases/grocery-reorder-with-running-low-check)
HTML
<a href="https://trustcase.dev/use-cases/grocery-reorder-with-running-low-check"><img src="https://trustcase.dev/badge/grocery-reorder-with-running-low-check.svg" alt="Trustcase trust score for Grocery reorder with running low check" height="20"></a>

More personal workflows

  • Next day training plan with approval

    Each evening an agent proposes tomorrow's workout from your recovery data, training load, weather and weekly plan. Fixed rules check the proposal and nothing goes on the calendar until you tap approve.

  • Inbox sorter

    Clears the noise so you only see email that needs you.

  • Calendar guard

    Protects focus time and catches double bookings.

  • Travel planner

    Puts together trip options that fit your rules.