How do I install the Travel Prep skill?

Run npx skillmds@latest add quixiai/travel-prep in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Travel Prep safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Travel Prep?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Travel Prep free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Travel Prep?

quixiai (@quixiai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Travel Prep by quixiai — Agent Skill

Name: Travel Prep
Author: quixiai

File contents

Travel Preparation

Build a source-grounded plan for a trip without turning planning into an unauthorized booking or purchase.

Workflow

Establish the trip. Confirm the destination, dates, travelers, origin, time zone, and any constraints the user supplied. If several calendar events could be the trip, show the candidates and ask which one they mean.
Gather owned facts. Read the relevant calendar events and, when useful, search email for booking confirmations. Treat confirmation numbers, addresses, times, and baggage or check-in rules as sensitive. Include them only when they help the user and do not persist them unless asked.
Recover personal context. Use recall for stated preferences, accessibility needs, previous promises, and destination context. Never convert a weak or unrelated memory into a trip requirement.
Research what can change. Use web_search and web_fetch for current entry requirements, transit disruptions, opening hours, weather-dependent advice, and other time-sensitive facts. Name the source and checked date. Separate official requirements from suggestions.
Build the brief. Present a chronological itinerary, unresolved gaps, departure checklist, local logistics, reservations, contacts, and a short contingency section. Preserve local times and label time zones when ambiguity is possible.
Offer actions. Propose calendar blocks or tasks after the brief. Create or update them only when the user explicitly chooses the exact action and destination system. Prefer the local backlog when no external task service is configured.

Control and Failure Boundaries

Never book, buy, cancel, check in, or submit traveler information. This skill prepares; it does not transact.
Never silently move an event or infer a missing date, traveler, currency, visa status, or reservation.
A request to "prepare" authorizes reading and drafting, not calendar changes, outbound mail, or task creation.
If calendar or email access is unavailable, continue from details the user provides and state exactly what is missing. Give the concrete setup or input needed next instead of ending at an error.
Keep unknowns visible. A short plan with an explicit gap is better than a complete-looking fiction.

---name: travel-prepdescription: Turn calendar events, confirmations, current research, and personal context into a practical trip brief---# Travel PreparationBuild a source-grounded plan for a trip without turning planning into an unauthorized booking or purchase.## Workflow1. **Establish the trip.** Confirm the destination, dates, travelers, origin, time zone, and any constraints the user supplied. If several calendar events could be the trip, show the candidates and ask which one they mean.2. **Gather owned facts.** Read the relevant calendar events and, when useful, search email for booking confirmations. Treat confirmation numbers, addresses, times, and baggage or check-in rules as sensitive. Include them only when they help the user and do not persist them unless asked.3. **Recover personal context.** Use `recall` for stated preferences, accessibility needs, previous promises, and destination context. Never convert a weak or unrelated memory into a trip requirement.4. **Research what can change.** Use `web_search` and `web_fetch` for current entry requirements, transit disruptions, opening hours, weather-dependent advice, and other time-sensitive facts. Name the source and checked date. Separate official requirements from suggestions.5. **Build the brief.** Present a chronological itinerary, unresolved gaps, departure checklist, local logistics, reservations, contacts, and a short contingency section. Preserve local times and label time zones when ambiguity is possible.6. **Offer actions.** Propose calendar blocks or tasks after the brief. Create or update them only when the user explicitly chooses the exact action and destination system. Prefer the local backlog when no external task service is configured.## Control and Failure Boundaries- Never book, buy, cancel, check in, or submit traveler information. This skill prepares; it does not transact.- Never silently move an event or infer a missing date, traveler, currency, visa status, or reservation.- A request to "prepare" authorizes reading and drafting, not calendar changes, outbound mail, or task creation.- If calendar or email access is unavailable, continue from details the user provides and state exactly what is missing. Give the concrete setup or input needed next instead of ending at an error.- Keep unknowns visible. A short plan with an explicit gap is better than a complete-looking fiction.

Frequently asked questions

Travel Prep