# Trip Plan

Plan a trip end to end (itinerary by day, a packing list to tick off, a budget, and the...

- Repository: https://github.com/nano-muse/nanoMuse (2980 stars)
- Category: Engineering
- License: GPL-3.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nano-muse/nanoMuse --skill trip-plan -g -a claude-code -y`
Codex: `npx skills add nano-muse/nanoMuse --skill trip-plan -g -a codex -y`
Cursor: `npx skills add nano-muse/nanoMuse --skill trip-plan -g -a cursor -y`
Gemini CLI: `npx skills add nano-muse/nanoMuse --skill trip-plan -g -a gemini-cli -y`

## Description

Plan a trip end to end (itinerary by day, a packing list to tick off, a budget, and the calendar checked for conflicts) as pages in the workspace. Use when the user is going somewhere for more than a day and wants a plan, an itinerary or a packing list.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Trip plan

Everything goes in `trips/<place>-<yyyy-mm>/` in the workspace: `itinerary.html`, `packing.html`, and `budget.csv` when money is discussed.

## Before anything

- You need: where, the dates (or roughly when and for how long), who is going, and what the trip is for (work, holiday, visiting someone). Ask for what is missing with **one** `ask_user` call, not one question at a time.
- `recall` the user's travel preferences (pace, budget, dietary needs, kids, mobility, what they hated last time). Follow them without asking again.
- `calendar` action=search for the trip dates: anything already on the calendar during the trip is a conflict to mention up front.

## Research

- `web_search` for: how to get there and around, the weather in that season, opening days of the two or three things worth seeing, and anything that must be booked ahead. Two or three searches, then stop; `web_fetch` a page only when the search result is not enough.
- Prices and times only from pages you actually read. If you did not find something, say "check" next to it rather than inventing a figure.
- Trains in China: real options come from the `12306__*` tools (the 12306 MCP server; the `train-tickets` skill says how; search only, no booking); the times and prices go into the itinerary and the budget. Without the server, the 12306 app on a connected phone the same way; without either, "check 12306" in the plan.
- Places and distances in China: when the `amap__maps_*` tools are there (the 高德 MCP server, see the `amap` skill), use them for the travel time between the day's places, the route to the station, and the forecast for the dates; the itinerary's "travel time between places" then comes from a map, not a guess.

## Itinerary (`itinerary.html`)

The rest: https://github.com/nano-muse/nanoMuse/blob/HEAD/nanomuse/skills/builtin/trip-plan/SKILL.md