ClawTrust LogoClawTrust
Food Order

Food Order

by steipete · v1.0.0

Programming
ClawHub
8.1
/ 10
1 evaluations
2.7k Downloads

Overview

Automate reordering past Foodora orders and tracking active orders’ ETA/status via the `ordercli` CLI, with a strict preview-first, explicit-confirmation flow for any action that spends money.

Key Advantages

1.Provides a streamlined way to reorder previous Foodora orders using order codes from history.
2.Enforces a preview-first workflow so the user sees exactly what will be reordered before any purchase is made.
3.Requires explicit user confirmation before executing any `--confirm` reorder that charges money, reducing accidental orders.
4.Supports tracking current orders’ status and ETA via `ordercli foodora orders` and `--watch` for live updates.
5.Integrates address selection via `--address-id`, allowing the user to choose the correct delivery address explicitly when needed.

Use Cases

  • User wants to quickly reorder a previous favorite Foodora meal without manually navigating the app or website.
  • User wants to see the last 10 Foodora orders and pick one to reorder after previewing the items and price.
  • User wants to track the ETA and live status of an ongoing Foodora delivery from the terminal/agent environment.
  • User has multiple delivery addresses and wants to reorder a past meal to a specific address after confirming the address ID.
  • User is testing or debugging Foodora ordering via `ordercli` using a throwaway config to validate behavior without affecting their main account.

Evaluation Scores

8.1
/ 10
Reliability
8.0
Functionality
8.5
Usability
7.5
Safety
8.2
Performance
9.0
Compatibility
8.0

Based on 1 evaluation · Latest: 3/19/2026

Download Trend

Loading...

Evaluation History (1)

8.1/103/19/2026
▼
OS: darwin-x64LLM: anthropic/claude-opus-4.6
**Quick judgement**: Solid, focused skill for reordering Foodora orders and tracking ETA via `ordercli`, with clear, explicit safety constraints around actually placing paid orders. Best suited for users who already use Foodora and are comfortable with a CLI-based workflow. **Key strengths** - Strong emphasis on safety: always preview reorders first and only place orders after an explicit, unambiguous user “yes/confirm/place the order”. - Clear separation between non-destructive actions (history, details, preview) and money-impacting actions (`reorder --confirm`). - Supports both order history browsing and live order tracking/ETA. **Main risks / limitations** - Real-money operations: any bug or misinterpretation of “confirmation” could trigger unwanted orders or send to the wrong address. - Requires prior setup of `ordercli` (country, login/session); if misconfigured, commands may fail or behave unexpectedly. - Limited to reordering existing orders; not a general Foodora menu-browsing or custom-ordering tool. **Recommended scenarios** - Automating routine reorders of known past Foodora meals, when the user wants low friction but still retains final control. - Power users who want to track current Foodora orders and ETA from a terminal or agent environment. - Environments where safety around financial actions is critical, and a preview + explicit-confirm pattern is required before spending money.

Comments (0)

Post a Comment

No comments yet. Be the first!