Order
/Order
Zamawia jedzenie i usługi online przez zatwierdzonych dostawców, a każdy zakup wymaga pytania i limitu wydatków.
- Autor
- danielmiessler ↗
- Repozytorium
- LifeOS ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 05.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 8
- Skrypty
- 2
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: Tools/SubmitOrder.ts, Tools/WatchOrder.ts
Co robi i kiedy
Zamawia jedzenie i usługi online przez zatwierdzonych dostawców, a każdy zakup wymaga pytania i limitu wydatków.
Oryginalny opis (EN)
Orders real-world goods and services online through approved providers (DoorDash via dd-cli, Amazon planned); every purchase is a must-ask with a spend ceiling. USE WHEN order food, order DoorDash, get me lunch, get dinner delivered, reorder my usual, order online, order takeout, place a food order, DoorDash search, buy this online, order from Amazon. NOT FOR phone bookings, where to eat, business search or reviews (a scraping skill or Google Maps), or taste and gear skills.
Jak działa
- Ideal State
- Intent Routing
- The Purchase Gate (applies to every provider)
- Examples
- Gotchas
- Tools
- Data & Config
Podgląd SKILL.md
---
metadata:
short-description: "Order food through DoorDash with explicit purchase confirmation and spending limits. Amazon is planned. Use a restaurant-recommendation skill for where to eat."
name: Order
evals:
manual:
reason: "purchase verification is intentionally approval-gated and must not create a real order as an automated test"
falsifier: "the provider receipt differs from the confirmed cart, price ceiling, delivery destination, or requested order status"
version: 1.2.6
description: Orders real-world goods and services online through approved providers (DoorDash via dd-cli, Amazon planned); every purchase is a must-ask with a spend ceiling. USE WHEN order food, order DoorDash, get me lunch, get dinner delivered, reorder my usual, order online, order takeout, place a food order, DoorDash search, buy this online, order from Amazon. NOT FOR phone bookings, where to eat, business search or reviews (a scraping skill or Google Maps), or taste and gear skills.
---
# Order
Turn a plain request — "order me ramen", "reorder my usual" — into a real order for physical goods and services, through provider integrations that are sanctioned and safe. One skill, one purchase-gate, many providers.
## Ideal State
- No money moves without the principal's explicit yes on a fully itemized total, under the per-order ceiling, through a sanctioned provider path, with nothing substituted or absorbed on their behalf.
- Searches, menus, order history and delivery status are answered at once, with no gate.
- After every placed order the principal holds the command that follows it to a terminal state and texts them when it is near and when it lands (`Tools/WatchOrder.ts`, run in their own second terminal, since the watcher lives only as long as that terminal).
- The provider account stays in good standing: official tooling only, the owner's own orders only, never a scraper.
## Intent Routing
| Intent | Trigger | File |
|----------|---------|------|
| **Setup** | "set up ordering", "install dd-cli", "dd-cli login", "re-auth DoorDash", "update dd-cli" | `Intents/Setup.md` |
| **Doordash** | "order DoorDash", "get me food", "search restaurants", "reorder my usual" | `Intents/Doordash.md` (live, official `dd-cli`) |
| **Amazon** | "order from Amazon", "buy this on Amazon" | `Intents/Amazon.md` (stub — sanctioned deep-link path, not yet built) |
| File | Read when |
|------|-----------|
| `Safety.md` | the reasoning behind each purchase-gate rule, or deciding whether something needs the gate |
| `Setup.md` | first-time setup: Config.md fields, the DoorDash account and waitlist, and the commands that prove the install works |
## The Purchase Gate (applies to every provider)
Spending money is irreversible and outward-facing, so it stays in the "must ask" column no matter how autonomous the tooling gets; a standing deploy-without-asking authorization does not extend to charges. Before any order that costs money, all four must hold. The reason behind each rule: `Safety.md`.
1. **Explicit confirmation before the charge.** Show the full itemized cart — every line, subtotal, fees, tip, tax, delivery, grand total — and get a clear yes on that total before invoking checkout. Never chain checkout onto search in one uninterrupted run.
2. **Per-order USD ceiling.** The standing ceiling is the "Per-order ceiling" line in Config.md; with no such line it is $75. An order above it stops and asks even if otherwise confirmed. A raise applies to that one order only. In code, `Tools/SubmitOrder.ts` refuses any request whose stated amount, or the total in the provider's own re-read preview, is above the ceiling (or when the preview carries no readable total), and any submit without the principal's echoed confirmation token. Submit only through `Tools/SubmitOrder.ts`. A one-order raise has no code path: that order is the principal's to place.
3. **Sanctioned paths only.** Official provider tooling (dd-cli) or sanctioned mechanisms (Amazon deep-links). Never the ToS-violating browser-scraper MCPs — they risk a permanent account ban (see Gotchas).
4. **No silent substitution.** Out-of-stock item, price moved, address ambiguous, store closed → surface it and re-confirm. Never swap an item or eat a price change on the principal's behalf.
## Examples
**Example 1: Search (free, no gate)**
```
User: "What ramen can I get delivered right now?"
→ Doordash intent → dd-cli --json-output search --query "ramen" --address-id <home> --intent "..."
→ Returns nearby stores + menus. No charge, no gate — search is free.
```
**Example 2: Order with the gate**
```
User: "Order me the tonkotsu from that first place"
→ Doordash intent: menu → cart add-items → order preview --beautify
→ I show the preview verbatim + the named card + the delivery address + tip, and stop (Gate #1)
→ Tools/SubmitOrder.ts --issue-confirmation → the principal echoes the token → SubmitOrder.ts --confirmation-token <echo> → the principal runs Tools/WatchOrder.ts in a second terminal; it texts them when the Dasher is nearby and when it lands
```
**Example 3: Blocked by the ceiling**
```
User: "Order the family feast for the party"
→ Cart totals $128 — over the $75 ceiling (Gate #2)
→ I stop, show the total, and say it is above the ceiling, so the principal places this order themselves (or raises the Per-order ceiling line in Config.md)
```
## Gotchas
- **Community DoorDash/UberEats/Instacart "MCP" servers are Playwright scrapers that violate ToS.** DoorDash runs Cloudflare Bot Management with real IP-ban enforcement. Never route an order through them to dodge the waitlist — a banned account is a worse outcome than waiting.
- **DoorDash may finalize a CLI order without a second confirmation on its side,** so the purchase gate here is what stands between a cart and a charge.
- **Personal use only:** the account owner's own account and own orders. Never order for anyone else through it.
- **Amazon has no consumer purchase API,** which is why Amazon here is sanctioned-deep-link only. Never automate checkout on the consumer account.
## Tools
- `Tools/SubmitOrder.ts` — the only `order submit` path. `<request.json> --issue-confirmation` re-reads the preview and addresses and prints a challenge token; `<request.json> --confirmation-token <echo>` checks the configured ceiling against both the request amount and the preview total, that the request amount is the preview total, that the request address and card are the account's default address and card (the ones `order submit` uses), and the principal's echo, then runs `dd-cli order submit` without `--yes`.
- `Tools/WatchOrder.ts` — follows one order to a terminal state and texts the principal via `LIFEOS/TOOLS/NotifyPrincipal.ts` at `dasher_nearby`, `completed`, and any problem state. Hand the principal its command after every submit, to run in a second terminal; it stops when that terminal closes.
## Data & Config
Per-install values live in `<configRoot>/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Order/Config.md` (configRoot is `$CLAUDE_CONFIG_DIR` when set, else `~/.claude`): home address id, other saved-address ids, default card brand + last4, the "Per-order ceiling" line, the food preferences file, and the `--intent` template. Read it at the start of every Doordash intent; never hardcode ids in this skill. The food preferences file it names lets "get me food" resolve to a real choice. With no Config.md, `Tools/SubmitOrder.ts` refuses and points at `Setup.md`. The DoorDash token itself lives in the macOS Keychain, written by `dd-cli login`.
Pliki w paczce (8)
- SKILL.md 7 KB
- Safety.md 2 KB
- Setup.md 5 KB
- Intents/Amazon.md 2 KB
- Intents/Doordash.md 11 KB
- Intents/Setup.md 6 KB
- Tools/SubmitOrder.ts 10 KB
- Tools/WatchOrder.ts 6 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · danielmiessler/LifeOS | 95 | MIT |
| Trevojan/regency | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki a89d2182b362 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100doordash-group-orders
Zamawia jedzenie grupowo przez DoorDash CLI z trwałej listy zespołu: jeden wspólny koszyk, przypisanie pozycji do osób, podział kosztów z opłatami, rotacja płacącego i kontrola alergenów przed zamówieniem. - 100doordash-spend-guard
Egzekwuje twardą politykę wydatków przy zamówieniach DoorDash robionych przez agenta: limit na zamówienie, limity dzienne, tygodniowe i miesięczne, przerwa między zamówieniami i zablokowane godziny. - 96food-order
Ponownie zamawia wcześniejsze dania z Foodora, pokazuje zawartość koszyka i śledzi status oraz czas dostawy. - 95food402
Zamawia jedzenie w TGO Yemek (Trendyol GO), tureckim serwisie dostaw: przeglądanie restauracji, wyszukiwanie dań, adresy dostawy, historia zamówień i płatność z 3D Secure. - 86buy
Kupuje, zamawia, rezerwuje, zwraca lub anuluje zamówienie w sklepie internetowym dla użytkownika przez Menta, po jego wyraźnym poleceniu. - 100doordash-drive-webhooks
Odbiera i uwierzytelnia webhooki DoorDash Drive, sprawdza nagłówek Authorization i obsługuje zdarzenia dostawy, np. odbiór czy anulowanie.