Cake Uncle Mall Ordering Assistant

Problem

When ordering on the Cake Uncle mall through a conversation, the city, address, product category, specification, quantity, and payment link still need to be confirmed in a fixed order. The flow also has small contract pitfalls: the district field should be area, not district; the detailed address field should be addr, not detail; and the address ID should be aid. On Windows, passing Chinese parameters directly through curl can also cause encoding issues. This skill packages those steps into a repeatable ordering flow: the current user supplies a token, then the assistant normalizes the city, chooses or creates an address, searches products, confirms one specification, generates an order link, and checks order status.

How It Works

• Auth and address: After the user provides a user_token, the skill stores the default city and default address ID. City names are normalized to city level, for example Shenzhen is converted to its city-level form. If no address exists, it creates one using province, city, area, addr, name, and phone.
• Product search: The keyword is mapped to a category: 1 for cakes, 5 for snacks, and 8 for flowers. sweets_lst is called, and results are shown as a fixed table with index, brand, item name, spec, price, and detail.
• Order and status: After selecting one specification, getOrderaddr generates the order URL. The scene value is extracted from that URL and can later be used with getOrderStatus to view the item name and order status. The API uses JSON-RPC 2.0, places parameters under params.arguments, and returns success as code: 200.

Boundary: This skill is intended for single-specification orders, order-link generation, and order-status checks in enabled cities. It does not handle refunds, cancellations, logistics tracking, invoices, or other unsupported actions. Keep the user’s own token, avoid committing dgss_token.md, and prefer the Python path on Windows to avoid Chinese parameter encoding issues.