skills/ordercli/SKILL.md
Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).
npx skillsauth add openclaw/openclaw ordercliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use ordercli to check past orders and track active order status (Foodora only right now).
Quick start (Foodora)
ordercli foodora countriesordercli foodora config set --country ATordercli foodora login --email [email protected] --password-stdinordercli foodora ordersordercli foodora history --limit 20ordercli foodora history show <orderCode>Orders
ordercli foodora ordersordercli foodora orders --watchordercli foodora order <orderCode>ordercli foodora history show <orderCode> --jsonReorder (adds to cart)
ordercli foodora reorder <orderCode>ordercli foodora reorder <orderCode> --confirmordercli foodora reorder <orderCode> --confirm --address-id <id>Cloudflare / bot protection
ordercli foodora login --email [email protected] --password-stdin --browser--browser-profile "$HOME/Library/Application Support/ordercli/browser-profile"ordercli foodora cookies chrome --profile "Default"Session import (no password)
ordercli foodora session chrome --url https://www.foodora.at/ --profile "Default"ordercli foodora session refresh --client-id androidDeliveroo (WIP, not working yet)
DELIVEROO_BEARER_TOKEN (optional DELIVEROO_COOKIE).ordercli deliveroo config set --market ukordercli deliveroo historyNotes
--config /tmp/ordercli.json for testing.development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------