trip-budget
Skill1 starsChanged 4 months agoMITView on GitHub
This skill should be used whenever money and the trip meet — phrases like "how much so far", "are we over budget", "what's left to spend", "track the budget", "can we afford", "cheaper option", or automatically whenever a flight, stay or activity is chosen so its cost gets logged against the ceiling.
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
- on-trip-conciergeSkill
- plan-tripSkill
- sync-calendarSkill
- traveller-profileSkill
- trip-checklistsSkill
- trip-weatherSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Keep a running cost tracker in travel/trips/<trip>/budget.md and hold the plan to the traveller's ceiling.
- Distinctive: line 40
Add sensible estimates for the unpriced realities — meals, local transport, airport transfers — scaled to destination and style, and mark …
- Distinctive: line 46
When asked "what's left", answer with headroom and the biggest remaining unpriced items.
- Distinctive: line 48
Business trips with receipts needed: keep every line itemised with date, vendor and amount so the table doubles as an expense-report draft.
≈ “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 Budget
Keep a running cost tracker in travel/trips/<trip>/budget.md and hold the
plan to the traveller's ceiling.
File format
# Budget — <Trip title>
**Ceiling:** £2,000 (total, incl. flights) · **Currency:** GBP
| Item | Category | Status | Per person | Total |
|---|---|---|---|---|
| LHR→LIS return, KL1234 | Flights | Committed | £120 | £240 |
| Hotel Exemplo, 4 nights | Stay | Committed | — | £520 |
| Food tour | Activities | Committed | £55 | £110 |
| Meals (4 days, est.) | Food | Estimate | — | £320 |
| Local transport (est.) | Transport | Estimate | — | £40 |
**Committed:** £870 · **Estimates:** £360 · **Projected total:** £1,230
**Headroom vs ceiling:** £770 (39%)Rules
- Log every chosen flight, stay and activity the moment it is picked; keep the summary lines recalculated on each edit.
- Add sensible estimates for the unpriced realities — meals, local transport, airport transfers — scaled to destination and style, and mark them Estimate.
- Convert to the traveller's currency; note the rate used for conversions.
- Warn at 80% of the ceiling and on any single pick that would cross it, offering one or two concrete cheaper swaps.
- When asked "what's left", answer with headroom and the biggest remaining unpriced items.
- Business trips with receipts needed: keep every line itemised with date, vendor and amount so the table doubles as an expense-report draft; separate any personal ("bleisure") spend into its own section so it never mixes with reclaimable costs.
- Present spend visually when helpful (category breakdown as a simple table or chart where the interface supports it).
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.

