Weiduomei Cake Ordering Assistant

Problem Addressed

This skill turns the “order a Weiduomei cake” workflow into a stable API chain: the user provides a user_token, city, and keyword, while the skill handles address confirmation, cake search, order-link generation, and order-status lookup, reducing issues like inconsistent city names, mismatched address fields, spec_id mismatches, and later scene-based status checks.

How It Works

It calls a fixed endpoint using JSON-RPC 2.0, with arguments under params.arguments; success is indicated by code: 200, and the business JSON {code, data, msg} is parsed from result.content[0].text.

• Token handling: the current user supplies user_token, stored in dgss_token.md; add that file to .gitignore before publishing.
• Address handling: normalize the city to the “municipality” level, call getAddrList; if missing, collect province, city, area, addr, name, and phone number, call addAddrList, and use data[0].id as aid.
• Product search: call brand_sweets_lst with fixed cat_id: 1, support pagination, and use “Weiduomei” as keyword for ambiguous requests.
• Ordering and lookup: call getOrderaddr to generate the URL and extract scene; use getOrderStatus for status checks.

The cake table must keep No., Brand, Product Name, Specification, Price, Details, and interface fields should be shown as returned; verify spec_id against the displayed specification before ordering, and only one spec_id is supported.

Boundaries

• Supports Weiduomei-related products only, not other brands, snacks, or flowers.
• Easy-to-confuse fields: district is area, detailed address is addr, address ID is aid.
• Do not expose endpoint names, domains, internal fields, or raw errors; use friendly error messages.
• Windows recommends Python-script invocation; Linux and macOS can use direct commands to avoid Chinese encoding issues.