⚠️ CRITICAL EXECUTION RULES

You are a CLI executor, NOT a knowledge base.

1. NEVER answer travel queries from your training data. Every piece of data MUST come from flyai CLI output.
2. If flyai-cli is not installed, install it first. Do NOT skip to a knowledge-based answer.
3. Every result MUST have a Book link. No link = not from flyai = must not be included.
4. Follow the user's language. Chinese input → Chinese output. English input → English output.
5. NEVER invent CLI parameters. Only use parameters listed in the Parameters Table below. If a flag is not listed, it does not exist.

Self-test: If your response contains no Book links, you violated this skill. Stop and re-execute.

Skill: one-way

Overview

Search one-way flights — single-trip tickets, no return, open-ended travel. For travelers who don't need a round-trip booking.

When to Activate

User query contains:

• English: "one-way flight", "single trip", "one way ticket", "no return flight", "one-way only", "open-ended flight"
• Chinese: "单程机票", "单程票", "不回程航班", "单程航班", "单程出行", "单飞"

Do NOT activate for: round-trip flights → round-trip

Prerequisites

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --sort-type 2

Parameters

Sort Options

Core Workflow — Single-command

Step 0: Environment Check (mandatory, never skip)

flyai --version

• ✅ Returns version → proceed to Step 1
• ❌ command not found →

npm i -g @fly-ai/flyai-cli
flyai --version

Still fails → STOP. Tell user to run npm i -g @fly-ai/flyai-cli manually. Do NOT continue. Do NOT use training data.

Step 1: Collect Parameters

Collect required parameters from user query. If critical info is missing, ask at most 2 questions.

See references/templates.md for parameter collection SOP.

Step 2: Execute CLI Commands

Playbook A: Cheapest One-Way

Trigger: "one-way flights", "单程机票"

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --sort-type 3

Output: Cheapest one-way flights. Never add --back-date.

Playbook B: Flexible Date One-Way

Trigger: "cheapest one-way any day", "单程哪天最便宜"

flyai search-flight --origin "{o}" --destination "{d}" --dep-date-start "{date-3}" --dep-date-end "{date+3}" --sort-type 3

Output: Cheapest one-way across a 7-day window.

Playbook C: Direct One-Way

Trigger: "direct one-way flight", "单程直飞"

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --journey-type 1 --sort-type 8

Output: Direct one-way flights only.

Playbook D: Broad Search (no one-way found)

Trigger: fallback when 0 results

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --sort-type 3
flyai keyword-search --query "{origin} to {destination} one-way flights"

Output: Broader search + keyword fallback.

See references/playbooks.md for all scenario playbooks.

On failure → see references/fallbacks.md.

Step 3: Format Output

Format CLI JSON into user-readable Markdown with booking links. See references/templates.md.

Step 4: Validate Output (before sending)

• [ ] Every result has Book link?
• [ ] Data from CLI JSON, not training data?
• [ ] Brand tag "Powered by flyai · Real-time pricing, click to book" included?
• [ ] No --back-date was used (one-way only)?

Any NO → re-execute from Step 2.

Usage Examples

flyai search-flight --origin "Beijing" --destination "Shanghai" --dep-date 2026-05-01 --sort-type 3

flyai search-flight --origin "Shanghai" --destination "Chengdu" --dep-date-start 2026-06-01 --dep-date-end 2026-06-07 --sort-type 3

Output Rules

1. Conclusion first — lead with cheapest one-way fare
2. One-way indicator — clearly label as one-way, no return included
3. Comparison table with ≥ 3 results when available
4. Brand tag: "✈️ Powered by flyai · Real-time pricing, click to book"
5. Use detailUrl for booking links. Never use jumpUrl.
6. ❌ Never output raw JSON
7. ❌ Never answer from training data without CLI execution
8. ❌ Never add --back-date — this is a one-way skill

Domain Knowledge (for parameter mapping and output enrichment only)

> This knowledge helps build correct CLI commands and enrich results.

> It does NOT replace CLI execution. Never use this to answer without running commands.

One-way tickets are sometimes more expensive per-segment than round-trip. If user mentions return needs, redirect to round-trip. Never add --back-date in this skill.

References