Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →borski/trip-log
Save flight searches, itineraries, and booked trips to the trips/logs/ directory for future reference. OPT-IN — use when the user asks to log a trip or look up past searches, or on every search only if the user has said they want automatic logging. Also use to update status when a trip is booked or completed.
Passed 16 of 20 test cases with the skill, and 4 of 20 without it.
and 25 more in the full report
14 fixed4 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Create the YAML frontmatter block for a new trip log document covering an upcoming award search from LAX to SYD in business cabin from 2026-11-01 to 2026-11-15 searched on 2026-05-10.
| Checked | Without skill | With skill |
|---|---|---|
| Expect frontmatter key destinations with array [SYD]. | Missed | Passed |
| Expect frontmatter key travel_dates formatted as YYYY-MM-DD to YYYY-MM-DD. | Missed | Passed |
| Expect frontmatter key cabin set to business. | Missed | Passed |
The instructions your model reads when the skill loads.
Save and retrieve flight searches, award analyses, and booked itineraries from trips/logs/. Past entries are a reference library — pull them when planning connected trips, checking what was already searched, or reviewing what was booked and why.
This skill is opt-in. Create entries when the user asks ("log this trip", "save this search"), or automatically only if the user has said they want every search logged. Don't append logging to searches uninvited.
trips/logs/YYYY-MM-DD_ORIGIN-DEST_short-label.md
YYYY-MM-DD — date the search was runORIGIN-DEST — airport codes. Multiple destinations: SFO-NRT-HND-SFOshort-label — 2–4 word slug describing the trip purposeExamples:
trips/logs/2026-08-11_SFO-CDG_paris-anniversary.md
trips/logs/2026-07-01_JFK-NRT_japan-ana-first.md
trips/logs/2026-09-02_SFO-OSL_oslo-work-trip-booked.md
Every trip log file uses this structure. Sections marked required must always be present. Others only when relevant.
---
date_searched: YYYY-MM-DD # required
origin: XXX # required
destinations: [XXX, XXX] # required
travel_dates: YYYY-MM-DD to YYYY-MM-DD # required
cabin: business / premium / economy # required
status: researched # required: researched | booked | completed | cancelled
booked_option: null # fill in when booked: carrier, miles/cash, date
tags: [tag1, tag2] # freeform
points_at_search: # snapshot at search time — one key per program the user holds
example_program: 0
---
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.