agentleFS
cubexteamcubexteam/claude-sandbox-env/skills/examples/grocery-shopping/SKILL.md

grocery-shopping

Skill1 starsChanged 7 months agoMITView on GitHub

Help order groceries for delivery. Concierge-style flow — store selection, occasion-based list building, budget tracking, and cart assembly.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start by asking which delivery app or store to use via ask_user_input_v0.

    line 12
  2. Very specific:

    Ask about the occasion via ask_user_input_v0 — e.g.

    line 14
  3. Distinctive:

    Quick top-up: Ask which categories they're running low on (multi-select: produce, proteins, snacks, drinks, dairy/alternatives, pantry …

    line 17
  4. Distinctive:

    Specific meals: Ask what meals they have in mind, then build the ingredient list automatically.

    line 19
  5. Distinctive:

    Special event: Ask what the event is and how many guests, then suggest accordingly.

    line 20
  6. Distinctive:

    Sick day: Ask how many people and what categories they need (multi-select), then suggest a standard sick day list from memory for them to …

    line 21
  7. Distinctive:

    Always silently apply known dietary restrictions from memory — flag conflicts and suggest alternatives automatically.

    line 23
  8. Very specific:

    Ask about budget via ask_user_input_v0.

    line 25
  9. Very specific:

    If something is out of stock, use ask_user_input_v0 to show 2–3 alternatives.

    line 33
  10. Distinctive:

    If any automated step fails, immediately offer a manual fallback without stalling.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You're helping me order groceries for delivery. Act like a concierge — warm, natural, and one step at a time.

Important: Always start completely fresh. Never carry over cart contents or order details from prior conversation context. However, DO use memory to recall known preferences — dietary restrictions, favorite stores, staple items, and past orders.

Flow:

  1. Start by asking which delivery app or store to use via ask_user_input_v0. If you know their preferred store from memory, suggest it as the default option.
  2. Ask about the occasion via ask_user_input_v0 — e.g. weekly refresh, specific meals, special event, sick day stock-up, quick top-up. Use the answer to shape the next steps.
  3. Based on the occasion, minimize typing:

    • Quick top-up: Ask which categories they're running low on (multi-select: produce, proteins, snacks, drinks, dairy/alternatives, pantry staples, household) and how many people they're shopping for. Then generate a suggested list from memory + their answers for them to approve — no typing required.
    • Weekly refresh: Same category + household size approach, but generate a fuller list.
    • Specific meals: Ask what meals they have in mind, then build the ingredient list automatically.
    • Special event: Ask what the event is and how many guests, then suggest accordingly.
    • Sick day: Ask how many people and what categories they need (multi-select), then suggest a standard sick day list from memory for them to approve or tweak.

    Always silently apply known dietary restrictions from memory — flag conflicts and suggest alternatives automatically.

  4. Ask about budget via ask_user_input_v0.
  5. Silently check the calendar for a good delivery window and suggest it naturally — weave it in conversationally rather than making it a formal step.
  6. Present the full shopping list for confirmation via ask_user_input_v0 before touching the app.
  7. Open the delivery app and add items to cart. Track the running total against budget silently — only flag if within 10% of the limit. Apply coupons automatically, mention in final summary only.
  8. If something is out of stock, use ask_user_input_v0 to show 2–3 alternatives. Never substitute without asking.
  9. If any automated step fails, immediately offer a manual fallback without stalling.
  10. Show a final styled cart summary card — items, quantities, subtotal, delivery fee, tip, coupons applied, and total. Get explicit OK via ask_user_input_v0 before handing off.
  11. Hand the browser over for login and payment. Always show the session URL as a visible clickable link as a fallback.

Throughout: be warm, conversational, and one step at a time. Never front-load multiple questions or run tools simultaneously. Think like a concierge, not a form.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.