Agent skill

stopovers

Per-program stopover rules for award redemptions. Which programs allow free stopovers, how many, how long, and which don't. Covers Icelandair, Aeroplan, Alaska, Flying Blue, Singapore, Cathay, JAL, and the negative space (BA, AA, Delta).

borski611★ · 1 repos on radarProfile →
claude-coderead-onlyMIT
Install
npx skills add borski/travel-hacking-toolkit --skill stopovers --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 11 KB
Bundled scripts: none
Allowed tools: Bash(jq*)Read
Path: plugins/travel-hacking-toolkit/skills/stopovers/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 611
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Stopover Rules per Loyalty Program Reference data for which programs allow stopovers on award redemptions, how many, where, for how long, and at what cost. Sourced primarily from each airline's own award rules pages, cross-checked against Frequent Miler, OMAAT, Travel Miles 101, Prince of Travel, and Upgraded Points. Data lives in [`data/stopovers.json`](../../data/stopovers.json). Refresh cadence is 90 days because stopover rules change rarely (much less often than transfer bonuses or program valuations). ## What Is a Stopover? A planned interruption of a journey at a point between origin and destination. The IATA standard definition is: - **More than 24 hours** for international itineraries - **More than 4 hours** for domestic itineraries (US/Canada) Each loyalty program defines its own rules within or beyond this baseline. Some programs let you stop for a week. Some let you stop for 365 days. Some don't allow stopovers at all. The headline value: a free stopover lets you visit two destinations on a single award. Iceland on the way to Europe. Tokyo on the way to Bangkok. Singapore on the way to Sydney. ## When to Use This Skill - User wants to plan a multi-city trip and asks "w

What's inside
Steps it walks through
  1. What Is a Stopover?
  2. When to Use This Skill
  3. When NOT to Use
  4. Quick Reference Table
  5. Programs That Allow Stopovers (positive)
  6. Programs That Do NOT Allow Stopovers (negative space)
  7. The Iceland Callout
  8. Reading the Data File
  9. Decision Rules
  10. Cross-References
  11. Source Hierarchy (Per Research Integrity Protocol)
  12. Avoiding Fabrication
Commands it runs
All programs that allow stopovers, sorted by max round-trip stopovers
jq '.programs[] | select(.category == "positive") |
data/stopovers.json | head -40
Find programs that allow free phone-bookable stopovers
jq '.programs[] | select(.category == "positive" and .surcharge_points == 0 and .booking_method == "phone") |
data/stopovers.json
Programs that do NOT allow stopovers (negative space)
jq '.programs[] | select(.category == "negative") | {name, restrictions}' data/stopovers.json
All sources/citations for a given program
jq '.programs[] | select(.id == "aeroplan") | .sources' data/stopovers.json
More from travel-hacking-toolkit
All skills →
About this skill
What does the stopovers skill do?

Per-program stopover rules for award redemptions. Which programs allow free stopovers, how many, how long, and which don't. Covers Icelandair, Aeroplan, Alaska, Flying Blue, Singapore, Cathay, JAL, and the negative space (BA, AA, Delta).

How do I install it?

Run `npx skills add borski/travel-hacking-toolkit --skill stopovers --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From borski/travel-hacking-toolkit, a repository with 611 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going