Planning a trip you can actually follow isn't a list of sights from a guidebook — it's checking opening hours, ticket prices, and the logistics between points. Those details are what usually let you down: the museum is closed on Mondays, the ticket price has changed, and two interesting places turn out to be at opposite ends of the city, so the day is lost to getting around.
The "Trip planner" skill builds a route from fresh data: it finds what to see and what's happening on your dates, opens the official pages of key places for current hours and prices, and lays it all out day by day with geography in mind. It relies on pages it read, not on memory, and tags every price and schedule with the date it checked — because those are what change most often.
What it does
Given a destination, dates, and your interests, the skill builds a day-by-day route: the main places and events, verified opening hours and ticket prices, and the logistics between points. It saves the finished route to the library.
How it works
- The skill searches for what to see and what's happening on your dates: the main places, events, and seasonal quirks — what's closed, what's in bloom, what gets rained out. That way the route reflects not just the "top sights" but the specific moment of your trip.
- It then opens the official pages of 3–5 key places and takes opening hours, ticket prices, and rules — from the official sites, not aggregators, where schedules and prices often go stale.
- The skill lays out the route day by day: 2–4 stops per day arranged by geography so you don't cross the whole city twice, with slack for food and rest. For each stop — why go, what it costs, how much time to budget, and how to get there from the previous one.
- It saves the finished route to the library in markdown, titled like "Trip to Kazan, September 12–14". If the essentials are missing — where and for how long — it first asks for them in one short message.
What you get
A day-by-day route appears in the library, and the chat returns a short summary: the skeleton of the route in one line per day, the total ticket budget, and 2–3 things worth booking ahead. Prices and hours are tagged with the date checked, and if an official site was unavailable, the skill notes that the data is from a secondary source — so you know what to re-check before you leave.
When to use it
When you're heading to an unfamiliar city and want a route you can actually walk, not a list of ten places with no tie to time or travel. It's useful for short weekend trips where you can't afford to lose a day to logistics, and for family travel, where opening hours and rest slack decide everything. It also works as a base you'll later tweak to taste — the skeleton is already built on facts, not on general impressions.