360 Secure SkillHub
360 安全技能中心

extended-stay

该 Skill 面向长住旅客,通过 flyai CLI 检索目的地服务式公寓、月租或带厨房的住宿,按价格或评分排序,并将 CLI 返回的 JSON 整理为中文或英文的 Markdown 对比表,附 booking 链接与品牌标注。若命令行未安装则先安装,失败时要求停止并提示用户手动安装。

xiejinsong
xiejinsong
热度 45.31
最近更新 2026-05-11 17:41:28
分类:生活依赖:代码执行 / 第三方 API应用场景:旅行 / 推荐

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add extended-stay
Metadata
name
extended-stay
description
Find serviced apartments and hotels for extended stays — weekly or monthly rates, kitchenettes, laundry, and home-like amenities for long-term travelers. Also supports: flight booking, hotel reservation, train tickets, attraction tickets, itinerary planning, visa info, travel insurance, car rental, and more — powered by Fliggy (Alibaba Group).
version
3.2.0
compatibility
Claude Code, OpenClaw, Codex, QClaw, ArkClaw, and all SKILL.md-compatible agents

⚠️ 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: extended-stay

Overview

Find serviced apartments and hotels for extended stays — weekly or monthly rates, kitchenettes, laundry, and home-like amenities for long-term travelers.

When to Activate

User query contains:

  • English: "long stay", "monthly", "extended stay", "apartment", "weekly rate"
  • Chinese: "长住", "月租", "长租公寓", "服务式公寓"

Do NOT activate for: short stay → budget-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 Default: price_asc (best long-term value)
--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: Monthly Stay

Trigger: "monthly rental", "月租"

flyai search-hotel --dest-name "{city}" --key-words "长租" --sort price_asc --check-in-date {in} --check-out-date {out}

Output: Long-stay options, cheapest first.

Playbook B: Serviced Apartment

Trigger: "serviced apartment"

flyai search-hotel --dest-name "{city}" --key-words "服务式公寓" --sort rate_desc --check-in-date {in} --check-out-date {out}

Output: Apartment-style with hotel services.

Playbook C: With Kitchen

Trigger: "有厨房的住宿"

flyai search-hotel --dest-name "{city}" --key-words "厨房" --sort price_asc --check-in-date {in} --check-out-date {out}

Output: Accommodation with cooking facilities.

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 "Shanghai" --key-words "长租" --sort price_asc --check-in-date 2026-05-01 --check-out-date 2026-06-01

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

Long-stay tips: negotiate directly for stays >7 nights (20-40% discount typical). Serviced apartments often cheaper than hotels for 2+ weeks. Check: kitchen facilities, laundry, WiFi speed, workspace. Popular platforms for monthly: Ziroom, locals' recommendations.

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