← ClaudeAtlas

travel-planninglisted

Turn a trip request into a structured, editable travel plan — a day-by-day itinerary plus a reconciled budget — as a Markdown document. Use this whenever the user wants to plan a trip, vacation, or holiday: "help me plan a week in Portugal", "build an itinerary for 5 days in Tokyo with my kids", "map out a road trip", "we have $3k for a long weekend, what can we do", "organize my Japan trip", or any request to structure travel across days and a budget — even if they don't say the word "itinerary". This is a reasoning-and-structuring skill: it plans, paces, and budgets, and will do a best-effort web lookup to anchor cost estimates in typical or seasonal prices (labeled, sourced, not live quotes). It does NOT make bookings, transact, or read real-time seat/room inventory — steer those to the actual booking sites and keep planning.
kevin-burns/claude-skills · ★ 7 · Data & Documents · score 78
Install: claude install-skill kevin-burns/claude-skills
# Travel Planning Turn a loose trip idea into a plan someone can actually act on: a paced day-by-day itinerary and a budget that's been reconciled against what the traveler can spend. The output is a single editable Markdown file they can tweak by hand afterward. ## What this skill is — and the hard boundary The durable value here is **structure and judgment**: sequencing days so they flow, clustering things by geography so no day zig-zags across a city, matching pace to the travelers, and turning a budget number into a defensible allocation. That's what an LLM is genuinely good at and what a traveler staring at a blank page actually needs. **It does not book, and it never presents a number as a live quote it read off a site.** No reservations, no "this exact flight is $142 right now", no availability or seat checks. Booking needs accounts, payment, and liability a skill shouldn't take on; real-time fares render live and usually can't be fetched reliably anyway. What it *can* do — and should, when it helps — is **ground its estimates in retrieved data**: a best-effort web lookup for *typical / seasonal* price levels for the route and dates, so the budget is anchored in something real rather than guessed (see Step 3a). That's grounding, not a live quote, and it's always labeled with an as-of date, a source, and "verify live." When cost comes up, this skill gives **clearly-labeled estimate ranges** (grounded where possible) and tells the traveler where to check current pri