fun-facts
Skill1 starsChanged 4 months agoMITView on GitHub
This skill should be used to surface surprising, non-obvious facts about a destination — triggers include a destination being set during trip planning, and direct asks like "fun facts about Lisbon", "did you know anything interesting about Japan", "tell me something cool about this place", "trivia about", or "something to tell my friends about". Also use it proactively, once, when a trip's destination is confirmed, and during on-trip downtime when the traveller wants a spontaneous nugget about where they are.
In this repository15 other files it gives its agents.
- expense-reportSkill
- export-itinerarySkill
- find-activitiesSkill
- find-diningSkill
- find-flightsSkill
- find-staysSkill
- manage-itinerarySkill
- monitor-faresSkill
- on-trip-conciergeSkill
- 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, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Verifiable: search the web to confirm before using it.
- Very specific: line 39
Read trip-brief.md for the template and interests, and pick facts that match:
- Very specific: line 62
Keep a running list of facts already shared in travel/trips/<trip>/fun-facts.md (one line per fact) so repeat requests during a trip …
- Distinctive: line 68
If a search turns up conflicting claims (a popular "fact" that's actually a myth), say so — "widely claimed, but…" — rather than repeating …
- Distinctive: line 71
Keep the tone playful and genuine, never like padded content or an ad for the destination.
- Distinctive: line 73
Don't let this delay the actual planning — it's a garnish, not the main course.
≈ “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
Fun Facts
Give the traveller genuinely surprising, shareable facts about a destination — the kind that make people say "wait, really?" and repeat it to a friend. Never generic tourist-brochure trivia.
What counts as a good fact
- Non-obvious: skip anything in the first paragraph of a guidebook (population, "it's the capital of…", "famous for its tower"). If it's the first thing a search result says, it's not a fun fact — dig further.
- Verifiable: search the web to confirm before using it; do not rely on memory alone, since specifics (numbers, records, "only place in the world…") are exactly where memory drifts and dates fastest.
- Concrete and specific: a precise, odd detail beats a vague claim. "The city has more canals than Venice" beats "the city has lots of water".
- Light by default: aim for delight and conversation value. Avoid anything grim, tragic, or a sensitive stereotype unless the trip itself is history/heritage-focused and the traveller would want that depth — and even then, handle it respectfully rather than as a shock fact.
Tailor to the trip
Read trip-brief.md for the template and interests, and pick facts that
match:
| Trip flavour | Lean towards |
| Food & drink / gastronomy | Culinary origins, odd food laws, surprising ingredient history, where a dish "actually" comes from |
| Adventure & outdoors | Geological oddities, wildlife quirks, record-holding terrain |
| Culture & history | Overlooked history, surprising architectural stories, etymology of place names |
| Family holiday | Fun, safe-for-all-ages, nothing grim |
| Business trip | Quick, sharp, good for small talk with local colleagues or clients |
| No clear flavour / Surprise me | A broad, varied mix |
For multi-city trips, tailor per city, not just once for the whole trip.
Delivering facts
- Format as a short "Did you know…?" line, one or two sentences, no more than 3–5 per delivery — a handful of great facts beats a wall of trivia.
- During trip planning: offer once, right after the destination is set, framed as a small bonus, not a mandatory step — easy to skip.
- On-trip (via
on-trip-concierge): offer when the traveller has downtime or asks directly; can tie a fact to where they physically are if that context is available. - Keep a running list of facts already shared in
travel/trips/<trip>/fun-facts.md(one line per fact) so repeat requests during a trip surface new ones rather than repeating.
Care points
- If a search turns up conflicting claims (a popular "fact" that's actually a myth), say so — "widely claimed, but…" — rather than repeating a myth as true.
- Keep the tone playful and genuine, never like padded content or an ad for the destination.
- Don't let this delay the actual planning — it's a garnish, not the main course.
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.