← 返回 Skills 市场
Explore Japan
作者
dingtom336-gif
· GitHub ↗
· v3.2.1
· MIT-0
88
总下载
0
收藏
0
当前安装
2
版本数
在 OpenClaw 中安装
/install explore-japan
功能描述
Your complete Japan travel companion — flights to Tokyo/Osaka/Kyoto, hotels from ryokan to capsule, shrine visits, cherry blossom viewing, ramen tours, JR Pa...
使用说明 (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: explore-japan
Overview
Your complete Japan travel companion — flights to Tokyo/Osaka/Kyoto, hotels from ryokan to capsule, shrine visits, cherry blossom viewing, ramen tours, JR Pass guidance, and visa help.
When to Activate
User query contains:
- English: "Japan", "Tokyo", "Osaka", "Kyoto", "Hokkaido"
- Chinese: "日本", "东京", "大阪", "京都", "北海道", "去日本"
Do NOT activate for: generic 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: Multi-City Japan
Trigger: "Japan trip"
visa check + flights to Tokyo + hotels per city + POIs per city + JR Pass advice
Output: Full Japan itinerary.
Playbook B: Tokyo Only
Trigger: "Tokyo trip"
Flight to NRT/HND + Tokyo hotel + Tokyo POIs
Output: Tokyo-focused trip.
Playbook C: Kansai
Trigger: "Kyoto Osaka"
Flight to KIX + hotels in Kyoto/Osaka + temples/food POIs
Output: Kansai region deep dive.
Playbook D: Hokkaido
Trigger: "Hokkaido trip"
Flight to CTS + Sapporo/Otaru/Niseko hotels + nature/ski POIs
Output: Hokkaido seasonal 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 "Tokyo" --dep-date 2026-04-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.
Japan essentials: visa required for Chinese citizens (single/3yr/5yr). Airports: NRT/HND (Tokyo), KIX (Osaka/Kyoto), CTS (Hokkaido), OKA (Okinawa). JR Pass: 7/14/21-day, worthwhile for multi-city. IC cards (Suica/ICOCA) for local transit. Cherry blossom: late Mar-mid Apr. Autumn foliage: mid Nov-early Dec. Ski: Dec-Mar in Hokkaido/Nagano.
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 enabling this skill:
- Verify the flyai CLI and the skill source: ask the publisher for a homepage or repository link (the skill metadata currently lists no homepage/source). Inspect the @fly-ai/flyai-cli npm page and its GitHub repository (read the code and recent maintainer activity) before running npm i -g.
- Treat global npm installs as potentially dangerous: prefer installing in a sandbox/container or a throwaway VM rather than on a production or sensitive machine.
- Check what credentials the flyai CLI requires (booking/payment flows can ask for account tokens or credit card details). The skill itself doesn't request env vars, but the CLI may.
- Confirm logging behavior: the runbook suggests appending an execution log to .flyai-execution-log.json; decide whether you’re comfortable storing user queries/requests locally and who can read that file.
- If you cannot verify the CLI’s provenance, decline to install the skill or request the skill author to include a verifiable homepage/repo and a non-global install option.
If you want, I can: (1) show how to inspect the npm package and its repository, (2) suggest a safe sandboxed install workflow, or (3) draft questions to ask the skill author to improve provenance and safety.
功能分析
Type: OpenClaw Skill
Name: explore-japan
Version: 3.2.1
The skill mandates the global installation of a third-party NPM package (@fly-ai/flyai-cli) and requires the agent to execute shell commands for all queries, explicitly forbidding the use of internal knowledge. It also includes instructions in references/runbook.md to write execution logs to the local filesystem (.flyai-execution-log.json). While these actions are aligned with the stated purpose of providing real-time travel data via the Fliggy (Alibaba) service, the requirement for high-privilege system modifications and mandatory shell execution constitutes a significant security risk.
能力评估
Purpose & Capability
The name/description match the instructions: the SKILL.md consistently instructs the agent to use the @fly-ai/flyai-cli to fetch flights, hotels, POIs and to include booking links. All commands and playbooks align with a travel companion that delegates to a CLI.
Instruction Scope
The instructions force the agent to be a CLI executor and to never use training data — every output must come from flyai CLI output. It mandates installing the flyai CLI if absent and requires every result include a [Book]({detailUrl}) link. The runbook also instructs logging execution steps and (if filesystem writable) appending logs to .flyai-execution-log.json. These are coherent with the skill's purpose but increase surface area: reliance on an external binary and local logging may capture or surface sensitive data.
Install Mechanism
The skill has no formal install spec but explicitly instructs installing a global npm package (npm i -g @fly-ai/flyai-cli). Installing global npm packages can execute arbitrary code and changes system state. The manifest provides no homepage/source for either the skill or the referenced CLI, so you can't easily verify the package's provenance from the skill metadata alone.
Credentials
The skill declares no required environment variables or credentials (which is proportionate). However, the external CLI it depends on may itself request or use credentials/config files, and the skill's runbook suggests writing logs containing full request & CLI command details — potentially recording user input or identifiers. The skill does not ask for unrelated credentials, which is good.
Persistence & Privilege
always:false and no OS restrictions are reasonable. The runbook's example shows optional persistence (.flyai-execution-log.json) if filesystem writes are available; this is a modest persistence behavior but worth noting because it can store queries and command outputs locally. The skill does not request elevated privileges or modify other skills' configurations.
如何使用
- 确保已安装 OpenClaw（本地或 Docker 部署）
- 在对话框中输入安装命令：
/install explore-japan - 安装完成后，直接呼叫该 Skill 的名称或使用
/explore-japan触发 - 根据 Skill 的参数说明提供必要输入，即可获得结构化输出
版本历史
v3.2.1
Bug fixes and improvements
v3.2.0
**Major rewrite: Strictly enforces real-time Japan travel bookings only from the flyai CLI.**
- Now outputs only real-time flight, hotel, POI, and other Japan travel data powered by the flyai CLI; no training data answers allowed.
- Adds critical CLI parameter rules: never invent or skip CLI queries; always include `[Book]({detailUrl})` links from CLI output.
- Automatically validates that every response contains booking links and is sourced from up-to-date CLI data.
- Expanded step-by-step workflow: checks environment, collects/asks for parameters, orchestrates multi-command playbooks, formats output per strict templates.
- New brand tag requirement: every result includes "✈️ Powered by flyai · Real-time pricing, click to book".
- Greatly improved clarity for users and executors on when and how to activate this Japan travel assistant.
元数据
常见问题
Explore Japan 是什么？
Your complete Japan travel companion — flights to Tokyo/Osaka/Kyoto, hotels from ryokan to capsule, shrine visits, cherry blossom viewing, ramen tours, JR Pa... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 88 次。
如何安装 Explore Japan？
在 OpenClaw 或 Claude Code 对话框中运行命令「/install explore-japan」即可一键安装，无需额外配置。
Explore Japan 是免费的吗？
是的，Explore Japan 完全免费，采用 MIT-0 许可证，可自由下载、安装和使用。
Explore Japan 支持哪些平台？
Explore Japan 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。
谁开发了 Explore Japan？
由 dingtom336-gif（@dingtom336-gif）开发并维护，当前版本 v3.2.1。
推荐 Skills