Trip Plan

Organization

nano-muse

trip-plan

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.

Overview

Publisher	nano-muse
Repository	`nanoMuse`
Skill name	`trip-plan`
Stars	885
Forks	94
Bundled files	Instructions only
License	GPL-3.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by nano-muse on GitHub. Read the source before you install it.

Installation

Install the Trip Plan AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/trip-plan
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/nano-muse/nanoMuse.git /tmp/nanoMuse
mkdir -p .claude/skills
cp -r /tmp/nanoMuse/nanomuse/skills/builtin/trip-plan .claude/skills/trip-plan

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Trip Plan in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Trip Plan on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Trip Plan is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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`)

One card per day: date and weekday, the area of town, morning / afternoon / evening, travel time between places, one alternative for bad weather.
The first day is arrival and settling in; the last day ends when the transport leaves. Do not overfill: two anchors a day and free time.
A "Before you go" box: bookings, documents, connections to arrange, with dates.
Self-contained HTML, inline CSS, readable on a phone; no external resources.

Packing list (`packing.html`)

Grouped (documents, clothes for the weather you found, tech, toiletries, for the kids…), each item a checkbox that stays ticked when the page is reopened (localStorage).
Sized to the trip: the number of days, the weather, laundry or not.

Budget (`budget.csv`, when asked or when the user mentioned money)

Columns: item, when, estimated, currency, booked (yes/no), note. One row per transport leg, night, and day of food; totals the user can change.

Finish

Reply with the shape of the trip in three or four lines and the file names; point out the calendar conflicts and the two things to book first.
Offer, in one line, to make a goal from the "Before you go" list so the bookings get done and checked in on; if the user agrees, goals action=create with those steps and the departure date as the target.
Never book, pay or send anything yourself; drafting an event with calendar action=draft for the departure is fine.

Frequently asked questions

What does the Trip Plan AI skill do?

Why use Trip Plan on TypingMind?

Because you install it once and use it with any model. Trip Plan is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Trip Plan in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/trip-plan. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Trip Plan?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Trip Plan?

As many as you like. As long as a model supports skills, you can use Trip Plan with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Trip Plan AI skill free?

Yes. It is published on GitHub by nano-muse under the GPL-3.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Plan Canvas

affaan-m

CommunityPopular

Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or…

Improve Codebase Architecture

mattpocock

CommunityPopular

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Grilling

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Teach

Teach the user a new skill or concept, within this workspace.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Trip plan

Before anything

Research

Itinerary (itinerary.html)

Packing list (packing.html)

Budget (budget.csv, when asked or when the user mentioned money)

Finish

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

Itinerary (`itinerary.html`)

Packing list (`packing.html`)

Budget (`budget.csv`, when asked or when the user mentioned money)