aerobase-travel_skill

This skill analyzes Aerobase jetlag scores for flights and summarizes recovery days, helping users choose routes with minimal jetlag impact.

Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill aerobase-travel

_meta.json284 B
SKILL.md8.4 KB

Overview

This skill provides jetlag-aware flight intelligence for AI travel agents using the Aerobase API. It ranks flights by jetlag impact, estimates recovery time, and supplies practical departure and arrival strategies. The skill also returns airport facilities and route-level analysis to help travelers minimize circadian disruption.

How this skill works

When given flight details or a route, the skill calls Aerobase endpoints to compute a 0–100 jetlag score, a tier (excellent/good/moderate/poor/severe), and estimated recovery days. It can search and rank multiple flights by jetlag, fetch airport facilities relevant to rest and recovery, analyze route timezone shifts, and surface jetlag-scored deals. Responses include human-readable insights, actionable strategies, and tips to present directly to users.

When to use it

Planning long-haul travel and wanting the least jetlaggy option
Comparing flights where price vs. jetlag tradeoffs matter
Advising business travelers who must be functional on arrival
Preparing layovers and choosing airports with recovery facilities
Curating travel deals that balance cost and circadian impact

Best practices

Always show the jetlag score and recovery_days up front when presenting options
Compare scores between alternatives and translate differences into recovery time (e.g., “one day less recovery”)
Lead with departure/arrival strategies and one-line actionable tips users can follow immediately
Convert timezone_shift_hours into plain language (e.g., “you’ll cross 9 hours heading east”)
Respect API rate limits (free tier: 10 requests/hour) and cache repeated airport/route lookups

Example use cases

Score a specific flight: user supplies departure and arrival times to get a jetlag score, tier, and recovery plan
Search flights for a date: return top 3–5 options ranked by jetlag and show price when available
Airport briefing for layovers: list sleep pods, showers, lounges, and time-to-transit to aid recovery
Route intelligence for planners: compare direct vs connecting options and explain when a connection reduces jetlag
Travel deals feed: surface high value_score offers while flagging jetlag impact and error fares

FAQ

You must provide origin and destination IATA codes and ISO-8601 departure and arrival timestamps with timezone offsets. Cabin class is optional.

How should I present multiple flight options?

Lead with the best jetlag score and recovery_days, then compare the top and bottom scores and summarize the practical impact (e.g., days of recovery difference).

What are common tier meanings?

80–100 excellent (0–1 days), 65–79 good (1–2 days), 50–64 moderate (2–3 days), 35–49 poor (3–5 days), 0–34 severe (5+ days).

Any rate limit I should be aware of?

Free tier allows 10 requests per hour; monitor calls_remaining in the response meta and cache results when possible.