Snack Supermarket

Problem

This skill targets a narrow snack-only purchase flow: it removes manual API handling and prevents general assistants from drifting into cake, flower, or dessert categories that are not supported. It keeps the pre-order state limited to token, city, address, and keyword, then produces a payable link.

How It Works

• Credentials and address: reads or writes local dgss_token.md to confirm user_token, default_city, and default_aid; uses getAddrList or addAddrList when address data is missing.
• Product search: locks the snack category to cat_id=5, calls snacks_sweets_lst, and displays fixed columns such as brand, name, spec, and price.
• Checkout and lookup: after choosing one spec_id and quantity, calls getOrderaddr to generate a payment URL; extracts the scene=... order identifier and can check status via getOrderStatus.

Boundaries

It only supports snack ordering, and explicitly rejects cakes, flowers, desserts, refunds, tracking, and invoices. The token file should stay local, responses are nested JSON, and address fields use area and addr rather than common aliases.