Use Zim as a travel workflow engine, not a generic search helper. Accept structured or messy travel intent, apply policy and traveler preferences, assemble coherent booking-ready options, and state clearly what is and is not automated.
This skill package includes:
SKILL.md — operating instructions for the skillscripts/search-flights.sh — Travelpayouts/Aviasales flight search with cached-fare fallbackscripts/search-hotels.sh — hotel deeplink generation for live availability lookupscripts/search-cars.sh — car rental comparison deeplinksreferences/api-guide.md — API/deeplink notes for Travelpayouts and related linksreferences/agent-to-agent-booking.md — product model and truthfulness ruleszim/ — Python package implementing:zim flights, zim hotels, zim cars, zim trip, zim preferences, zim policy)tests/ — package testspyproject.toml — Python package metadata and dependency declarationsDo not describe this package as shell scripts only. It contains both shell helpers and a Python application.
Require all of the following when using or publishing this skill:
bashcurljqpython3pydantic>=2.0click>=8.0httpx>=0.25python-dateutilstripe>=8.0pytest>=7.0pytest-asyncio>=0.21respx>=0.21If a downstream environment expects requirements.txt, generate it from the package metadata or install from pyproject.toml. This package currently declares dependencies in pyproject.toml, not in a checked-in requirements.txt file.
Declare these explicitly when using the skill:
| Variable | Required | Purpose |
|---|---|---|
| --- | --- | --- |
TRAVELPAYOUTS_TOKEN | Yes for flight/hotel affiliate search | Travelpayouts / Aviasales token used for API access and affiliate attribution |
TRAVELPAYOUTS_MARKER | Yes for production affiliate attribution consistency | Affiliate marker identifier for Travelpayouts deeplinks and tracking |
STRIPE_SECRET_KEY | Yes for payment flow | Stripe secret key used to create and retrieve Checkout Sessions |
STRIPE_WEBHOOK_SECRET | Yes for webhook verification in deployed payment flow | Stripe webhook signature secret |
ZIM_BASE_URL | No | Base URL for Stripe success/cancel redirects; defaults to http://localhost:8000 |
Important notes:
TRAVELPAYOUTS_TOKEN enables the current search scripts.TRAVELPAYOUTS_MARKER should be treated as required configuration for a production deployment even if some current scripts reuse the token as a marker fallback.STRIPE_SECRET_KEY should be sk_test_... in the current beta/test setup.Zim depends on these external services:
Used for:
Used for:
Zim may generate outbound deeplinks to:
These links are for comparison or manual completion unless a real provider executor is added.
Be precise about what Zim does today.
PlaceholderExecutor does not create real airline, hotel, or car rental reservations.booked in plain language unless supplier-side booking execution truly happened.Preferred truthful language:
booking-ready options assembledawaiting approvalpayment link createdpayment collected; provider reservation still requires execution/manual completionAvoid false claims like:
your trip is fully bookedpayment completed and reservation confirmedunless a real provider confirmation exists.
Zim includes payment orchestration via Stripe, but payment-card handling is intentionally limited.
STRIPE_SECRET_KEY.STRIPE_WEBHOOK_SECRET in deployed flows.Treat booking/payment metadata as sensitive operational data even though raw card data is not stored by the package.
# Flights
bash scripts/search-flights.sh LHR DXB 2025-12-15 2025-12-20 usd 5
# Hotels
bash scripts/search-hotels.sh "Dubai" 2025-12-15 2025-12-18 usd 10
# Cars
bash scripts/search-cars.sh "Dubai Airport" 2025-12-15 2025-12-18
# Install package locally
python3 -m pip install .
# Search flights
zim flights LHR DXB 2026-04-15 --return-date 2026-04-20 --cabin business
# Search hotels
zim hotels Dubai 2026-04-15 2026-04-20 --stars-min 4
# Search cars
zim cars "Dubai Airport" 2026-04-15 2026-04-20 --car-class suv
# Assemble full itinerary
zim trip LHR DXB 2026-04-15 --return-date 2026-04-20 --mode business --human
When handling travel messages on the WhatsApp channel, use the Zim WhatsApp agent for a smoother conversational experience with stateful multi-turn flows (search → select → confirm → book).
bash /home/ubuntu/.openclaw/workspace/zim/scripts/zim-wa.sh "<user message>" "whatsapp:<user_phone>"
This returns JSON: {"response": "...", "success": true/false}
Send the response text back to the user on WhatsApp.
The WhatsApp agent maintains state per user automatically:
State persists across calls via SQLite, so multi-message conversations work.
zim-wa.sh)zim flights, zim hotels)search-flights.sh)Extract as many of these fields as possible:
Core trip fields
business or personalFlight fields
Hotel fields
Car fields
Policy / workflow fields
If key fields are missing, ask only for the minimum needed to continue.
Convert city names to IATA codes before flight search where needed. Common defaults:
Convert dates to YYYY-MM-DD.
Apply ranking differently by mode.
Business mode
Personal mode
Use the Python CLI when you want structured JSON for agent consumption. Use shell scripts when you want simple direct output and live deeplinks.
Default behavior is to combine flight + hotel + car into a coherent recommendation when the request implies a trip.
Preferred response structure:
When total cost exceeds threshold or any item is out of policy, say approval is required.
When payment has not been started, say so.
When payment link/session exists, say so.
When provider execution is still placeholder/manual, say so.
Surface recurring preferences as durable travel preferences when relevant:
TRAVELPAYOUTS_TOKEN is not set, explain that affiliate-linked flight/hotel search cannot run.STRIPE_SECRET_KEY is not set, explain that checkout session creation cannot run.Read these only when needed:
references/api-guide.mdreferences/agent-to-agent-booking.md共 1 个版本