Luckin Ordering
Apps & Automationluckin-orderingLuckin Ordering is an Agent Skill for apps & automation published in the AIDotNet/OpenCowork repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Order Luckin Coffee for store pickup with the My Coffee extension tools. Use when the user asks to order coffee, buy a Luckin drink, check a coffee order, or cancel one. Covers store selection, product search, SKU customization, order preview, payment QR, and order status.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/AIDotNet/OpenCowork/blob/HEAD/resources/extensions/my-coffee/skills/luckin-ordering/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/luckin-ordering, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Luckin Ordering Workflow
Order Luckin Coffee for store pickup using the My Coffee extension tools
(extension__my-coffee__*). Follow this workflow as a contract; the gates below exist because
the upstream API rejects out-of-order calls.
Preflight
- Run
check_token. If the token is missing, stop and walk the user through Settings -> Extensions -> My Coffee before anything else. - If tool parameters ever look stale or a call fails with a schema error, run
list_toolsand re-check the current schema before retrying.
Hard Rules
- Pickup only. For delivery requests, ask whether store pickup works instead; do not improvise a delivery flow.
- Never pick a store for the user. Show candidates from
query_shop_listand wait for an explicit choice. Only setlocationIsPrecise: truewhen the user gave exact coordinates. - Never guess SKUs. Customizations (temperature, sweetness, milk, size) go through
query_product_detailthenswitch_product; search results alone do not identify a SKU. preview_orderis a mandatory gate beforecreate_order: same store, same product list. The create call is rejected otherwise. Coupons returned by preview are passed through automatically.- Show only the payment QR (
payOrderQrCodeUrl) after creating an order. Show the pickup code only whenquery_order_detailreports the order is paid and returns pickup info. create_orderandcancel_orderare mutating actions; confirm intent with the user first.
Flow
- Ask what drink they want and roughly where they are (or reuse the store from earlier in the conversation).
query_shop_list-> user picks a store.search_productin that store -> if customization is requested,query_product_detail+switch_productto get the final SKU.preview_order-> confirm the final price with the user.create_order-> show the payment QR and tell the user to scan it.- On request,
query_order_detailfor status/pickup code;cancel_orderto cancel.
Keep replies short and warm. Lead with the result (store found, price confirmed, QR ready), not with tool mechanics.