Agent skill

wikipedia-airports

Discover destinations served from any airport via Wikipedia. Sanity-check whether an airline flies a specific route, find regional service that fare tools miss, identify late-split-return airport options.

borski611★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add borski/travel-hacking-toolkit --skill wikipedia-airports --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: plugins/travel-hacking-toolkit/skills/wikipedia-airports/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

# Wikipedia Airports Use Wikipedia as a **route discovery and sanity-check source** for airport destinations. This is especially useful when: - an airport page has an **Airlines and destinations** section - an airline's own city-pair marketing pages confirm service patterns - flight search tools disagree about whether a route exists Wikipedia is **not a booking source** and not a real-time schedule source. Use it to discover likely routes, then confirm them with airline or fare tools. ## Best Use Cases - "What destinations does SAN serve?" - "Does Southwest fly SAN -> EUG?" - "What airports can I use for a late split return?" - "Which airline serves this small airport nonstop?" ## Workflow ### 1. Resolve the airport page from an IATA code Use Wikipedia search with the airport code plus the word `airport`. ```bash curl -s "https://en.wikipedia.org/w/api.php?action=query&list=search&srsearch=SAN+airport&format=json" \ | jq '.query.search[0:5][] | {title}' ``` Usually the first result is the airport page, e.g. `San Diego International Airport`. ### 2. Fetch the page Use the readable page HTML or the wikitext parse API. ```bash curl -s "https://en.wikipedia.org/w/api.php?action=parse&p

What's inside
Steps it walks through
  1. Best Use Cases
  2. Workflow
  3. 1. Resolve the airport page from an IATA code
  4. 2. Fetch the page
  5. 3. Look for route sections
  6. 4. Treat airline city-pair pages as a second source
  7. 5. Then confirm with fare tools
  8. Decision Rules
  9. Use Wikipedia to answer:
  10. Do NOT use Wikipedia to answer:
  11. Example: SAN and Southwest to EUG
  12. Useful Patterns
  13. Airport page lookup by IATA code
  14. Pull likely destination section lines
Commands it runs
curl -s "https://en.wikipedia.org/w/api.php?action=query&list=search&srsearch=SAN+airport&format=json" \
curl -s "https://en.wikipedia.org/w/api.php?action=parse&page=San_Diego_International_Airport&prop=wikitext&formatversion=2&format=json" \
curl -Ls "https://en.wikipedia.org/wiki/San_Diego_International_Airport"
curl -Ls "https://www.southwest.com/en/flights/flights-from-portland-or-to-san-diego" | rg "PDX|SAN|Portland|San Diego"
curl -Ls "https://www.southwest.com/en/flights/flights-from-portland-or-to-orange-county-santa-ana" | rg "PDX|SNA|Portland|Orange County"
curl -s "https://en.wikipedia.org/w/api.php?action=query&list=search&srsearch=${CODE}+airport&format=json" \
curl -s "https://en.wikipedia.org/w/api.php?action=parse&page=${PAGE}&prop=wikitext&formatversion=2&format=json" \
More from travel-hacking-toolkit
All skills →
About this skill
What does the wikipedia-airports skill do?

Discover destinations served from any airport via Wikipedia. Sanity-check whether an airline flies a specific route, find regional service that fare tools miss, identify late-split-return airport options.

How do I install it?

Run `npx skills add borski/travel-hacking-toolkit --skill wikipedia-airports --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