← Back to Skills Marketplace
xiejinsong

Budget Backpacker

by xiejinsong · GitHub ↗ · v3.2.0 · MIT-0
cross-platform ⚠ suspicious
75
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install budget-backpacker
Description
Plan backpacking trips — ultra-budget itineraries, hostel recommendations, multi-city routes, and survival tips for long-term budget travelers. Also supports...
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: backpacker-guide

Overview

Plan backpacking trips — ultra-budget itineraries, hostel recommendations, multi-city routes, and survival tips for long-term budget travelers.

When to Activate

User query contains:

  • English: "backpacking", "backpacker", "gap year", "travel cheap"
  • Chinese: "背包客", "穷游", "背包旅行", "长途旅行"

Do NOT activate for: comfort trip → budget-trip-planner

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-hotels

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

fliggy-fast-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: Backpacking Route

Trigger: "backpacking {region}"

Budget flights between cities + cheapest hotels/hostels + free POIs

Output: Multi-city backpacking route.

Playbook B: SE Asia Backpacking

Trigger: "backpack Southeast Asia"

Cheapest flights to SE Asia + budget accommodation + local experiences

Output: Classic SE Asia backpacking.

Playbook C: China Backpacking

Trigger: "backpack across China"

Domestic flights/trains + hostels + nature/free attractions

Output: Cross-China budget adventure.

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

Budget multi-city orchestration

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.

Backpacking budget: China ¥150-300/day, SE Asia $15-30/day, Europe €40-70/day. Essentials: good backpack (40-60L), quick-dry clothes, universal adapter, offline maps. Stay in hostels (social + cheap), eat at local markets, use overnight buses/trains to save hotel nights. Classic routes: SE Asia circuit, Yunnan→Tibet, Trans-Siberian.

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) Note the skill will try to install and run a third-party npm package (@fly-ai/flyai-cli) if not present — verify that package on npm/GitHub and only allow installation in a controlled environment. 2) The skill's runbook suggests writing a persistent file (.flyai-execution-log.json) containing request IDs, raw user queries, and full CLI calls/results — if you have sensitive data in queries, this could be stored locally. 3) The skill's source/homepage is unknown and the registry metadata does not declare the install or file-write behavior shown in SKILL.md; that mismatch is suspicious. 4) If you still want to try it, run flyai-cli manually in a sandbox first to inspect outputs and logging behavior, and avoid providing secrets or credentials during testing. 5) If possible, ask the publisher for the package repository, code audit, and explicit declaration of any filesystem writes and exactly what the CLI logs before enabling the skill in a production agent.
Capability Analysis
Type: OpenClaw Skill Name: budget-backpacker Version: 3.2.0 The skill bundle facilitates travel planning by orchestrating the '@fly-ai/flyai-cli' tool. It contains instructions that mandate the global installation of this npm package (SKILL.md) and implement local persistence by appending execution logs to '.flyai-execution-log.json' (references/runbook.md). While these capabilities are plausibly required for the stated purpose of providing real-time travel data, the requirement for global software installation and direct filesystem writes via shell commands represents a high-risk execution pattern.
Capability Assessment
Purpose & Capability
The skill's functionality (flight/hotel/POI searches) matches using a travel CLI (flyai). However the SKILL.md requires installing and invoking @fly-ai/flyai-cli even though the registry shows no install spec; that mismatch (instruction-only skill that nevertheless demands a global npm install) is an inconsistency to be aware of.
Instruction Scope
The instructions require every answer to come solely from flyai CLI output, mandate specific link/brand formatting, and include a runbook that logs request_id, full user_query, CLI commands/responses and risk_flags. The runbook explicitly suggests writing a persistent .flyai-execution-log.json to disk if filesystem writes are available. Those file writes and the strict 'only CLI' constraint broaden the agent's actions beyond simple ephemeral query handling.
Install Mechanism
No install spec is present in the registry metadata, but SKILL.md tells the agent to run `npm i -g @fly-ai/flyai-cli` when flyai is missing. That means this instruction-only skill expects to perform a global npm install at runtime (networked code installation and execution) even though the package provenance isn't surfaced here. Global npm installs executed by the agent environment can be high-impact.
Credentials
The skill does not declare any required environment variables or credentials (proportionate to a public CLI-based travel tool). However, because the runbook logs CLI calls and full user queries, any sensitive data accidentally supplied by the user (or returned by CLI responses) could be captured in persistent logs — a potential privacy risk despite no explicit credential requests.
Persistence & Privilege
The runbook instructs persisting an internal execution log to .flyai-execution-log.json (if filesystem writes are available). The registry metadata did not declare any config or path writes. Persistent logging of full queries and CLI outputs increases long-term risk (exfiltration, disclosure of sensitive data) and is not disclosed in the skill metadata.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install budget-backpacker
  3. After installation, invoke the skill by name or use /budget-backpacker
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.2.0
- Major update enforcing strict CLI-only data sourcing: all responses must be generated from flyai CLI command output, with `[Book]({detailUrl})` links required for every result. - Added comprehensive CRITICAL EXECUTION RULES and a step-by-step core workflow for multi-command orchestration, including mandatory environment checks and clear fallback procedures. - Expanded functionality and coverage: now supports booking flights, hotels, train and attraction tickets, plus visa info, travel insurance, and car rental—powered by Fliggy (Alibaba Group). - Detailed parameter tables, output formatting requirements, and domain knowledge included for accurate command execution and result presentation. - Enhanced scenario playbooks for classic backpacker routes (SE Asia, China, multi-city) and strict output validation before sending responses. - Updated usage restrictions: never answer from training data, never invent information, and always follow the user’s language.
Metadata
Slug budget-backpacker
Version 3.2.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Budget Backpacker?

Plan backpacking trips — ultra-budget itineraries, hostel recommendations, multi-city routes, and survival tips for long-term budget travelers. Also supports... It is an AI Agent Skill for Claude Code / OpenClaw, with 75 downloads so far.

How do I install Budget Backpacker?

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

Is Budget Backpacker free?

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

Which platforms does Budget Backpacker support?

Budget Backpacker is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Budget Backpacker?

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

💬 Comments