skills/ordercli/SKILL.md
Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).
npx skillsauth add steipete/clawdis 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.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? | | ------------------------------------------------------ | --------------------------
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.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.