plan-trip
Skill1 starsChanged 3 months agoMITView on GitHub
Run a trip from a short intake conversation to a filled trip file — architecture (hub-and-spoke vs. circuit), a day skeleton respecting the 8-day novelty peak, threat calibration, and a gear delta checklist. Use when the user says "plan a trip", "help me plan X days in Y", "new trip", "plan my trip to <place>", or asks to scope/organize an upcoming trip.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- cobusgreyling/grok-bot-templatestheir own version, first seen Aug 29, 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
- cobusgreyling/grok-bot-templates★ 14same name
- aakashg/parenting-os★ 1same name
- bethron/travel-concierge★ 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 repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
PROTOCOL.mdin this folder is the authoritative flow: Read it before running the skill — it has the actual questionnaire, the decision … - Very specific: line 26
Never edits anything under frameworks/ or playbooks/ — those are read-only reference for this skill, not output targets.
- Very specific: line 28
Never invents bookings, prices, or confirmations as fact.
“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
Turns a few answered questions into a filled trip file, built from the frameworks and playbooks in this repo rather than generic travel advice.
What it does
Runs intake → architecture → itinerary skeleton → threat calibration → gear
delta, in that order, pulling each stage's method from the relevant
frameworks/ or playbooks/ file rather than reasoning from scratch.
PROTOCOL.md in this folder is the authoritative flow. Read it before
running the skill — it has the actual questionnaire, the decision rules for
each stage, and the failure-mode shortcuts (fully-fixed itinerary, working
month). This file is the pointer, not the spec.
Output contract
- Writes
trips/<destination-slug>-<duration>d/trip.md, built fromtrips/_template/trip.md. - Never edits anything under
frameworks/orplaybooks/— those are read-only reference for this skill, not output targets. - Never invents bookings, prices, or confirmations as fact. Leave
Open questionsand theBookingstable honest about what's still unresolved.
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.

