trip
Skill2 starsChanged 8 months agoMITView on GitHub
Trip planning with day-by-day itineraries and local recommendations
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ziweiCai123/claude-skillstheir own version, first seen Nov 1, 2026
- nbirkner/digital-braintheir own version, first seen Apr 12, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ziweiCai123/claude-skills★ 1same name
- nbirkner/digital-brain★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- checkinSkill
- code-reviewSkill
- eod-reviewSkill
- journalSkill
- meeting-prepSkill
- morning-kickoffSkill
- plantsSkill
- read-laterSkill
- recipeSkill
- researchSkill
- standupSkill
- todoSkill
- watchlistSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Before generating the itinerary, ask about (keep it to one quick question):
- Distinctive: line 36
If the user already provided preferences in their initial message, skip this step.
- Distinctive: line 40
Create a day-by-day plan. For each day include:
- Distinctive: line 60
After the itinerary, include:
- Distinctive: line 71
Using {{notes}}: Create a page titled "[Destination] Trip — [Dates]" with the full itinerary.
- Distinctive: line 77
After presenting the plan, ask: "Want to adjust anything — swap days, add rest time, more food spots?"
- Distinctive: line 82
Add more/fewer restaurant recommendations
- Distinctive: line 84
Add a day trip to a nearby town
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Trip
Plan trips with day-by-day itineraries, food recommendations, and logistics. Iteratively refine until it feels right.
Trigger Phrases
- "trip to [place]"
- "plan trip"
- "travel to [place]"
- "vacation to [place]"
Workflow
Step 1: Gather Basics
Extract from the user's message or ask:
- Destination
- Dates (or duration: "5 days in October")
- Travelers (solo, couple, family, group)
Step 2: Ask Preferences
Before generating the itinerary, ask about (keep it to one quick question):
- Pace: Packed schedule vs. relaxed with downtime
- Vibe: Adventure, culture, food, relaxation, nightlife, nature
- Budget: Budget-friendly, mid-range, or splurge
- Interests: Any must-dos or must-avoids
If the user already provided preferences in their initial message, skip this step.
Step 3: Generate Itinerary
Create a day-by-day plan. For each day include:
- Morning / Afternoon / Evening blocks
- Specific place names (neighborhoods, landmarks, restaurants)
- Practical notes: how to get there, estimated time, reservation tips
- One food recommendation per meal slot
Structure:
### Day 1: [Theme — e.g., "Historic Center"]
**Morning**: [Activity] — [details, location]
**Lunch**: [Restaurant/area] — [what it's known for]
**Afternoon**: [Activity]
**Dinner**: [Restaurant/area]
**Evening**: [Optional activity or downtime]Step 4: Add Logistics Section
After the itinerary, include:
- Getting around: Best transport options (metro, rideshare, walking, rental car)
- Neighborhoods to stay in: 2-3 options with trade-offs (central vs. budget vs. vibe)
- Practical tips: Currency, tipping norms, language basics, safety notes
- Packing notes: Weather-specific or activity-specific gear
Step 5: Save
Save the complete plan.
Using {{notes}}: Create a page titled "[Destination] Trip — [Dates]" with the full itinerary.
Markdown fallback: Save to ~/.ai-workflow/trips/[destination]-[date].md.
Step 6: Iterate
After presenting the plan, ask: "Want to adjust anything — swap days, add rest time, more food spots?"
Accept refinements and update the saved plan. Common adjustments:
- Swap out activities
- Add more/fewer restaurant recommendations
- Shift pace (more downtime, more sightseeing)
- Add a day trip to a nearby town
Examples
Start planning:
trip to Lisbon, 4 days in May
Nice — Lisbon in May is great weather. Quick question before I build the itinerary:
What's your vibe? (adventure / food-focused / culture / relaxed mix)With preferences upfront:
plan a 5-day trip to Tokyo, food-focused, moderate budget, first time visiting
Generates a full 5-day itinerary focused on food neighborhoods (Tsukiji, Shinjuku, Shibuya), includes ramen rankings, izakaya recommendations, and a day trip to Kamakura.
Refine:
day 3 looks too packed, can we swap the temple visit for free time?
Updates Day 3 with a lighter schedule and re-saves the plan.
Quick trip:
weekend trip to Portland
Generates a 2-day plan with breweries, Powell's Books, food carts, and neighborhood walking routes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.