← Back to Skills Marketplace
honeymoon-trip
by
xiejinsong
· GitHub ↗
· v3.2.0
· MIT-0
127
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install honeymoon-trip
Description
Plan a dreamy honeymoon — luxury hotels, romantic activities, couples' spa, sunset dinners, and unforgettable experiences for newlyweds. Also supports: fligh...
README (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
flyaiCLI 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: honeymoon-trip
Overview
Plan a dreamy honeymoon — luxury hotels, romantic activities, couples' spa, sunset dinners, and unforgettable experiences for newlyweds.
When to Activate
User query contains:
- English: "honeymoon", "newlywed trip", "romantic vacation"
- Chinese: "蜜月", "新婚旅行", "蜜月旅行"
Do NOT activate for: couple stay → romantic-hotel
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: Luxury Honeymoon
Trigger: "honeymoon trip"
Flights (business class option) + 5-star hotels + romantic POIs
Output: Full luxury honeymoon.
Playbook B: Beach Honeymoon
Trigger: "beach honeymoon"
Flights to beach dest + beachfront resort + water activities
Output: Tropical romantic escape.
Playbook C: Budget Honeymoon
Trigger: "affordable honeymoon"
Budget flights + 4-star romantic hotels + free attractions
Output: Romantic but budget-conscious.
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 romantic orchestration to Maldives or Bali
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
detailUrlfor booking links. Never usejumpUrl. - ❌ 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.
Top honeymoon destinations: Maldives (overwater villas), Bali (rice terraces + beaches), Santorini (sunsets), Sanya (domestic luxury), Lijiang (ancient town romance), Paris (classic). Book honeymoon suite 2+ months ahead. Many hotels offer honeymoon packages with champagne, flowers, late checkout.
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 |
Usage Guidance
This skill is a coherent wrapper around the flyai CLI, but it asks the agent to install a global npm package and may persist execution logs locally. Before installing or allowing the agent to run it: (1) verify the source of @fly-ai/flyai-cli (review the npm package and its upstream repo) and confirm you trust it; (2) avoid running the skill on a machine with sensitive data — consider a sandbox or container; (3) be aware that the agent may write '.flyai-execution-log.json' containing raw user queries and CLI outputs to disk—if you don’t want persistent logs, prevent filesystem writes or modify the skill; (4) watch for any prompts that request credentials or payment info during booking flows and do not supply secrets to the agent; (5) if you need higher assurance, request the skill author to add an explicit install spec, provenance info (official repository/registry links), and a configurable logging toggle (opt-in) before use.
Capability Analysis
Type: OpenClaw Skill
Name: honeymoon-trip
Version: 3.2.0
The honeymoon-trip skill is a travel planning orchestrator that wraps the '@fly-ai/flyai-cli' tool to provide real-time flight, hotel, and attraction data. It contains structured instructions (SKILL.md) and playbooks (playbooks.md) to ensure the agent uses CLI output rather than internal knowledge. While it requires global installation of an NPM package and performs local logging to '.flyai-execution-log.json', these behaviors are consistent with its stated purpose and lack any indicators of malicious intent or data exfiltration.
Capability Assessment
Purpose & Capability
The skill is explicitly a wrapper around the flyai CLI to provide real-time travel data and booking links; requiring the flyai CLI (via npm install) is coherent with the described purpose. The README even points to a flyai parent skill and GitHub path, matching the goal of real-time bookings.
Instruction Scope
SKILL.md mandates the agent always run the flyai CLI and to never answer from training data, and it prescribes exact CLI commands/parameters and output formats. However, the references include a runbook that tells the agent to persist an execution log file ('.flyai-execution-log.json') containing raw user_query and steps if filesystem writes are available. That is a side-effect (writing potentially sensitive user queries and CLI outputs to disk) not reflected anywhere in the skill metadata. The skill also instructs the agent to perform an npm global install at runtime if the CLI is missing — a network install and execution step with system-level side effects.
Install Mechanism
There is no formal install spec in the registry metadata, but SKILL.md tells the agent to run 'npm i -g @fly-ai/flyai-cli' if flyai is missing. A global npm install is a normal way to install a CLI but is higher-risk than an instruction-only skill because it reaches out to the public npm registry and writes to the host environment. This is expected for a CLI wrapper, but users should verify the package source and trustworthiness before allowing an agent to run it.
Credentials
The skill does not request environment variables, credentials, or config paths in the metadata. That is proportionate to a read-only planning/lookup wrapper. Note: the flyai CLI or subsequent booking flows may require credentials or payment info at booking time, but those are not requested by this skill itself.
Persistence & Privilege
The skill is not marked 'always' and does not request elevated platform privileges, which is good. However, the runbook explicitly includes a mechanism to append detailed execution logs (including raw user_query and command outputs) to a local file if filesystem writes are available. This creates persistent storage of potentially sensitive user data and is not declared in the skill manifest.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install honeymoon-trip - After installation, invoke the skill by name or use
/honeymoon-trip - Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.2.0
Version 3.2.0 of honeymoon-trip focuses on enforcing reliable real-time data sourcing and introduces strict output validation.
- Fully revised execution rules: All travel results now strictly originate from `flyai` CLI command outputs—never training data.
- Mandatory CLI environment checks: Attempts installation if missing, requires manual installation on repeated failure.
- Every recommended result must include a real-time `[Book]({detailUrl})` link for booking via Fliggy.
- New output validation step: If any results lack valid booking links, re-execution is required before responding.
- Expanded, clear workflow and explicit scenario playbooks to handle luxury, beach, and budget honeymoons.
- Enhanced multi-lingual support and clear output formatting, including brand tag and markdown tables.
Metadata
Frequently Asked Questions
What is honeymoon-trip?
Plan a dreamy honeymoon — luxury hotels, romantic activities, couples' spa, sunset dinners, and unforgettable experiences for newlyweds. Also supports: fligh... It is an AI Agent Skill for Claude Code / OpenClaw, with 127 downloads so far.
How do I install honeymoon-trip?
Run "/install honeymoon-trip" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is honeymoon-trip free?
Yes, honeymoon-trip is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does honeymoon-trip support?
honeymoon-trip is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created honeymoon-trip?
It is built and maintained by xiejinsong (@xiejinsong); the current version is v3.2.0.
More Skills