Agent skill · Design & Presentation

status-match

Status match and status challenge rules for airlines and hotels. Covers free direct matches, paid concierge via statusmatch.com with fees, card-granted status, and critical lifetime/once-per-N-years restrictions that make wasted matches expensive.

borskigithub.com/borskiGitHub ↗
claude-coderead-onlyMIT
Install
npx skills add borski/travel-hacking-toolkit --skill status-match --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 14 KB
Bundled scripts: none
Allowed tools: Bash(jq*)
Path: plugins/travel-hacking-toolkit/skills/status-match/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

# Status Match Reference When a user wants to switch loyalty programs or shortcut to elite status, the question is rarely "can I match?" but "should I match?" The answer depends on three things this skill makes explicit: how often the program lets you do it, what it costs (free vs paid concierge), and whether a credit card already grants the tier you want. **Reference data:** [`data/status-match.json`](../../data/status-match.json). Refresh cadence is 90 days because rules change occasionally but not weekly. ## Critical Rule: Lifetime Restrictions Punish Wasted Matches **Many of the best status matches are once-per-lifetime or once-every-3-years.** A match wasted in the wrong year because the user doesn't have travel coming up is gone forever. Always read the `lifetime_warning` field before recommending an application. The biggest offenders: | Program | Restriction | |---------|-------------| | **Alaska Atmos Rewards** | **ONCE PER LIFETIME** (literally; from terms: "one status match for the lifetime of their account") | | **Flying Blue (paid concierge)** | **ONCE PER LIFETIME** ("Only 1 match is allowed per person") | | **United MileagePlus** | **ONCE EVERY 3 YEARS** (failed chall

What's inside
Steps it walks through
  1. Critical Rule: Lifetime Restrictions Punish Wasted Matches
  2. When to Use This Skill
  3. When NOT to Use
  4. The Three Paths to Elite Status
  5. Path 1: Free Direct Status Match
  6. Path 2: Paid Concierge via statusmatch.com
  7. Path 3: Card-Granted Renewable Status
  8. Workflow
  9. Step 1: Identify what status the user actually wants
  10. Step 2: Check Path 3 first (card-based)
  11. Step 3: Check Path 1 (free direct match)
  12. Step 4: If no free path exists, check Path 2 (paid concierge)
  13. Step 5: Cross-check via community database
  14. Output Format
Commands it runs
All programs that allow free direct matches
All paid concierge programs with US fees
All cards that grant hotel status
All ONCE PER LIFETIME programs (never miss this warning)
More from travel-hacking-toolkit
All skills →
About this skill
What does the status-match skill do?

Status match and status challenge rules for airlines and hotels. Covers free direct matches, paid concierge via statusmatch.com with fees, card-granted status, and critical lifetime/once-per-N-years restrictions that make wasted matches expensive.

How do I install it?

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