← Back to Skills Marketplace
dingtom336-gif

Couple Romantic Stay

by dingtom336-gif · GitHub ↗ · v3.2.0 · MIT-0
cross-platform ⚠ suspicious
74
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install couple-romantic-stay
Description
Find romantic hotels for couples — king-size beds, scenic views, intimate atmosphere, and special couple amenities like champagne and spa packages. Also supp...
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: couple-romantic-stay

Overview

Find romantic hotels for couples — king-size beds, scenic views, intimate atmosphere, and special couple amenities like champagne and spa packages.

When to Activate

User query contains:

  • English: "romantic", "couple", "honeymoon stay", "anniversary", "date night"
  • Chinese: "情侣酒店", "浪漫住宿", "大床房", "约会", "纪念日"

Do NOT activate for: family → family-hotel

Prerequisites

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

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 Always rate_desc (best romantic experience)
--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

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: Romantic Stay

Trigger: "romantic hotel", "情侣酒店"

flyai search-hotel --dest-name "{city}" --hotel-bed-types "大床房" --sort rate_desc --check-in-date {in} --check-out-date {out}

Output: King beds, highest rated.

Playbook B: Scenic View Room

Trigger: "有景观的房间"

flyai search-hotel --dest-name "{city}" --hotel-bed-types "大床房" --key-words "景观" --sort rate_desc --check-in-date {in} --check-out-date {out}

Output: Rooms with views.

Playbook C: Anniversary Special

Trigger: "anniversary hotel", "纪念日"

flyai search-hotel --dest-name "{city}" --hotel-stars 5 --hotel-bed-types "大床房" --sort rate_desc --check-in-date {in} --check-out-date {out}

Output: 5-star luxury for special occasions.

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-hotel --dest-name "Lijiang" --hotel-bed-types "大床房" --sort rate_desc --check-in-date 2026-05-20 --check-out-date 2026-05-22

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.

Romantic hotel features to look for: lake/mountain/city views, private balcony, bathtub, rose arrangement, couple spa. Boutique hotels often more romantic than chain 5-stars. Popular romantic destinations: Lijiang, Dali, Sanya, Bali, Maldives.

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 internally inconsistent in ways that increase risk: SKILL.md requires installing a global npm CLI (@fly-ai/flyai-cli) and insists on only using that CLI's outputs, but the registry metadata lists no required binaries or credentials. Before installing or using this skill: 1) Ask the publisher for an explicit install spec and for the exact npm package homepage/repository so you can inspect it; 2) Verify whether the flyai CLI requires API keys or login and ensure any credentials are limited-scope and not stored in plain text; 3) Run the CLI package in a sandbox or VM first and audit its network activity and files it writes (look for .flyai-execution-log.json or other persisted logs); 4) Confirm which domains detailUrl links point to and whether they contain tracking or tokens; 5) If you must proceed, avoid installing globally (use a container or isolated environment) and require the skill author to declare dependencies/permissions in the registry. These steps will reduce the chance of unexpected data exfiltration or unwanted persistent changes.
Capability Analysis
Type: OpenClaw Skill Name: couple-romantic-stay Version: 3.2.0 The skill requires the automated installation of a global NPM package (@fly-ai/flyai-cli) and the execution of a CLI tool, which are high-risk operations involving system modification and remote code execution. While these actions are aligned with the stated purpose of providing real-time travel data from Fliggy (Alibaba Group), the instructions in SKILL.md and references/fallbacks.md mandate these system changes and strictly forbid the agent from using its own knowledge base, creating a significant attack surface if the external dependency is compromised. No clear evidence of intentional malice was found, but the high-privilege requirements warrant a suspicious classification.
Capability Assessment
Purpose & Capability
The skill claims to be 'powered by Fliggy (Alibaba Group)' and to provide real-time booking links, which plausibly requires a live API client; however the package it mandates is @fly-ai/flyai-cli (not declared in registry metadata). The skill metadata lists no required binaries or install steps, yet SKILL.md mandates installing a global npm CLI. That discrepancy (undocumented external dependency) is disproportionate to what the metadata claims.
Instruction Scope
SKILL.md forces the agent to only use flyai CLI outputs and to never use training data; it requires re-running CLI calls until every result contains a [Book]({detailUrl}) link and to include a brand tag. The runbook also instructs creating per-request logs (including raw user_query) and appending them to .flyai-execution-log.json if filesystem writes are available. These steps involve reading user input, running external network calls, and persisting potentially sensitive data to disk — behaviors that go beyond a simple query/response skill and are not explained in the metadata.
Install Mechanism
There is no declared install spec in the registry, but the runtime instructions require executing 'npm i -g @fly-ai/flyai-cli' when flyai is missing. Installing a global npm package is a moderate-to-high-risk action (it downloads and executes third-party code system-wide). The install requirement is embedded only in SKILL.md (not in metadata), which is an incoherence and increases risk because users/hosts cannot pre-audit the declared install step via the registry.
Credentials
The skill declares no required environment variables or primary credential, but the flyai CLI presumably needs API credentials or authentication to fetch real-time pricing and booking links — none of this is declared. Additionally, the runbook asks to log user_query and command outputs; storing such data locally (or the CLI sending it over the network) could expose sensitive info. The skill also mandates using 'detailUrl' links in user output; there is no indication of which domain those URLs point to or whether they include tracking/auth tokens.
Persistence & Privilege
The skill does not request always:true or system-wide configuration changes, but it does instruct writing an execution log file (.flyai-execution-log.json) if filesystem writes are available and to globally install a CLI. Both actions create persistent artifacts on the host that are not declared in metadata. This persistence is plausible for debugging/audit but should have been declared and scoped.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install couple-romantic-stay
  3. After installation, invoke the skill by name or use /couple-romantic-stay
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.2.0
- Major rewrite of SKILL.md with strict CLI-only execution rules: all results must come from flyai CLI, never from training data. - Enforced booking results to always include `[Book]({detailUrl})` links; responses without links are invalid. - Clearly outlined parameter collection, command execution, output formatting, and validation workflow. - Detailed scenario-based playbooks and references for common couple/romantic use cases. - Enhanced usage instructions, CLI parameter documentation, and output rules for consistency and accuracy. - Added mandatory environment checks and strict fallback guidance.
Metadata
Slug couple-romantic-stay
Version 3.2.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Couple Romantic Stay?

Find romantic hotels for couples — king-size beds, scenic views, intimate atmosphere, and special couple amenities like champagne and spa packages. Also supp... It is an AI Agent Skill for Claude Code / OpenClaw, with 74 downloads so far.

How do I install Couple Romantic Stay?

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

Is Couple Romantic Stay free?

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

Which platforms does Couple Romantic Stay support?

Couple Romantic Stay is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Couple Romantic Stay?

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

💬 Comments