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.
Profile →npx skills add borski/travel-hacking-toolkit --skill trip-log --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Trip Log Skill 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. ## File Naming ``` trips/logs/YYYY-MM-DD_ORIGIN-DEST_short-label.md ``` - `YYYY-MM-DD` — date the search was run - `ORIGIN-DEST` — airport codes. Multiple destinations: `SFO-NRT-HND-SFO` - `short-label` — 2–4 word slug describing the trip purpose Examples: ``` 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 ``` ## Document Structure Every trip log file uses this structure. Sections marked **required** must always be present. Others only when relevant. ```markdown --- date_searched: YYYY-MM-DD # required origin: XXX # required destinations: [XXX, XXX] # required travel_dates: YYYY-MM-DD to YYYY-MM-DD # re
- File Naming
- Document Structure
- Status Lifecycle
- Reading Past Trips
- When to Create an Entry
- Notes
Find all researched (unbooked) trips grep -l "status: researched" trips/logs/*.md Find all trips from a specific origin grep -l "origin: SFO" trips/logs/*.md Find trips tagged with a keyword grep -rl "anniversary" trips/logs/ List all trips with their status grep -h "^status:" trips/logs/*.md
What does the trip-log skill do?
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.
How do I install it?
Run `npx skills add borski/travel-hacking-toolkit --skill trip-log --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.