trip-log

# 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 # 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, ta...