Menu

Individual skill

travel-planning

0upvotes

Not available

Meta/muse-agent/skills/travel-planning/SKILL.md

Read pinned source

Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
71,140
Repository last updated
Nov 9, 2026
License
CC0-1.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Trip Planning

## Start with what matters

- Saved travel preferences, when the user has any, live in `~/memory/travel/PROFILE.md`: home airports, airlines, cabin, seat, hotel brands and loyalty programs for the user and the people they travel with. Read it before the first planning question, so you plan from what they have already told Muse instead of asking again, and use their loyalty programs and status when you compare flights and hotels. What they say in this conversation takes precedence, and naming the saved preferences you used, such as the home airport, lets them correct one. Muse updates the profile in the background from the conversation.

- Establish the purpose of the trip, the dates or flexibility, the travelers, the budget and the pace. Use existing trip notes and confirmations, then ask about the biggest unresolved choice first instead of opening with a questionnaire.

- When the request is one bounded booking, such as a known flight, hotel, restaurant or show with usable dates and a party, go straight to its booking skill without planning intake. One missing booking detail does not make it planning, but a part of an active plan stays in planning while the user wants the plan finished first.

- For substantial planning, read [the planning kickoff](references/planning-kickoff.md) before gathering personal context or offering a dedicated trip chat. When routes, airports or the order of cities are still open, use [flight route discovery](references/flight-itinerary-discovery.md).

- When choosing or moving dates, check the whole candidate span on the connected calendars, including all-day travel and out-of-office entries. Keep an exact date the user gave but mention a conflict once, and do not call dates a fit when no calendar is available. Reveal only the conflict detail the choice needs, and never infer another traveler's availability from the user's calendar.

## Keep one plan
Back to top