trip-exporterlisted

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.
skandm/trip-planner-template · ★ 0 · Data & Documents · score 72

Install: claude install-skill skandm/trip-planner-template

# Trip exporter This skill turns a trip's plan into a polished single-file HTML page the user can AirDrop to a co-traveler, print, or share as a link. It renders what `trip.md` has settled — it never plans, picks, or fills gaps. ## Step 1: Read trip.md — and only trip.md The export is built from `trips/<trip>/trip.md` alone. Do **not** pull content from `profiles/travelers.md` into the page — the export is the one file in a trip folder designed to leave the repo, so it must contain nothing that shouldn't (see Step 2). If the trip's `status` is still `planning`, say so and ask whether to export anyway. If yes, render the settled parts and mark unsettled slots honestly — a stay still `unbooked` becomes "Lodging: to be decided", a `_to scout_` meal becomes "Restaurant: to be decided". Never invent a placeholder that looks like a decision. **Running outside the repo** (a claude.ai chat with skills attached): ask the user to attach their `trip.md`, render the page from it, and return the HTML file directly in the conversation. No trip file, nothing to export — say so rather than improvising. ## Step 2: The scrub rule — what may leave the repo This page gets shared. Apply CLAUDE.md's privacy boundary to its content, not just to web searches: **Include** — the *what, where, when*: - Route summary, per-day segments, drive times, the notable-stop facts. - Chosen stays (name, check-in time, Maps link). - Chosen food (name, price tier, Maps/website links, dishes-to-try lists). -