← Back to Skills Marketplace
Plan Bali Travel — Flights, Hotels, Attractions, Temples, Beaches, Villas & Itineraries
by
xiejinsong
· GitHub ↗
· v3.2.0
· MIT-0
69
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install bali-travel
Description
Plan your Bali dream trip — Ubud rice terraces, Seminyak beach clubs, Uluwatu temple sunsets, Nusa Penida cliffs, and spiritual yoga retreats. Also supports:...
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: bali-travel
Overview
Plan your Bali dream trip — Ubud rice terraces, Seminyak beach clubs, Uluwatu temple sunsets, Nusa Penida cliffs, and spiritual yoga retreats.
When to Activate
User query contains:
- English: "Bali", "Ubud", "Seminyak", "Kuta"
- Chinese: "巴厘岛", "乌布", "库塔"
Do NOT activate for: general SE Asia → explore-southeast-asia
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 Bali
Trigger: "Bali trip"
Flight to DPS + hotels in Ubud/Seminyak + temples/beaches/rice terrace POIs
Output: Complete Bali experience.
Playbook B: Luxury Bali
Trigger: "luxury Bali"
Flight + 5-star villa + private tours
Output: Premium Bali escape.
Playbook C: Adventure Bali
Trigger: "Bali adventure"
Flight + budget stay + surfing/diving/trekking
Output: Active Bali trip.
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
flyai search-flight --origin "Shanghai" --destination "Bali" --dep-date 2026-06-01 --sort-type 3
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.
Bali areas: Ubud (culture, rice terraces, monkey forest), Seminyak (beach clubs, restaurants, shopping), Kuta (budget, surfing), Uluwatu (cliffside temples, sunset), Canggu (digital nomads, surf). Dry season: Apr-Oct (best). Wet: Nov-Mar (afternoon showers, greener). Rent scooter for flexibility. Temple dress code: sarong required.
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 plausibly a travel helper but has a few red flags you should consider before installing or running it:
- The skill requires installing a third-party npm package at runtime (npm i -g @fly-ai/flyai-cli). Verify the package owner, read its npm page and source repository, and confirm it's published by the expected vendor (the description references Fliggy/Alibaba but the package name differs).
- The runbook may write persistent logs to your filesystem (.flyai-execution-log.json). If you care about privacy, run the skill in a sandbox/container or ensure the agent cannot write to your home directory.
- The skill does not declare how bookings/authentication are handled. Expect the CLI to possibly prompt for credentials or to store tokens locally — ask the skill author whether credentials are needed and where they are stored.
- Because the skill forces re-execution until a specific link format appears, it could generate repeated network calls; monitor network activity when first running it.
Recommended actions before proceeding:
- Inspect the @fly-ai/flyai-cli package on npm/GitHub to confirm publisher and code quality.
- Run the CLI installation and initial tests in an isolated environment (container or VM) first.
- Ask the skill author to clarify the Fliggy vs flyai provenance, booking authentication flow, and log retention policy.
- If you cannot verify the CLI origin, do not install the package globally on a production machine.
Capability Analysis
Type: OpenClaw Skill
Name: bali-travel
Version: 3.2.0
The skill requires the agent to automatically install a global NPM package (`@fly-ai/flyai-cli`) and execute shell commands to perform travel searches (SKILL.md, references/fallbacks.md). While these capabilities are aligned with the stated purpose of a travel planner, the automated installation of external software and the reliance on CLI execution represent significant security risks, such as potential supply chain attacks or remote code execution, which warrant a suspicious classification in the absence of verified intent.
Capability Assessment
Purpose & Capability
The skill's stated purpose (Bali travel planning) matches the CLI-driven workflow described (search-flight, search-hotel, search-poi). However the description claims 'Powered by Fliggy (Alibaba Group)' while the runtime tooling is a different package name ('flyai' / @fly-ai/flyai-cli), which is an unexplained mismatch and worth verifying. Requiring a third-party CLI is plausible for this purpose, but the provenance of that CLI is not declared in metadata.
Instruction Scope
SKILL.md mandates installing and running an external npm CLI at runtime, requires that every result come from that CLI (never use training data), and defines a persistent execution log format. The runbook explicitly suggests appending logs to .flyai-execution-log.json if filesystem writes are available — this writes persistent data to the host. The instructions also require strict output rules (every result must include a booking link) and a forced re-execute behavior if those rules aren't met, which could cause repeated network calls. These runtime actions extend beyond simple query-to-result behavior and have privacy/persistence implications.
Install Mechanism
There is no declared install spec in the skill metadata, yet SKILL.md instructs the agent/user to run 'npm i -g @fly-ai/flyai-cli' if flyai is not installed. Installing a global npm package at runtime is a moderate-to-high risk action because it fetches and executes third-party code from the npm registry; the package's origin, publisher, and trustworthiness are not provided. The install instruction being embedded in runtime instructions (not in a vetted install spec) reduces transparency and control.
Credentials
The skill declares no required environment variables or credentials, which is consistent with the metadata. However booking and booking-link creation typically require service credentials or redirects to vendor pages. The skill does not describe how authentication for bookings is handled, whether the flyai CLI will prompt for credentials, or whether any tokens might be stored in the environment or config files. The absence of declared credential requirements is plausible but leaves open questions that should be answered before use.
Persistence & Privilege
The runbook includes a schema for an execution log and explicitly suggests appending such logs to a host file (.flyai-execution-log.json) if filesystem writes are available. This grants the skill the ability to persist user queries, parameters, and command outputs locally. While not 'always:true', the skill does request persistent local writes when possible, which is a meaningful privilege and could contain personal travel data.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install bali-travel - After installation, invoke the skill by name or use
/bali-travel - Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.2.0
Renamed and optimized per naming methodology v3
Metadata
Frequently Asked Questions
What is Plan Bali Travel — Flights, Hotels, Attractions, Temples, Beaches, Villas & Itineraries?
Plan your Bali dream trip — Ubud rice terraces, Seminyak beach clubs, Uluwatu temple sunsets, Nusa Penida cliffs, and spiritual yoga retreats. Also supports:... It is an AI Agent Skill for Claude Code / OpenClaw, with 69 downloads so far.
How do I install Plan Bali Travel — Flights, Hotels, Attractions, Temples, Beaches, Villas & Itineraries?
Run "/install bali-travel" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Plan Bali Travel — Flights, Hotels, Attractions, Temples, Beaches, Villas & Itineraries free?
Yes, Plan Bali Travel — Flights, Hotels, Attractions, Temples, Beaches, Villas & Itineraries is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Plan Bali Travel — Flights, Hotels, Attractions, Temples, Beaches, Villas & Itineraries support?
Plan Bali Travel — Flights, Hotels, Attractions, Temples, Beaches, Villas & Itineraries is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Plan Bali Travel — Flights, Hotels, Attractions, Temples, Beaches, Villas & Itineraries?
It is built and maintained by xiejinsong (@xiejinsong); the current version is v3.2.0.
More Skills