Meituan Errand Ordering Assistant

Problem Addressed

When users say “send this for me”, “pick this up”, “buy this for me”, or “queue for a restaurant”, the challenge is converting fuzzy local errand intent into submittable service parameters: pickup and delivery addresses, purchase address, item or note, phone number, service type, and fee confirmation. This skill targets same-city Meituan errand requests and uses the Meituan open platform APIs to preview and submit orders, not merely search or draft messages.

How It Works

• Scene routing: classifies requests as pickup-delivery, proxy buying, or help tasks, then decides whether two addresses, item fields, or note fields are required.
• Address and phone handling: reads and fuzzy-matches the address book first; falls back to POI search; prefers the phone number explicitly provided in the current session, then an address-book number, or asks for one.
• Parameter construction: maps the request to service parameters using references/params.md, including proxy buying at a specified address or nearby locations.
• Fee preview: displays service type, addresses, item, distance, fee, and expected time using fixed templates; submission requires explicit user confirmation.
• Submission constraints: treats ordering as a real, irreversible transaction; fees over 100 CNY require extra confirmation; after submission, users must complete payment in the Meituan app.

Boundaries

It is intended for mainland China Meituan errand ordering and should not be used for cross-city delivery or when users decline to order. API key configuration and user authorization are required. Phone numbers should be masked in conversation, and final order parameters must come from actual preview API responses rather than hardcoded examples.