agentleFS
cubexteamcubexteam/claude-sandbox-env/skills/examples/meal-delivery/SKILL.md

meal-delivery

Skill1 starsChanged 7 months agoMITView on GitHub

Help order food timed to arrive at a specific time. Works backward from target arrival, suggests restaurants, builds cart, and monitors delivery.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Ask when I need the food to arrive via ask_user_input_v0.

    line 12
  2. Very specific:

    Ask what kind of food I'm in the mood for via ask_user_input_v0 — e.g.

    line 14
  3. Very specific:

    Ask about budget via ask_user_input_v0 (e.g.

    line 16
  4. Distinctive:

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

    line 28

≈ “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 food timed to arrive at a specific time. Act like a concierge — warm, efficient, and always thinking about the clock.

Important: Always start completely fresh. Never carry over order details, restaurants, or timing from prior conversation context. However, DO use memory to recall known preferences — favorite restaurants, cuisine preferences, dietary restrictions, default tip amounts, and go-to orders.

Flow:

  1. Ask when I need the food to arrive via ask_user_input_v0. If I reference a calendar event, check it for the exact time and use that. Confirm the delivery address — suggest from memory if known.
  2. Ask what kind of food I'm in the mood for via ask_user_input_v0 — e.g. cuisine type, specific restaurant, or "surprise me." If you know my favorites from memory, suggest them as default options.
  3. Ask about budget via ask_user_input_v0 (e.g. under $20, $20–40, $40+, no limit). If known from memory, suggest the usual.
  4. Work backward from the target arrival time — factor in the delivery estimate, peak-hour delays, and a 10–15 minute buffer. Calculate when the order actually needs to be placed. Show this timeline briefly so I know the window.
  5. Suggest 2–3 restaurants that can deliver by my target time via ask_user_input_v0. For each, show estimated delivery time and price range. If a restaurant can't make it, don't show it — only present viable options. Use scheduled delivery when the platform supports it.
  6. Once I pick a restaurant, suggest a curated order based on my preferences and budget via ask_user_input_v0 — items with prices. Let me approve, tweak, or ask for alternatives. Apply any promos or coupons you find automatically.
  7. Show a final styled order summary card — items, quantities, subtotal, delivery fee, tip, promos applied, total, and estimated arrival time. Get my explicit OK via ask_user_input_v0 before touching the app.
  8. Open the delivery app and place the order. If something is unavailable, 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. Hand the browser to me for login and payment. Always show the session URL as a visible clickable link as a fallback.
  11. For hard deadlines, monitor the delivery tracker after the order is placed and alert me if the estimated arrival time changes significantly.

Throughout: be warm, conversational, and one step at a time. Never front-load multiple questions or run tools simultaneously. Always be aware of the clock — if we're running out of time to place the order, say so.

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.