SkillHub

meituan

v1.1.0

Help users make better Meituan ordering decisions from public merchant and delivery information. Use when the user wants to compare Meituan restaurants, judge whether a delivery offer is worth it, understand delivery fee, minimum order, estimated time, discount conditions, or choose between stores f...

Sourced from ClawHub, Authored by haidong

Installation

Please help me install the skill `meituan` from SkillHub official store. npx skills add harrylabsj/meituan

Meituan

Help users make better Meituan ordering decisions from public merchant and promotion information.

This is a low-sensitivity public skill. It focuses on public-page decision support and does not perform login, coupon claiming, order retrieval, cookie handling, account access, or local database persistence.

Use this skill when the user wants to: - compare Meituan restaurants or stores - understand whether a delivery offer is worth it - judge delivery fee, minimum order, delivery time, and promotion conditions - choose between stores for one-person, two-person, or group ordering

For public live-page inspection, pair it with browser-based workflows. For account pages, orders, red packets, addresses, or login-state actions, do not treat this skill as the tool for that work.

Read these references as needed: - references/comparison-guide.md for merchant comparison logic - references/promotion-judgment.md for discount and fee interpretation - references/risk-signals.md for common takeout decision risks - references/output-patterns.md for final answer structure

Workflow

  1. Identify the ordering need.
  2. Accept a store, dish type, ordering scenario, or comparison request.
  3. If the request is too broad, ask one short clarifying question.

  4. Focus on decision-relevant public signals. Compare factors such as:

  5. delivery fee
  6. minimum order
  7. estimated delivery time
  8. platform discount and store discount conditions
  9. rating and sales context
  10. dish pricing and order threshold fit

  11. Explain trade-offs.

  12. A lower displayed price may still be worse if delivery fee is high.
  13. A stronger discount may still be worse if the threshold is unrealistic.
  14. A higher-rated store may still be worse if delivery time or basket fit is poor.

  15. Give practical ordering advice.

  16. Say which store looks better for the user’s scenario.
  17. Mention what the user should verify before placing the order.

Output

Use this structure unless the user asks for something shorter:

Best Option

State the strongest current choice for the user’s scenario.

Why

List the main reasons.

Comparison Factors

Summarize the most important fields, such as delivery fee, minimum order, time, discount, and fit.

Risks or Caveats

List meaningful concerns, such as weak discount conditions, high delivery fee, long wait time, or low-value bundle traps.

Final Advice

Give a direct ordering suggestion in plain language.

Quality bar

Do: - focus on public merchant and promotion signals - explain trade-offs clearly - optimize for the user’s actual ordering scenario - warn when a discount looks attractive but is not actually cost-effective

Do not: - pretend to log in or inspect account-only pages - claim to retrieve orders, coupons, or red packets - store cookies or account data - present public-page heuristics as guaranteed outcomes