skandm
UserA Claude-powered trip planning workspace template — skills for route planning, food/stay scouting, itinerary building, and mid-trip replanning
Categories
Indexed Skills (5)
itinerary-builder
Assemble a trip's day-by-day schedule once route, stays, and food are mostly decided. Trigger when the user says "build the itinerary" (or equivalent), when trips/<trip>/trip.md's Route/Stays/Food sections are largely settled, or during the itinerary phase of "plan my whole trip" (travelers -> route -> stays/food -> itinerary). Assembles departure times, drive blocks with breaks, meal stops, check-ins, and anchor activities, respecting traveler logistics like early bird/night owl rhythms and motion-sickness breaks. Flags unresolved blockers instead of guessing, and flips trip status planning -> ready when complete.
replanner
Handle mid-trip disruptions to an in-progress trip without losing the plan. Trigger when the user reports a change during an in-progress trip ("I-70 is closed", "we're too tired to drive 6h tomorrow", "the hotel cancelled on us"), or explicitly asks to re-plan from a given day ("re-plan from Thursday onward"). Reads trips/<trip>/trip.md as ground truth (the user may have hand-edited it on the road), changes only the disruption-affected segments/days, shows a before/after diff before writing, and logs a dated entry explaining what changed and why. Never silently drops hard traveler constraints or hard deadlines.
route-planner
Turn an origin, destination, and dates into a day-by-day driving route. Trigger when the user asks to plan a road trip ("plan a road trip from Chicago to Denver"), when a new trip folder is being created, or when an existing trips/<trip>/trip.md has an empty or tentative Route section. Reads profiles/travelers.md for driving limits, motion sickness, and who can share driving, and trip.md Parameters for dates and style. Proposes a fastest option plus 1-2 scenic options built around stops matched to the travelers' interests, each stated with total drive time, tolls, notable-stop facts, and food picks along the way, then writes the chosen route (per-day segments, decision date) and rejected options (with reason) back into trip.md.
traveler-profiles
Interview the user about who is traveling and record the results in profiles/travelers.md — the shared profile file every trip-planning skill reads. Use this skill whenever traveler profiles are missing, incomplete, or stale; whenever profiles/travelers.md still has status template; whenever the user mentions setting up profiles, who's coming on a trip, a new travel companion, or any change to someone's dietary needs, allergies, health constraints, or travel preferences ("Maya's vegetarian now", "we're bringing the kids this time", "my dad is joining and he can't do stairs"). Also use it when another planning task (routes, food, hotels, packing) needs traveler information that isn't on file yet — run this first rather than asking ad-hoc questions.
trip-exporter
Render a trip's settled plan into a self-contained, shareable HTML itinerary page. Trigger when the user asks to export, share, print, or "make a page for" a trip ("export the Cape May trip", "make something I can send my mom", "give me a printable itinerary"), or as an offer right after itinerary-builder flips a trip to status ready. Reads trips/<trip>/trip.md as the only content source, scrubs traveler-profile rationale (health, dietary, mobility reasons never leave trip files), writes trips/<trip>/itinerary.html from the bundled template, and optionally publishes it as a private claude.ai Artifact link when that tool is available. The export is derived output — trip.md stays the source of truth and the page is regenerated, never hand-maintained.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.