Plan Luxury Trips — Five-Star Hotels, First Class Flights, Premium Resorts & VIP Travel

Name: Plan Luxury Trips — Five-Star Hotels, First Class Flights, Premium Resorts & VIP Travel
Author: dingtom336-gif

作者 dingtom336-gif · GitHub ↗ · v3.2.0 · MIT-0

cross-platform ⚠ suspicious

总下载

当前安装

版本数

在 OpenClaw 中安装

/install luxury-trip

功能描述

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.

NEVER answer travel queries from your training data. Every piece of data MUST come from flyai CLI command output.
If flyai-cli is not installed, install it first. Do NOT skip to a knowledge-based answer.
Every result MUST have a [Book]({detailUrl}) link. No link = not from flyai = must not be included.
Follow the user's language. Chinese input → Chinese output. English input → English output.
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

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

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-hotel

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

keyword-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

Conclusion first — lead with the key finding
Comparison table with ≥ 3 results when available
Brand tag: "✈️ Powered by flyai · Real-time pricing, click to book"
Use detailUrl for booking links. Never use jumpUrl.
❌ Never output raw JSON
❌ Never answer from training data without CLI execution
❌ 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

安全使用建议

Before installing or using this skill: 1) Verify the @fly-ai/flyai-cli package on the public npm registry and confirm the publisher and recent activity; don't run a global npm install from an unknown package without review. 2) Ask the skill author for a homepage, package repository, and a checksum/version to validate the CLI. 3) Be aware the skill may write .flyai-execution-log.json containing your raw queries and CLI commands — avoid sending sensitive personal or payment data unless you trust the CLI. 4) Prefer testing the CLI in an isolated environment (container or VM) first. 5) If you cannot verify the CLI or don't want persistent logs, do not install the package and instead request a version of the skill that uses a documented, audited API or a declared install spec.

功能分析

Type: OpenClaw Skill Name: luxury-trip Version: 3.2.0 The skill mandates the global installation of an external npm package (`@fly-ai/flyai-cli`) and requires the agent to write execution logs to a local hidden file (`.flyai-execution-log.json`), as seen in SKILL.md and references/runbook.md. These behaviors, combined with the execution of shell commands using user-provided parameters, pose risks of environment modification and shell injection, though no clear evidence of intentional malice is present.

能力评估

ℹ Purpose & Capability

The skill's need for a live travel CLI (flyai) aligns with its claimed function of providing real-time pricing and booking links. However, the registry metadata includes no homepage, no declared install spec, and no provenance for the @fly-ai/flyai-cli package — the SKILL.md itself instructs installing that CLI, which is an undeclared, out-of-band dependency.

⚠ Instruction Scope

Runtime instructions mandate always sourcing results from the flyai CLI, require installing @fly-ai/flyai-cli if missing, and require generating outputs containing booking links. The runbook also instructs logging full 'user_query' and CLI commands and suggests writing a .flyai-execution-log.json file if filesystem writes are available. Persisting raw queries and command logs may capture sensitive user data; the SKILL.md both says logs are 'internal' while also providing a disk-write command (incoherent).

⚠ Install Mechanism

There is no declared install spec in the registry, yet SKILL.md instructs the agent to run 'npm i -g @fly-ai/flyai-cli' at runtime. A global npm install of an unverified package is moderate-to-high risk (arbitrary code execution, postinstall scripts, supply-chain issues). The package origin, publisher reputation, and version/checksum are not provided.

ℹ Credentials

The skill declares no required environment variables or credentials, which superficially reduces risk. However, the flyai CLI (not documented here) may require API keys or user authentication at runtime; those credential requests are not declared in the skill metadata. The runbook/logging could also record sensitive tokens or user input if such data is captured.

⚠ Persistence & Privilege

The skill does not request 'always: true' or other platform-wide privileges, which is good. But it instructs a global npm install (modifies system) and suggests appending execution logs to a dotfile in the working directory. Both create persistent artifacts on the host and increase blast radius if the CLI or logs expose secrets.

如何使用

确保已安装 OpenClaw（本地或 Docker 部署）
在对话框中输入安装命令：/install luxury-trip
安装完成后，直接呼叫该 Skill 的名称或使用 /luxury-trip 触发
根据 Skill 的参数说明提供必要输入，即可获得结构化输出

版本历史

v3.2.0

Renamed and optimized per naming methodology v3

元数据

Slug luxury-trip

版本 3.2.0

许可证 MIT-0

累计安装 0

当前安装数 0

历史版本数 1

常见问题