moonlight-lupin/agent-skills / productivity/travel-itinerary
travel-itinerary
VerifiedUse when the user needs a business-trip itinerary built, updated, shared, or exported — create, update, sanitize, route, and export structured business-trip itineraries from booking confirmations, emails, tickets, PDFs, screenshots, calendar invites, or notes. Covers day-by-day itinerary generation, privacy-safe sharing, route links, and Markdown/PDF/DOCX/Google Doc/ICS exports.
| File | Kind | Size |
|---|---|---|
| .gitignore | other | 139 B |
| SKILL.md | skill md | 12.9 KB |
| examples/tokyo-trip.md | markdown | 24.1 KB |
| references/exports.md | markdown | 9.2 KB |
| references/node-types.md | markdown | 10.4 KB |
| references/privacy.md | markdown | 5.7 KB |
| references/routing.md | markdown | 7.1 KB |
| scripts/itinerary_utils.py | script | 8.9 KB |
| templates/itinerary-schema.yaml | config | 5.7 KB |
| tests/test_itinerary_utils.py | script | 3.0 KB |
references/exports.md
View on GitHub# Exports — Templates and Formats
This file defines the output formats. Pick the variant that matches the
audience (see `references/privacy.md` for what to include vs hide per audience).
## Contents
- File naming
- Output location
- Internal full — Markdown template
- Team-share — Markdown template
- Executive summary — Markdown template
- Travel-admin — Markdown template
- Chat-ready — plain text
- Calendar `.ics` export
- Export workflow
## File naming
```text
{YYYY-MM-DD}_{destination_slug}_business_trip_itinerary.md # internal full
{YYYY-MM-DD}_{destination_slug}_business_trip_team_share.md # team-share
{YYYY-MM-DD}_{destination_slug}_business_trip_exec_summary.md # exec summary
{YYYY-MM-DD}_{destination_slug}_business_trip_admin.md # travel-admin
{YYYY-MM-DD}_{destination_slug}_business_trip.ics # calendar
{YYYY-MM-DD}_{destination_slug}_business_trip_chat.txt # chat-ready
```
`{YYYY-MM-DD}` is the trip's start date. `{destination_slug}` is the primary
destination city, lower-case, hyphenated (e.g. `tokyo`, `kuala-lumpur`).
## Output location
Save deliverables to the user's selected folder or agreed workspace, not to the
scratchpad. Working drafts and intermediate YAML can live in the scratchpad.
After writing, present files using the delivery method your environment supports:
- Chat / messaging environments: send the local file directly using the platform's file-attachment mechanism.
- CLI / desktop environments: provide the absolute file path or a supported local-file link.
- Cloud-doc exports (Google Docs / Drive, etc.): provide the verified share URL.
## Internal full — Markdown template
```markdown
# {Trip Title}
**Dates:** {start_date} – {end_date}
**Destination:** {rough_destination}
**Travel party:** {travellers}
**Purpose:** {purpose}
**Prepared:** {prepared_date}
## Quick Summary
- **Hotel / base:** {hotel_name_and_dates}
- **Arrival:** {arrival_summary}
- **Departure:** {departure_summary}
- **Main meeting location:** {main_meeting_location}
- **Notes:** {high_level_notes}
## Open Questions / Missing Details
- [ ] {missing_detail_1}
- [ ] {missing_detail_2}
## Day 1 — {weekday}, {date} ({local_timezone})
**Overnight stay:** {hotel_name / address / check-in notes}
### {HH:MM} — {node title}
- **Type:** {node_type}
- **Location:** {location_name}, {address}
- **Participants:** {participants}
- **Reference:** {confirmation_ref_if_appropriate}
- **Cost:** {amount} {currency} ({payer}) — *omit line if unknown*
- **Notes:** {notes}
- **Map:** {maps_url_if_available}
### Transfer / route to next item
- **From:** {origin}
- **To:** {destination}
- **Estimated travel:** {duration} by {mode}
- **Map:** {directions_url}
## Day 2 — {weekday}, {date} ({local_timezone})
...
## Cancelled / no longer happening
- ~~{HH:MM} — {cancelled node title}~~ — {reason if known}
## Reference Details
### Flights / Trains
...
### Accommodation
...
### Restaurants / Events / Tickets
...
## Source Notes
- {source summary, not full raw email unless asked}
```
## Team-share — Markdown template
Same skeleton as internal-full, but apply the redactions from
`references/privacy.md`:
- Drop the **Source Notes** section.
- Drop **Reference Details > Flights/Trains** confirmation refs unless flights
are shared by the team.
- Drop `private_notes`.
- Cost lines: omit (per the privacy matrix — costs are not shared by default).
Override only on explicit user request, e.g. when sharing a per-traveller
budget summary.
- Cancelled nodes: omit entirely (do not show the strike-through section).
## Executive summary — Markdown template
One page, no longer than ~250 words.
```markdown
# {Trip Title} — {start_date} to {end_date}
**Destination:** {city, country}
**Travel party:** {names}
**Purpose:** {one-line purpose}
## Schedule
| Date | AM | PM | Overnight |
|-----------------|-------------------------------------|-------------------------------------|-----------|
| {date, weekday} | {top item} | {top item} | {hotel} |
| {date, weekday} | {top item} | {top item} | {hotel} |
## Key meetings
- {date HH:MM} — {who with} @ {short location}
- {date HH:MM} — {who with} @ {short location}
## Logistics
- **Arrival:** {flight no., HH:MM at {airport}}
- **Departure:** {flight no., HH:MM from {airport}}
- **Hotel:** {name}, {short address}
```
## Travel-admin — Markdown template
For assistants / ops. Reference-heavy.
```markdown
# {Trip Title} — Travel Admin Pack
## Bookings
| Type | Date | Provider | Ref | Cost | Cancellation deadline |
|--------|--------------|--------------|-------------|---------------|------------------------|
| Flight | {date} | {airline} | {ref} | {amt} {cur} | {date or n/a} |
| Hotel | {dates} | {hotel} | {ref} | {amt} {cur} | {date or n/a} |
## Supplier contacts
- {Provider}: {phone}, {email}
## Traveler assignment
- {Name}: {flights/hotel/meetings}
## Expense routing
- {item} → {billable_to / cost-centre}
## Open admin items
- [ ] {item, owner, due}
```
## Chat-ready — plain text
For WhatsApp / Telegram / Slack. Short. No sensitive details.
```text
{Trip Title} — {dates}
{Day 1 date}
• {HH:MM} {short item}
• {HH:MM} {short item}
• Overnight: {hotel/base}
{Day 2 date}
• {HH:MM} {short item}
• {HH:MM} {short item}
• Overnight: {hotel/base}
Notes:
• {important note}
• {map/share link if any}
```
## Calendar `.ics` export
Use one `VEVENT` per timed node. Skip `note`, `free_time`, and untimed `poi`
nodes by default unless the user asks to include them. `admin` nodes with a
`due_at` become `VTODO`s (Apple Calendar and Outlook support VTODO; Google
Calendar ignores VTODO — fall back to a 15-minute VEVENT if the user uses
Google Calendar).
Required structure:
```ics
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//travel-itinerary skill//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:Asia/Hong_Kong
BEGIN:STANDARD
DTSTART:19700101T000000
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
TZNAME:HKT
END:STANDARD
END:VTIMEZONE
BEGIN:VTIMEZONE
TZID:Asia/Tokyo
BEGIN:STANDARD
DTSTART:19700101T000000
TZOFFSETFROM:+0900
TZOFFSETTO:+0900
TZNAME:JST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:flight-001@travel-itinerary
DTSTAMP:20260610T120000Z
DTSTART;TZID=Asia/Hong_Kong:20260612T081000
DTEND;TZID=Asia/Tokyo:20260612T134000
SUMMARY:CX548 HKG → HND
LOCATION:Hong Kong International Airport (HKG) → Tokyo Haneda (HND)
DESCRIPTION:Cathay Pacific CX548. Ref ABC123. Terminal 1 → Terminal 3.
CATEGORIES:Travel,Flight
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR
```
Rules:
- `UID` — use the node `id` + `@travel-itinerary` so re-exports update rather
than duplicate.
- `DTSTART` / `DTEND` — for same-timezone nodes, use `TZID=` with
`node.timezone` (fall back to `day.local_timezone`, then
`trip.timezone_default`). For cross-timezone travel, use `timezone_start`
for `DTSTART;TZID=` and `timezone_end` for `DTEND;TZID=`. Always include a
matching `VTIMEZONE` block for every `TZID` used.
- `STATUS:` map from the node `status`: `confirmed → CONFIRMED`,
`tentative → TENTATIVE`, `cancelled → CANCELLED`, `unknown → CONFIRMED`
(most permissive default).
- `CATEGORIES:` derive from `type` and `subtype` (e.g. `Travel,Flight`,
`Meeting,Client`).
- `DESCRIPTION:` include `provider`, `confirmation_ref`, and key practical
notes. Escape `\n` with `\\n`, commas with `\\,`, semicolons with `\\;`.
Apply the same privacy rules as the equivalent Markdown variant — by default
the `.ics` matches the **internal full** variant; produce a separate
`*_team_share.ics` if needed.
- Lines must not exceed 75 octets; fold continuation lines with a leading
space (RFC 5545). Prefer generating `.ics` with CRLF line endings.
- Each `VEVENT` must include at least `UID`, `DTSTAMP`, `DTSTART`, `SUMMARY`,
and `END:VEVENT`.
- Each `VTODO` must include at least `UID`, `DTSTAMP`, `SUMMARY`, and
`END:VTODO`; use `DUE` when there is a deadline.
- Final line is `END:VCALENDAR`.
Untimed admin items as `VTODO`:
```ics
BEGIN:VTODO
UID:admin-001@travel-itinerary
DTSTAMP:20260610T120000Z
DUE;TZID=Asia/Tokyo:20260612T230000
SUMMARY:Online check-in opens for return flight
STATUS:NEEDS-ACTION
END:VTODO
```
## Export workflow
1. Confirm target audience (internal / team-share / exec / admin).
2. Confirm format (Markdown / PDF / DOCX / Google Doc / chat / `.ics`).
3. Apply redactions per `references/privacy.md`.
4. Render from the canonical YAML — do not re-derive facts from source emails
at this step. Apply node-level `visibility` first, then field-level
redactions per `references/privacy.md`.
5. Write file to the user's selected folder using the naming convention above.
6. Verify the file exists and opens cleanly before telling the user it's ready.
For `.ics`, use `python3 scripts/itinerary_utils.py ics-check <file>` or an
equivalent sanity check: `BEGIN:VCALENDAR` … `END:VCALENDAR` present,
balanced `BEGIN`/`END` blocks, required VEVENT/VTODO fields present, and
every used `TZID` has a matching `VTIMEZONE` block.Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |