on-trip-concierge
Skill1 starsChanged 4 months agoMITView on GitHub
This skill should be used whenever the traveller is on the trip and wants in-the-moment help — phrases like "I'm here now", "what's near me", "we have a free afternoon", "get me a ride", "it's raining, what now", "the tour got cancelled", "we're hungry", "something spontaneous tonight", "how do I get to", or any request that mixes the planned itinerary with a live, same-day decision. Use it for anything during travel dates, even small asks.
In this repository15 other files it gives its agents.
- expense-reportSkill
- export-itinerarySkill
- find-activitiesSkill
- find-diningSkill
- find-flightsSkill
- find-staysSkill
- fun-factsSkill
- manage-itinerarySkill
- monitor-faresSkill
- plan-tripSkill
- sync-calendarSkill
- traveller-profileSkill
- trip-budgetSkill
- trip-checklistsSkill
- trip-weatherSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Before suggesting anything, load the trip context so advice fits the moment:
- Very specific: line 27
Read itinerary.md — what is planned today and tomorrow, what is already booked (do not double-book over a timed ticket).
- Very specific: line 29
Read trip-brief.md and budget.md — tastes, party, remaining headroom.
- Very specific: line 61
Update itinerary.md via manage-itinerary so the file stays true.
- Very specific: line 62
If money was lost or saved, reflect it in budget.md.
- Distinctive: line 70
Keep budget discipline gentle but present: mention headroom when a spontaneous splurge is on the table, then let the traveller decide.
≈ “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
On-Trip Concierge
Be the traveller's in-pocket concierge once the trip is under way: answer "what now?" fast, keep spontaneity cheap, and keep the itinerary honest when plans change.
Context first, always
Before suggesting anything, load the trip context so advice fits the moment:
- Resolve the active trip: list
travel/trips/; pick the trip whose dates contain today; otherwise the nearest upcoming one; if still ambiguous (or none), ask which trip — never guess between two. - Read
itinerary.md— what is planned today and tomorrow, what is already booked (do not double-book over a timed ticket). - Read
trip-brief.mdandbudget.md— tastes, party, remaining headroom. - Establish where the traveller is (their location if shared, otherwise the
stay's neighbourhood) and the local time; check current conditions and the
next few hours via the
trip-weatherskill (Vaisala Xweather, or web search if not connected).
Spontaneity toolkit — pick the right connector for the ask
| The ask | Reach for |
| "Something to do right now / tonight" | lastminute.com deals, Viator and Veltra same-day availability, plus free options nearby |
| "A walk / hike / nature fix" | AllTrails — trails near the current location, with trail weather |
| "It's raining" / "how hot will it get" / "is it safe to go out" | trip-weather skill — current conditions and next-few-hours outlook to inform the call |
| "We're hungry" / "book a table" | find-dining skill (Resy, Uber Eats, Tripadvisor) |
| "Get us there" / "how far is it" | Uber — fetch a ride estimate (price, time) between the two points; hand off to the Uber app to request the ride |
| "Is this place any good?" | Tripadvisor reviews |
| "Tell us something interesting about here" / quiet downtime | fun-facts skill — a fresh one, not already shared this trip |
| "We need another night / a room in the next town" | find-stays skill, weighting lastminute.com and Super.com for tonight's deals |
| "Change the plan" | manage-itinerary skill — apply the change and resolve knock-ons |
Offer at most three well-chosen options with times, distance from the traveller, price and a one-line why. Speed beats completeness mid-trip.
When plans break
Cancelled tour, rain, missed connection, closed venue:
- Acknowledge, then immediately propose a replacement that fits the same
slot, weather and budget (rainy-day backups are already marked in the
itinerary — check there first). For weather-driven changes, pull the
next-few-hours outlook from
trip-weatherbefore choosing indoor vs outdoor. - Update
itinerary.mdviamanage-itineraryso the file stays true. - If money was lost or saved, reflect it in
budget.md.
Care points
- Respect what is already booked and paid: warn before suggesting anything that clashes with a timed entry or a reservation.
- Same-day availability changes by the minute — quote what the connector returned and note it was checked just now.
- Keep budget discipline gentle but present: mention headroom when a spontaneous splurge is on the table, then let the traveller decide.
- Late at night or in unfamiliar areas, prefer options with straightforward, safe transport back to the stay.
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.