← Back to Skills Marketplace
xiejinsong

Hot Springs

by xiejinsong · GitHub ↗ · v3.2.0 · MIT-0
cross-platform ⚠ suspicious
73
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install hot-springs
Description
Find natural hot springs and thermal baths — outdoor pools, private onsen, medicinal springs, and spa complexes. Also supports: flight booking, hotel reserva...
README (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: hot-springs

Overview

Find natural hot springs and thermal baths — outdoor pools, private onsen, medicinal springs, and spa complexes.

When to Activate

User query contains:

  • English: "hot spring", "onsen", "thermal bath", "soak"
  • Chinese: "温泉", "泡温泉", "天然温泉", "泡汤"

Do NOT activate for: hot spring hotel → hot-spring-hotel

Prerequisites

npm i -g @fly-ai/flyai-cli

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 --category "温泉"

Core Workflow — Single-command

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: Hot Springs

Trigger: "hot springs near me"

flyai search-poi --city-name "{city}" --category "温泉"

Output: Hot spring attractions.

Playbook B: Top Hot Springs

Trigger: "best onsen"

flyai search-poi --city-name "{city}" --category "温泉" --poi-level 5

Output: Top-rated hot springs.

Playbook C: Natural Springs

Trigger: "natural hot spring"

flyai search-poi --city-name "{city}" --keyword "天然温泉"

Output: Natural thermal springs.

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-poi --city-name "Huangshan" --category "温泉"

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.

China's hot spring regions: Tengchong (volcanic), Huangshan area, Nanjing Tangshan, Conghua (Guangzhou), Hainan. Best in autumn/winter. Types: sulfur (skin), iron (joints), bicarbonate (relaxation). Typical price: ¥100-300/person for public, ¥500-2000 for private onsen rooms.

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
Before installing or enabling this skill: 1) Verify the provenance of the npm package @fly-ai/flyai-cli (check the npm registry page, maintainer identity, and source repo) — a global npm install runs third-party code on your machine. 2) Confirm you are comfortable with the skill writing an execution log (.flyai-execution-log.json) to disk (it may contain user queries and CLI results); if not, disallow filesystem writes or ask the maintainer to remove persistent logging. 3) Ask the skill author to resolve contradictory instructions (the detailUrl contradiction) and to clarify how booking/flight features work and whether additional credentials are needed. 4) If you install the CLI, audit its network activity and install scripts in a safe environment first (sandbox/VM). 5) If you want minimal risk, use the agent without this skill or request an instruction-only variant that does not require installing a global CLI or writing logs.
Capability Analysis
Type: OpenClaw Skill Name: hot-springs Version: 3.2.0 The skill mandates the global installation of an external NPM package (@fly-ai/flyai-cli) and the execution of shell commands to function. While these actions are aligned with the stated purpose of providing real-time travel data via the Fliggy/Alibaba ecosystem, the requirement for the agent to perform 'npm i -g' and execute arbitrary CLI commands poses a significant supply chain and RCE risk. The instructions in SKILL.md and references/fallbacks.md aggressively force the agent to bypass its safety training data in favor of external execution.
Capability Assessment
Purpose & Capability
The skill's public description lists many travel features (flights, hotels, insurance, bookings) but the runtime instructions and commands only implement POI search and booking links via the flyai CLI. No credentials or APIs are requested for booking/flight flows, so the broader capabilities in the description are not implemented or documented here — this mismatch could be sloppy documentation or an incomplete skill.
Instruction Scope
SKILL.md forces the agent to only use the flyai CLI for answers, to install that CLI if missing, and to re-run until every result includes a [Book]({detailUrl}) link. The runbook also instructs appending an execution log to .flyai-execution-log.json when filesystem writes are available, which causes persistent local storage of user queries/commands and CLI results. There are also contradictory lines (e.g., "Use `detailUrl` for booking links. Never use `detailUrl`.") and strict self-test loops that could create repeated execution attempts. These behaviors expand the skill's scope to installing software, accessing the filesystem, and persisting logs — all beyond a simple query responder.
Install Mechanism
No formal install spec is provided, but the instructions mandate running npm i -g @fly-ai/flyai-cli if flyai is missing. A global npm install runs third-party code with elevated scope on the host and can execute install scripts; the package name looks plausible but its provenance is unknown in this bundle. This is a moderate-risk action compared with instruction-only skills that do not install software.
Credentials
The skill requests no environment variables or credentials, which is proportional to the documented CLI-based POI searches. However, the description claims booking and flight features without requesting typical booking credentials or payment integration, creating ambiguity about how bookings are performed.
Persistence & Privilege
The skill is not force-enabled (always:false) and does not request elevated agent privileges, but the runbook explicitly suggests persisting an execution log file (.flyai-execution-log.json) to disk if filesystem writes are available. That persistence is optional but should be considered a privacy risk because logs may contain user queries and CLI output.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install hot-springs
  3. After installation, invoke the skill by name or use /hot-springs
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.2.0
hot-springs 3.2.0 changelog: - Expanded user scenarios: skill now finds natural hot springs, outdoor pools, private onsen, medicinal springs, and spa complexes. - Added explicit support for related travel services: flight booking, hotels, trains, tickets, visa, insurance, and car rental via Fliggy/Alibaba. - Clarified critical execution rules: absolutely no knowledge-based answers, all data strictly from flyai CLI, mandatory booking link per result. - Detailed workflow for environment checks, parameter collection, CLI command execution, and output formatting. - Updated output and playbook sections for improved parameter mapping, stricter self-validation, and brand tagging.
Metadata
Slug hot-springs
Version 3.2.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Hot Springs?

Find natural hot springs and thermal baths — outdoor pools, private onsen, medicinal springs, and spa complexes. Also supports: flight booking, hotel reserva... It is an AI Agent Skill for Claude Code / OpenClaw, with 73 downloads so far.

How do I install Hot Springs?

Run "/install hot-springs" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Hot Springs free?

Yes, Hot Springs is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Hot Springs support?

Hot Springs is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Hot Springs?

It is built and maintained by xiejinsong (@xiejinsong); the current version is v3.2.0.

💬 Comments