← 返回 Skills 市场
xiejinsong

Explore Korea

作者 xiejinsong · GitHub ↗ · v3.2.0 · MIT-0
cross-platform ⚠ suspicious
88
总下载
0
收藏
0
当前安装
2
版本数
在 OpenClaw 中安装
/install explore-korea
功能描述
Plan your Korea experience — Seoul's palaces and K-pop culture, Busan's beaches, Jeju Island's nature, Korean BBQ crawls, and K-beauty shopping. Also support...
使用说明 (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: explore-korea

Overview

Plan your Korea experience — Seoul's palaces and K-pop culture, Busan's beaches, Jeju Island's nature, Korean BBQ crawls, and K-beauty shopping.

When to Activate

User query contains:

  • English: "Korea", "Seoul", "Busan", "Jeju"
  • Chinese: "韩国", "首尔", "釜山", "济州岛", "去韩国"

Do NOT activate for: Japan → explore-japan

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 Korea

Trigger: "Korea trip"

visa check + flights to ICN + hotels + palaces/food/shopping POIs

Output: Complete Korea itinerary.

Playbook B: Seoul

Trigger: "Seoul trip"

Flight to ICN + Seoul hotel + Gangnam/Myeongdong/palace POIs

Output: Seoul city deep dive.

Playbook C: Jeju

Trigger: "Jeju Island"

Flight to CJU + Jeju hotel + nature POIs

Output: Jeju Island nature 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 "Beijing" --destination "Seoul" --dep-date 2026-05-01 --sort-type 3

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 detailUrl.
  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.

Korea: visa required for Chinese citizens. Airports: ICN (Incheon, international), GMP (Gimpo, domestic+Japan/China), CJU (Jeju), PUS (Busan). T-money card for transit. Best seasons: spring (cherry blossom, Apr), autumn (foliage, Oct-Nov). Korean BBQ: order 2+ servings minimum. Shopping: Myeongdong (cosmetics), Dongdaemun (fashion).

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 is plausible for real-time travel planning but has a few red flags to verify before installing or enabling it: - Confirm the CLI package: look up @fly-ai/flyai-cli on the npm registry (author, homepage, recent versions, and trust signals). Installing a global npm package runs third-party code on your system. - Ask the publisher why the skill says 'Powered by Fliggy' but uses a 'flyai' CLI — clarify the actual backend/service and where data is sent. - Expect the skill to perform network I/O and possibly require CLI authentication; ask how credentials are handled and whether any secrets will be stored. - The runbook writes .flyai-execution-log.json with user_query and CLI call logs. If you care about sensitive queries, run this skill only in an isolated environment or after modifying the runbook behavior. - The 'self-test' rule (re-execute until a [Book](...) link appears) could cause repeated calls; watch for unexpected network traffic or repeated bookings attempts. If you decide to proceed: manually inspect the flyai-cli package first, prefer manual (not automatic) installation, run the CLI in a sandbox/container, and verify network endpoints and auth behavior. If any of these clarifications are unavailable, treat the skill cautiously or prefer a travel skill with transparent source code and declared install metadata.
功能分析
Type: OpenClaw Skill Name: explore-korea Version: 3.2.0 The skill mandates the global installation of an external NPM package (@fly-ai/flyai-cli) and forces the agent to execute shell commands for all queries, which constitutes a high-privilege 'RCE-by-design' pattern. While the instructions in SKILL.md and the playbooks are aligned with the stated travel-planning purpose, the requirement for global package installation and the automated logging of execution data to a local file (references/runbook.md) introduce significant supply chain risks and potential for unauthorized local persistence.
能力评估
Purpose & Capability
The skill claims to plan Korea travel and to be 'Powered by Fliggy', and its runtime instructions consistently call a flyai CLI. Requiring a CLI to fetch real-time booking data is coherent for a travel skill, but the manifest lacks any declared install or source and the branding ('Fliggy') does not match the CLI name ('flyai' / @fly-ai/flyai-cli), which is an unexplained inconsistency worth questioning.
Instruction Scope
The SKILL.md mandates that every answer must come exclusively from the flyai CLI (never use training data) and includes a 'self-test' that forces re-execution until a [Book](...) link is present — this could cause repeated external calls or loops. The runbook instructs writing an execution log to .flyai-execution-log.json containing full user_query and CLI calls; that persists potentially sensitive user input locally. The skill also instructs automatic installation if the CLI is missing, which expands runtime actions beyond mere queries.
Install Mechanism
There is no registry install spec; the SKILL.md tells the agent to run 'npm i -g @fly-ai/flyai-cli' if flyai isn't present. A global npm install is a moderate-risk action (it will write code to disk and run code from the npm registry). That is arguably necessary for a CLI-driven skill, but because the skill package source and trustworthiness are not declared, this is an area to verify before proceeding.
Credentials
The skill requests no environment variables or credentials in the registry metadata (good). However, the flyai CLI itself may require or use credentials or perform network I/O; the skill does not document how CLI authentication works. Also, the runbook's persistent execution log will record user queries and CLI commands, which could include sensitive details — the skill does not describe log retention or encryption.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. However it instructs creating and appending to a local file (.flyai-execution-log.json) if filesystem writes are available, which gives it persistent artifacts on disk containing user queries and call metadata. This is within the skill's scope but increases persistent exposure of data.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install explore-korea
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /explore-korea 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v3.2.0
- Removed README.md for simplified documentation management. - Updated SKILL.md: condensed domain knowledge and usage notes; minor corrections and streamlining. - No changes to functional commands or core workflows. - All scenario playbooks, templates, and fallback guidance now referenced via /references folder only.
v3.2.2
- Enforced strict CLI-sourced answers: All travel data must come directly from flyai-cli output, never from prior knowledge. - Enhanced execution rules: Skill will halt if flyai-cli is unavailable, instructing users to install it without fallback to stored knowledge. - Mandated booking links: Every recommendation requires a [Book](...) link from flyai, ensuring real-time pricing and authentic options. - Refined workflow and parameter collection: Robust process for gathering needed trip details, with user prompts limited to streamline planning. - Clear scenario-based playbooks: Tailored command orchestration for Korea, Seoul, or Jeju trips to deliver complete, actionable itineraries.
元数据
Slug explore-korea
版本 3.2.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 2
常见问题

Explore Korea 是什么?

Plan your Korea experience — Seoul's palaces and K-pop culture, Busan's beaches, Jeju Island's nature, Korean BBQ crawls, and K-beauty shopping. Also support... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 88 次。

如何安装 Explore Korea?

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

Explore Korea 是免费的吗?

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

Explore Korea 支持哪些平台?

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

谁开发了 Explore Korea?

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

💬 留言讨论