Back to Details

rail

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Rail skill（高铁/火车：时刻表 & 余票 & 晚点）

Rail Skill (High-Speed Rail/Train: Timetable, Ticket Availability, Delays)

心智模型

Mental Model

  • 时刻表 ≠ 余票 ≠ 晚点：这三类信息的实时性和权威来源不同，输出时要明确你查的是哪一类。
  • 余票/晚点是强实时：必须带来源链接和当地更新时间；拿不到就别下结论。
  • 站名/日期是关键：同一城市多个车站；“今天/明天”一定要落到当地日期。
  • Timetable ≠ Ticket Availability ≠ Delays: These three types of information differ in real-time nature and authoritative sources. Clearly specify which type you are querying when outputting results.
  • Ticket availability/delays are highly real-time: Must include source link + local update time; do not draw conclusions if you cannot obtain this information.
  • Station names/dates are critical: A city may have multiple stations; "today/tomorrow" must be converted to a specific local date.

只问 1 个关键问题（仅在必要时）

Ask Only 1 Key Question (Only When Necessary)

缺关键信息时只问一个：
  • 缺日期： “你查 哪天（当地日期） 的车？”
  • 站名不清： “你从哪个站出发、到哪个站？（例如 深圳北 → 广州南）”
  • 目标不清（时刻表/余票/晚点）： “你要看 时刻表、余票 还是 晚点/停运？”
When key information is missing, ask only one question:
  • Missing date: "Which date (local date) are you inquiring about?"
  • Unclear station names: "Which departure station and arrival station are you referring to? (e.g., Shenzhen North → Guangzhou South)"
  • Unclear query goal (timetable/ticket availability/delays): "Do you want to check the timetable, ticket availability, or delays/cancellations?"

输出硬要求（强约束）

Hard Output Requirements (Strict Constraints)

必须包含：
  • 类型：时刻表 / 余票 / 晚点 / 停运
  • 出发站 → 到达站 + 日期（当地日期）
  • 车次（如果用户提供或来源给出）
  • 来源 + 链接
  • 当地时间（来源页面的更新时间/发布时间；拿不到就写“来源未标注”）
建议格式（Markdown）：
  • 深圳北 → 广州南（YYYY-MM-DD）余票/时刻表/晚点（来源：xxx；当地时间：YYYY-MM-DD HH:mm / 来源未标注）
    • 结果：最关键一两条（不要刷屏）
Must include:
  • Type: Timetable / Ticket Availability / Delays / Cancellations
  • Departure Station → Arrival Station + Date (local date)
  • Train number (if provided by user or available from source)
  • Source + Link
  • Local Time (update/publish time of the source page; write "Source does not indicate update time" if unavailable)
Recommended Format (Markdown):
  • Shenzhen North → Guangzhou South (YYYY-MM-DD) Ticket Availability/Timetable/Delays (Source: xxx; Local Time: YYYY-MM-DD HH:mm / Source does not indicate update time)
    • Result: 1-2 key pieces of information (avoid information overload)

来源策略（中国为主）

Source Strategy (China-Focused)

白名单（用于下结论）

Whitelist (For Drawing Conclusions)

  • 12306.cn
    （官方售票/查询渠道；用于余票、正点/停运信息、权威时刻）
  • 12306.cn
    (official ticketing/inquiry channel; used for ticket availability, on-time/cancellation information, authoritative timetables)

余票查询优先链路（首选 12306 深链）

Priority Link for Ticket Availability Inquiry (Prefer 12306 Deep Links)

当用户问 余票/票价/可买性 时，不要把“去某个链接自己看”当成答案。应当你自己先查到结果，再把结果 + 来源一起给用户；其中 12306 必须优先。
执行方式（在技能内约束，不依赖自定义工具）：
  • 先打开 12306 深链页（
    leftTicket/init
    或 
    lcQuery/init
    ），在页面上完成查询/读取结果（必要时用网页阅读/浏览器工具提取列表内容）。
  • 把关键结果整理成 2~5 条即可（车次/出发到达/历时/余票），避免刷屏。
  • 输出时必须带对应的 12306 深链（用户可复核），并写清楚你查询的北京时间（若页面未标注更新时间，就写“以查询时刻为准”）。
来源链接（作为引用/复核，而不是让用户代查）：
  • 直达余票/车次列表（leftTicket）：
    • 模板：
      https://kyfw.12306.cn/otn/leftTicket/init?linktypeid=dc&fs=<出发站名>,<出发站码>&ts=<到达站名>,<到达站码>&date=<YYYY-MM-DD>&flag=N,N,Y
    • 示例：
      https://kyfw.12306.cn/otn/leftTicket/init?linktypeid=dc&fs=江门,JOQ&ts=深圳北,IOQ&date=2026-01-19&flag=N,N,Y
  • 中转换乘查询（lcQuery）（用户明确要“换乘/中转”、或直达结果不理想时优先给这个）：
    • 模板：
      https://kyfw.12306.cn/otn/lcQuery/init?linktypeid=dc&fs=<出发站名>,<出发站码>&ts=<到达站名>,<到达站码>&date=<YYYY-MM-DD>&flag=N,N,Y
    • 示例：
      https://kyfw.12306.cn/otn/lcQuery/init?linktypeid=dc&fs=江门,JOQ&ts=深圳北,IOQ&date=2026-01-19&flag=N,N,Y
使用要点：
  • 站码必须是 12306 站码（如 
    深圳北=IOQ
    ）。若用户只给站名，先用 12306 官方站名码表确认站码；站名有歧义（同城多站/旧站名）就先问清再生成深链。
  • 更新时间写法：12306 余票列表页通常不单独标注“更新时间”，此时在输出中写：
    以查询时刻为准（北京时间 YYYY-MM-DD HH:mm）
    ，并明确“页面未标注更新时间”。
  • 结论约束：即使第三方页面显示余票/票价，也只能作为辅助；最终结论必须以该 12306 深链页（或等价官方查询页）为准。
  • 例外处理（仅在不可抗力时）：若 12306 触发验证码/风控导致无法读取数据，必须明确说明“我现在无法在这里直接取到实时余票”，并给出 12306 深链作为备选复核路径（同时不要编造任何余票结论）。
When users ask about ticket availability/fare/purchase possibility, do not just tell users to "check the link themselves". You should first retrieve the results, then provide the results along with the source; 12306 must be prioritized.
Implementation (Constrained within the skill, no custom tools required):
  • First open the 12306 deep link page (
    leftTicket/init
    or 
    lcQuery/init
    ), complete the query/extract results on the page (use web reading/browser tools to extract list content if necessary).
  • Organize key results into 2-5 items (train number, departure/arrival time, duration, ticket availability) to avoid information overload.
  • Must include the corresponding 12306 deep link (for user verification) in the output, and clearly state the Beijing time of your query (if the page does not indicate update time, write "Subject to query time").
Source Links (For reference/verification, not for user to check on your behalf):
  • Direct Ticket Availability/Train List (leftTicket):
    • Template: 
      https://kyfw.12306.cn/otn/leftTicket/init?linktypeid=dc&fs=<Departure Station Name>,<Departure Station Code>&ts=<Arrival Station Name>,<Arrival Station Code>&date=<YYYY-MM-DD>&flag=N,N,Y
    • Example: 
      https://kyfw.12306.cn/otn/leftTicket/init?linktypeid=dc&fs=江门,JOQ&ts=深圳北,IOQ&date=2026-01-19&flag=N,N,Y
  • Transfer Inquiry (lcQuery) (Prioritize this when user explicitly requests "transfer" or direct results are unsatisfactory):
    • Template: 
      https://kyfw.12306.cn/otn/lcQuery/init?linktypeid=dc&fs=<Departure Station Name>,<Departure Station Code>&ts=<Arrival Station Name>,<Arrival Station Code>&date=<YYYY-MM-DD>&flag=N,N,Y
    • Example: 
      https://kyfw.12306.cn/otn/lcQuery/init?linktypeid=dc&fs=江门,JOQ&ts=深圳北,IOQ&date=2026-01-19&flag=N,N,Y
Usage Notes:
  • Station codes must be official 12306 codes (e.g., 
    Shenzhen North=IOQ
    ). If the user only provides station names, first confirm the code using the official 12306 station code list; if the station name is ambiguous (multiple stations in the same city/old name), clarify with the user before generating the deep link.
  • Update Time Format: The 12306 ticket availability list page usually does not separately indicate "update time". In this case, write in the output: 
    Subject to query time (Beijing Time YYYY-MM-DD HH:mm)
    and clearly state "Page does not indicate update time".
  • Conclusion Constraint: Even if third-party pages show ticket availability/fare, they can only be used as supplementary references; the final conclusion must be based on the 12306 deep link page (or equivalent official inquiry page).
  • Exception Handling (Only in Force Majeure Cases): If 12306 triggers a captcha/risk control that prevents data retrieval, clearly state "I cannot directly obtain real-time ticket availability here at the moment", provide the 12306 deep link as an alternative verification path, and do not fabricate any ticket availability conclusions.

全网（仅作补证/交叉验证）

Entire Web (Only for Supplementary Verification/Cross-Validation)

  • 第三方站点可用于辅助检索/引导，但余票与停运/晚点类结论必须回到官方或等价权威来源。
  • Third-party sites can be used for auxiliary retrieval/guidance, but conclusions on ticket availability, cancellations, or delays must be based on official or equivalent authoritative sources.

NEVER（绝对禁止）

NEVER (Absolutely Forbidden)

  • 不要编造余票数量、票价、晚点分钟数、停运信息
  • 不要把历史时刻表当作当天运行情况
  • 不要在没确认日期/站点时就输出具体车次与时间
  • Do not fabricate ticket quantities, fares, delay minutes, or cancellation information
  • Do not use historical timetables as the current day's operation status
  • Do not output specific train numbers and times without confirming the date/station",