Skill: liquanyu123/wedding-flight (version 3.2.0)

--- name: wedding-flight displayName: "Wedding Flight — Honeymoon Travel, Wedding Guest Flights, Ceremony Trip Booking" description: "Book wedding and honeymoon flights with flexible date ranges and seat class options. 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: wedding-flight ## Overview Wedding and honeymoon flights — ceremony travel, guest flights, honeymoon getaways. For couples planning wedding-related travel. ## When to Activate User query contains: - English: "wedding flight", "honeymoon flight", "wedding travel", "ceremony flight", "bridal trip" - Chinese: "婚礼航班", "蜜月机票", "婚庆出行", "结婚旅行", "蜜月旅行" Do NOT activate for: couple romantic stays → `couple-romantic-stay`; anniversary trips → `anniversary` ## Prerequisites ```bash npm i -g @fly-ai/flyai-cli ``` ```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 | | `--destination` | Yes | Arrival city or airport code | | `--dep-date` | No | Departure date, `YYYY-MM-DD` | | `--sort-type` | No | **Default: 2** (recommended) | | `--seat-class-name` | No | economy/business (default: economy, honeymoon suggests business) | | `--journey-type` | No | 1=direct (default for honeymoon), 2=connecting | | `--max-price` | No | Price ceiling in CNY | | `--dep-date-start` | No | Wedding season window start | | `--dep-date-end` | No | Wedding season window end | ## Core Workflow — Single-command ### Step 0: Environment Check (mandatory, never skip) ```bash flyai --version ``` - ✅ Returns version → proceed - ❌ `command not found` → install flyai-cli first ### 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: Honeymoon Flight **Trigger:** "honeymoon flight", "蜜月机票" ```bash flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --journey-type 1 --sort-type 2 ``` ### Playbook B: Wedding Guest Group Search **Trigger:** "wedding guest flight", "婚礼航班" ```bash flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --seat-class-name economy --sort-type 2 ``` ### Playbook C: Flexible Date Honeymoon **Trigger:** "honeymoon flexible dates", "蜜月旅行随便哪天" ```bash flyai search-flight --origin "{o}" --destination "{d}" --dep-date-start {start} --dep-date-end {end} --journey-type 1 --sort-type 2 ``` ### Playbook D: Broad Search **Trigger:** 0 results from above. ```bash flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --sort-type 2 flyai keyword-search --query "{origin} to {destination} wedding honeymoon flights" ``` See [references/playbooks.md](references/playbooks.md). On failure → see [references/fallbacks.md](references/fallbacks.md). ### Step 3: Format Output 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 included? ## Usage Examples ```bash flyai search-flight --origin "Shanghai" --destination "Maldives" --dep-date-start 2026-05-01 --dep-date-end 2026-05-31 --journey-type 1 --sort-type 2 ``` ## Output Rules 1. **Conclusion first** — lead with best-rated option (recommended priority) 2. **Wedding tip** — note popular honeymoon destinations and seasonal pricing 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 ## Domain Knowledge (for parameter mapping and output enrichment only) > This knowledge does NOT replace CLI execution. Never use this to answer without running commands. | User Query | CLI Parameter Mapping | |------------|----------------------| | "honeymoon flight" / "蜜月机票" | `--journey-type 1 --sort-type 2` | | "wedding guest" / "婚礼航班" | `--seat-class-name economy --sort-type 2` | | "bridal trip business" / "蜜月商务舱" | `--seat-class-name business --journey-type 1 --sort-type 2` | Popular honeymoon destinations: Maldives, Bali, Santorini, Sanya, Okinawa. Peak wedding seasons: May-June, September-October. ## 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 |


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)