agentleFS
bethronbethron/travel-concierge/skills/find-activities/SKILL.md

find-activities

Skill1 starsChanged 4 months agoMITView on GitHub

This skill should be used whenever the user wants things to do — phrases like "what should we do in", "activities in", "tours in", "day trips from", "tickets for", "experiences", "excursions", or when a trip plan reaches the activity-filling stage. Also use it for interest-led asks ("snorkelling near", "cooking class in", "something for kids in").

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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
  1. Distinctive:

    Search bookable tours, tickets, experiences and trails across the activity connectors, blend in free sights, and match everything to the …

    line 15
  2. Distinctive:

    Run the relevant sources in parallel, deduplicate, and complement with web search for free or unbookable highlights (viewpoints, markets, …

    line 37
  3. Distinctive:

    If neither connector is available, ask the user to enable them and continue with web-search suggestions clearly marked as not live-bookable.

    line 41
  4. Distinctive:

    Check seasonal availability — do not schedule an activity outside its operating season or hours as returned by the connector.

    line 73
  5. Distinctive:

    Keep at least one unscheduled block per day unless the pace is "packed".

    line 78

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Find Activities

Search bookable tours, tickets, experiences and trails across the activity connectors, blend in free sights, and match everything to the traveller's interests and pace.

Connector strategy

  • Viator — the broadest experiences catalogue: tours, tickets, day trips. A strong default alongside Veltra; fetch full details for anything shortlisted.
  • Veltra Activities — keyword search for tours, classes, day trips and experiences. Search per interest ("food tour Kyoto", "snorkelling Bali"), not one generic query.
  • Super.com experiences — city-level search for bookable attractions, tickets and day trips; good for headline sights and skip-the-line tickets.
  • AllTrails — the specialist for anything outdoors: hiking, running and cycling trails near a location, trail details, and the trailhead weather forecast. Reach for it whenever the trip template is adventure/outdoors or the traveller mentions walking, hiking or nature.
  • lastminute.com — check for experience deals when the trip is imminent or the traveller is already there.
  • Tripadvisor — sense-check a shortlisted attraction's reputation when the traveller asks whether it is worth it.
  • Run the relevant sources in parallel, deduplicate, and complement with web search for free or unbookable highlights (viewpoints, markets, neighbourhoods, beaches) so the plan is not purely commercial.

If neither connector is available, ask the user to enable them and continue with web-search suggestions clearly marked as not live-bookable.

Inputs

Pull interests, party (children's ages matter), pace and remaining budget from trip-brief.md. Aim for a density that matches the pace: roughly one booked activity per day for "balanced", two for "packed", every other day for "downtime".

Presenting results

Group by interest or by day slot, in a table:

ActivityTypeDurationSuitsPrice (pp)Source

Mark free sights as Free. Recommend a shortlist that fits the days available, and note anything needing advance booking or with limited schedules.

After the choice

  • Save the comparison table to options/activities-<date>.md for the savings summary (expense-report skill).
  • Slot each chosen activity into itinerary.md on a sensible day and time (respect opening hours, travel time, meal times, and rest after arrival).
  • Record picks and prices in trip-brief.md and budget.md.
  • Link to the provider for the actual booking.

Care points

  • Check seasonal availability — do not schedule an activity outside its operating season or hours as returned by the connector.
  • Warn about weather-dependent activities and suggest a rainy-day backup — check the trip-weather skill for the activity's date when it falls within the forecast horizon.
  • Keep at least one unscheduled block per day unless the pace is "packed".

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.