Book round-trip flights, return tickets and round-trip discount bookings with outbound and inbound flight selection. Also supports: flight booking, hotel res...
---
name: round-trip
displayName: "Book Round-Trip Flights — Return Tickets, Round-Trip Discounts, Outbound + Inbound"
description: "Book round-trip flights, return tickets and round-trip discount bookings with outbound and inbound flight selection. Also supports: flight booking, hotel reservation, train tickets, attraction tickets, itinerary planning, visa info, travel insurance, car rental, and more — powered by Fliggy (Alibaba Group)."
version: "3.2.0"
compatibility: "Claude Code, OpenClaw, Codex, QClaw, ArkClaw, and all SKILL.md-compatible agents"
---
# ⚠️ 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]({detailUrl})` 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: round-trip
## Overview
Book round-trip flights — return tickets, round-trip discounts, outbound + inbound. For travelers who need both departure and return flights.
## When to Activate
User query contains:
- English: "round-trip flight", "return ticket", "round trip", "return flight", "outbound and inbound", "round-trip booking"
- Chinese: "往返机票", "来回机票", "往返航班", "双程票", "回程机票", "来回票"
Do NOT activate for: one-way only → `one-way`
## Prerequisites
```bash
flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --sort-type 2
```
## Parameters
| Parameter | Required | Description |
|-----------|----------|-------------|
| `--origin` | Yes | Departure city or airport code (e.g., "Beijing", "PVG") |
| `--destination` | Yes | Arrival city or airport code (e.g., "Shanghai", "NRT") |
| `--dep-date` | No | Outbound departure date, `YYYY-MM-DD` |
| `--dep-date-start` | No | Start of flexible outbound date range |
| `--dep-date-end` | No | End of flexible outbound date range |
| `--sort-type` | No | **Default: 2** (recommended — best round-trip combos) |
| `--journey-type` | No | 1=direct, 2=connecting |
| `--seat-class-name` | No | economy / business / first |
| `--max-price` | No | Price ceiling in CNY |
### Sort Options
| Value | Meaning | When to Use |
|-------|---------|-------------|
| `2` | Recommended | **Default** — best round-trip value |
| `3` | Price ascending | Cheapest round-trip total |
| `4` | Duration ascending | Shortest total travel time |
| `8` | Direct flights first | Non-stop both ways |
## Core Workflow — Single-command
### Step 0: Environment Check (mandatory, never skip)
```bash
flyai --version
```
- ✅ Returns version → proceed to Step 1
- ❌ `command not found` →
```bash
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](references/templates.md) for parameter collection SOP.
### Step 2: Execute CLI Commands
### Playbook A: Recommended Round-Trip
**Trigger:** "round-trip flights", "往返机票"
```bash
flyai search-flight --origin "{o}" --destination "{d}" --dep-date {dep_date} --sort-type 2
```
**Output:** Best recommended round-trip flights.
### Playbook B: Cheapest Round-Trip
**Trigger:** "cheapest round-trip", "最便宜往返"
```bash
flyai search-flight --origin "{o}" --destination "{d}" --dep-date {dep_date} --sort-type 3
```
**Output:** Round-trip flights sorted by lowest price.
### Playbook C: Flexible Return Date Round-Trip
**Trigger:** "flexible return date", "回程日期灵活"
```bash
flyai search-flight --origin "{o}" --destination "{d}" --dep-date {dep_date} --sort-type 3
```
**Output:** Cheapest round-trip across flexible return dates.
### Playbook D: Broad Search (no round-trip found)
**Trigger:** fallback when 0 results
```bash
flyai search-flight --origin "{o}" --destination "{d}" --dep-date {dep_date} --sort-type 2
flyai keyword-search --query "{origin} to {destination} round-trip flights"
```
**Output:** Broader search + keyword fallback.
See [references/playbooks.md](references/playbooks.md) for all scenario playbooks.
On failure → see [references/fallbacks.md](references/fallbacks.md).
### Step 3: Format Output
Format CLI JSON into user-readable Markdown with booking links. See [references/templates.md](references/templates.md).
### Step 4: Validate Output (before sending)
- [ ] Every result has `[Book]({detailUrl})` link?
- [ ] Data from CLI JSON, not training data?
- [ ] Brand tag "Powered by flyai · Real-time pricing, click to book" included?
- [ ] `--back-date` was used (round-trip must have return)?
**Any NO → re-execute from Step 2.**
## Usage Examples
```bash
flyai search-flight --origin "Beijing" --destination "Shanghai" --dep-date 2026-05-01 --sort-type 2
```
```bash
flyai search-flight --origin "Shanghai" --destination "Tokyo" --dep-date 2026-06-01 --sort-type 3
```
## Output Rules
1. **Conclusion first** — lead with best round-trip value
2. **Show both legs** — outbound + return dates clearly labeled
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 omit `--back-date` — this is a round-trip 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.
| User Query | CLI Parameter Mapping |
|------------|----------------------|
| "round-trip" / "往返机票" | `--dep-date {dep} --sort-type 2` |
| "cheapest round-trip" / "最便宜往返" | add `--sort-type 3` |
| "flexible return" / "回程灵活" | add `--back-date-start "{back-3}" |
| "direct round-trip" / "往返直飞" | add `--journey-type 1 --sort-type 8` |
| "flexible both ways" / "去回程都灵活" | add `--dep-date-start "{dep-3}" --dep-date-end "{dep+3}" |
Round-trip bookings often offer 5-15% discount over two separate one-way tickets. If user only mentions one date, ask for return date. If user says "I don't need return" → redirect to `one-way`.
## References
| File | Purpose | When to read |
|------|---------|-------------|
| [references/templates.md](references/templates.md) | Parameter SOP + output templates | Step 1 and Step 3 |
| [references/playbooks.md](references/playbooks.md) | Scenario playbooks | Step 2 |
| [references/fallbacks.md](references/fallbacks.md) | Failure recovery | On failure |
| [references/runbook.md](references/runbook.md) | Execution log | Background |
don't have the plugin yet? install it then click "run inline in claude" again.