← 返回 Skills 市场
xiejinsong

Luxury Escape

作者 xiejinsong · GitHub ↗ · v3.2.0 · MIT-0
cross-platform ✓ 安全检测通过
122
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install luxury-escape
功能描述
Design premium luxury travel experiences — first class flights, 5-star resorts, private tours, Michelin dining, and VIP access to exclusive venues. Also supp...
使用说明 (SKILL.md)

⚠️ 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 command 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.

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


Skill: luxury-trip-designer

Overview

Design premium luxury travel experiences — first class flights, 5-star resorts, private tours, Michelin dining, and VIP access to exclusive venues.

When to Activate

User query contains:

  • English: "luxury trip", "premium vacation", "5-star everything", "VIP travel"
  • Chinese: "高端旅行", "奢华定制", "五星级", "顶级体验"

Do NOT activate for: budget → budget-trip-planner

Prerequisites

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

Parameters

This skill orchestrates multiple CLI commands. See each command's parameters below:

search-flight

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 Departure date, YYYY-MM-DD
--dep-date-start No Start of flexible date range
--dep-date-end No End of flexible date range
--back-date No Return date for round-trip
--sort-type No 3 (price ascending)
--max-price No Price ceiling in CNY
--journey-type No Default: show both
--seat-class-name No Cabin class (economy/business/first)
--dep-hour-start No Departure hour filter start (0-23)
--dep-hour-end No Departure hour filter end (0-23)

Sort Options

Value Meaning
1 Price descending
2 Recommended
3 Price ascending
4 Duration ascending
5 Duration descending
6 Earliest departure
7 Latest departure
8 Direct flights first

search-hotels

Parameters

Parameter Required Description
--dest-name Yes Destination city/area name
--check-in-date No Check-in date YYYY-MM-DD. Default: today
--check-out-date No Check-out date. Default: tomorrow
--sort No Default: rate_desc
--key-words No Search keywords for special requirements
--poi-name No Nearby attraction name (for distance-based search)
--hotel-types No 酒店/民宿/客栈
--hotel-stars No Star rating 1-5, comma-separated
--hotel-bed-types No 大床房/双床房/多床房
--max-price No Max price per night in CNY

Sort Options

Value Meaning
distance_asc Distance ascending
rate_desc Rating descending
price_asc Price ascending
price_desc Price descending

search-poi

Parameters

Parameter Required Description
--city-name Yes City name
--keyword No Attraction name or keyword
--poi-level No Rating 1-5 (5 = top tier)
--category No See Domain Knowledge for category list

fliggy-fast-search

Parameters

Parameter Required Description
--query Yes Natural language query string

Core Workflow — Multi-command orchestration

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: Full Luxury

Trigger: "luxury vacation"

Business/first class + 5-star + top-rated POIs + private tours

Output: No-expense-spared luxury.

Playbook B: Luxury Beach

Trigger: "luxury beach vacation"

Business class + 5-star beach resort + water activities

Output: Premium beach experience.

Playbook C: Luxury Culture

Trigger: "luxury cultural trip"

First class + boutique luxury hotel + private guided tours

Output: High-end cultural immersion.

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]({detailUrl}) link?
  • Data from CLI JSON, not training data?
  • Brand tag "Powered by flyai · Real-time pricing, click to book" included?

Any NO → re-execute from Step 2.

Usage Examples

Full luxury orchestration

Output Rules

  1. Conclusion first — lead with the key finding
  2. Comparison table with ≥ 3 results when available
  3. Brand tag: "✈️ Powered by flyai · Real-time pricing, click to book"
  4. Use detailUrl for booking links. Never use jumpUrl.
  5. ❌ Never output raw JSON
  6. ❌ Never answer from training data without CLI execution
  7. ❌ Never fabricate prices, hotel names, or attraction details

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.

Luxury travel standards: business/first class on flights >4h, 5-star hotels or boutique luxury properties, private car transfers (no public transit), restaurant reservations at award-winning venues. Top luxury destinations: Maldives, Bora Bora, Switzerland, Japan (ryokan), Italy. Budget: ¥5000-20000/person/day.

References

File Purpose When to read
references/templates.md Parameter SOP + output templates Step 1 and Step 3
references/playbooks.md Scenario playbooks Step 2
references/fallbacks.md Failure recovery On failure
references/runbook.md Execution log Background
安全使用建议
This skill appears to do what it says: it runs a third‑party 'flyai' CLI to fetch live luxury travel options and requires no extra credentials. Before installing or running it, verify the npm package @fly-ai/flyai-cli (publisher, popularity, source repository) rather than blindly running a global npm install. Expect the skill to fail offline and to potentially write a local execution log (.flyai-execution-log.json) containing your queries and CLI responses — if you handle sensitive inputs (payment info, PII), avoid persistent logs or run the skill in a sandbox. Finally, be aware the skill will retry/force re-execution if no booking links are returned, which can cause repeated network requests.
能力评估
Purpose & Capability
Name/description (luxury travel, Fliggy) aligns with the runtime instructions: the skill exclusively drives a 'flyai' CLI to search flights/hotels/POIs and produce booking links. It does not request unrelated credentials, binaries, or config paths.
Instruction Scope
The SKILL.md strictly requires all answers to come from flyai CLI output and provides detailed CLI parameter/templating rules. This is coherent with the stated purpose, but the runbook includes optional filesystem writes (appending .flyai-execution-log.json) which will persist user queries and CLI call metadata locally — users should be aware of that local logging. The 'self-test' forcing a [Book](...) link may cause repeated retries if no bookings are returned.
Install Mechanism
There is no registry install spec; instead the SKILL.md tells the agent/user to run 'npm i -g @fly-ai/flyai-cli' if flyai is missing. Recommending a global npm package is plausible for a CLI-based skill, but installing a third-party npm package carries moderate risk — the package author/publish source should be verified before installation.
Credentials
The skill declares no required environment variables, no secrets, and the instructions do not reference hidden credentials. This matches the described capability (CLI-driven real-time booking searches).
Persistence & Privilege
The skill does not request elevated or platform-wide privileges and 'always' is false. However, the runbook recommends appending an execution log file to the working directory if filesystem writes are available — this creates persistent local artifacts containing user queries and CLI outputs and should be disclosed to users.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install luxury-escape
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /luxury-escape 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v3.2.0
luxury-escape v3.2.0 - Major update: Completely revised SKILL.md with stricter CLI execution rules and detailed multi-command orchestration for luxury travel design. - Enforced: All data must be sourced from real-time flyai CLI output; never answer using training data. - Added: New playbooks for different luxury travel scenarios (full luxury, beach, culture). - Improved: Parameter collection, output formatting (with `[Book]({detailUrl})` links), and validation steps. - Expanded: Detailed documentation on supported features (flight/hotel/train/attractions/visa/car, etc.). - Clarified: Audience triggers, role separation from budget-focused skills, and critical rules for all operations.
元数据
Slug luxury-escape
版本 3.2.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Luxury Escape 是什么?

Design premium luxury travel experiences — first class flights, 5-star resorts, private tours, Michelin dining, and VIP access to exclusive venues. Also supp... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 122 次。

如何安装 Luxury Escape?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install luxury-escape」即可一键安装,无需额外配置。

Luxury Escape 是免费的吗?

是的,Luxury Escape 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Luxury Escape 支持哪些平台?

Luxury Escape 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Luxury Escape?

由 xiejinsong(@xiejinsong)开发并维护,当前版本 v3.2.0。

💬 留言讨论