plan-trip
Skill14 starsChanged 3 months agoMITView on GitHub
Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Plan Trip”. A useful skill states the six fields from Skills and routines. A trip needs a sanity-checked itinerary — flights, stays, connections, calendar collisions — and must stop before booking or paying. No booking, cart, or payment was completed. Prices have a URL and a fetch time. Calendar was not changed. Missing tickets are listed as missing, not invented. Itinerary…
3 other projects use a version of this.
Adopted by
Most recently taken up by
- christian93kg/travel-agenttheir own version, first seen Aug 22, 2026
- aakashg/parenting-ostheir own version, first seen Aug 13, 2026
- bethron/travel-conciergetheir own version, first seen Jul 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- aakashg/parenting-os★ 1same name
- bethron/travel-concierge★ 1same name
- christian93kg/travel-agent★ 1same 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 repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- convert/claude.mdCLAUDE.md
- docs/llms.txtllms.txt
- audit-subscriptionsSkill
- cited-researchSkill
- cloud-bill-noteSkill
- collate-feature-asksSkill
- coordinate-launchSkill
- daily-digestSkill
- defend-calendarSkill
- design-bot-templateSkill
- detect-docs-driftSkill
- diff-competitorsSkill
- draft-call-followupSkill
- draft-changelogSkill
- draft-issueSkill
- draft-newsletterSkill
- draft-security-answersSkill
- draft-sqlSkill
- draft-support-replySkill
- garden-memorySkill
- harden-repoSkill
- incident-timelineSkill
- install-teamSkill
- interrogate-assumptionsSkill
- investigate-perfSkill
- log-promisesSkill
- package-evidenceSkill
- prep-meetingSkill
- queue-socialSkill
- ramp-new-hireSkill
- rank-account-healthSkill
- recommend-media-reallocSkill
- reconcile-expensesSkill
- remix-contentSkill
- reproduce-bugSkill
- research-accountsSkill
- review-pr-riskSkill
- route-workSkill
- sanitize-shareSkill
- scout-x-threadsSkill
- source-talentSkill
- sweep-ciSkill
- triage-inboxSkill
- vendor-renewalsSkill
- watch-aeoSkill
- watch-brandSkill
- weekly-saas-financeSkill
- write-win-lossSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
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 23
Search mail for tickets, holds, or hotel mail already in play.
- Distinctive: line 24
Check calendar for meetings that overlap travel days.
- Distinctive: line 30
No booking, cart, or payment was completed.
- Distinctive: line 40
Do not book, pay, hold a card, or email a vendor.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Plan Trip
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Plan Trip”.
A useful skill states the six fields from Skills and routines.
1. When to use it
A trip needs a sanity-checked itinerary — flights, stays, connections, calendar collisions — and must stop before booking or paying.
2. Required inputs and access
- Destination, dates, constraints (budget band, airports, party size)
- Gmail for existing tickets, holds, or vendor mail
- Google Calendar for collisions in the travel window
3. Sequence of work
- Restate dates, origin, destination, and constraints. Confirm if any are missing.
- Search mail for tickets, holds, or hotel mail already in play. Quote confirmation numbers only from those messages.
- Check calendar for meetings that overlap travel days.
- Compare public flight and stay options the browser can reach. Quote prices with timestamps. Do not log into a booking site to pay.
- Build an itinerary sanity pack covering gaps, tight connections, visa/timezone notes, collisions, and a ranked option table.
4. How to validate the result
No booking, cart, or payment was completed. Prices have a URL and a fetch time. Calendar was not changed. Missing tickets are listed as missing, not invented.
5. What to return
Itinerary pack: proposed days, option table with URLs, collisions, gaps, and a do-not-book reminder. Action log.
6. What requires approval
Do not book, pay, hold a card, or email a vendor. Do not change calendar events. Do not apply for visas.
Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.
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.