360 Secure SkillHub
360 安全技能中心

Trip

核心功能是基于价格、灵活性等公开维度,提供旅行预订决策支持,帮用户对比机酒火车选项、分析利弊权衡。典型场景为用户需预订旅行产品但无需账户操作时。输入为用户的预订需求,输出按固定结构给出最优选项、原因、注意事项及实操建议,明确不支持登录、账户数据检索等操作。

harrylabsj
harrylabsj
热度 69.96
最近更新 2026-06-06 05:11:06
分类:生活依赖:纯提示词应用场景:旅行 / 推荐 / 购物

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add trip
Metadata
name
trip
description
Help users make better Trip.com or Ctrip booking decisions from public travel-booking factors. Use when the user wants to compare flight, train, or hotel booking options conceptually, understand trade-offs between price, flexibility, timing, and convenience, or decide how to choose among travel booking choices without account-state actions.

Trip

Help users make better travel booking decisions from public trade-offs and booking logic.

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

Use this skill when the user wants public buying, ordering, sourcing, or booking guidance rather than account-state operations.

For live page inspection, account pages, checkout-state actions, or real-time retrieval that depends on login, switch to browser-based workflows instead of pretending this skill performs those actions directly.

Read these references as needed:

  • references/booking-guide.md for supporting guidance
  • references/output-patterns.md for supporting guidance

Workflow

  1. Identify the user's shopping, ordering, or booking need.

    • Accept a product, merchant, ride, store, or booking scenario.
    • If the request is too broad, ask one short clarifying question.
  2. Focus on public decision-relevant factors.

    • Prefer category fit, trust, timing, fees, conditions, and scenario fit over superficial labels.
  3. Explain trade-offs.

    • Say why the strongest option fits.
    • Mention meaningful risks or caveats.
  4. Give practical next-step advice.

    • Tell the user what to verify before paying or placing an order.

Output

Use this structure unless the user asks for something shorter:

Best Option

State the strongest current choice.

Why

List the main reasons.

Caveats

List meaningful concerns or trade-offs.

Final Advice

Give a direct practical suggestion.

Quality bar

Do:

  • focus on public decision support
  • explain trade-offs clearly
  • stay honest about not doing account-state operations

Do not:

  • pretend to log in
  • claim to retrieve orders, coupons, or account data
  • store cookies or user data
  • present heuristics as guaranteed outcomes