Run2 ground transport route logic
Logic for planning itineraries that rely on ground transportation (driving) rather than flights, ensuring travel feasibility and daily activity engagement.From its SKILL.md
npx -y skills add cxcscmu/SkillLearnBench --skill run2_ground-transport-route-logicAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.2 KB, 233 tokens by cl100k_base, as published. Nobody here has run it
- Travel Feasibility: Use
googleDistanceMatrix/distance.csvto calculate travel times between cities. Since flights are prohibited, all transitions must be labeled as "Self-driving: from [City A] to [City B]". - Activity Loading: Even on heavy travel days (e.g., driving from Minneapolis to Ohio), you must schedule at least one attraction.
- Transit Attractions: If a drive consumes most of the day, populate the
attractionfield by:- Selecting an attraction in the departure city before leaving.
- Selecting an attraction in a transit city found along the route in the database.
- Selecting a short-duration attraction in the destination city upon arrival.
- Minimum Activity Threshold: Never allow a day to have zero attractions or a value of "-". Every day of the 7-day plan must include at least one point of interest.
- Route Continuity: Ensure the
current_cityreflects the movement (e.g., "from Minneapolis to Cleveland") and theaccommodationfor that night is located in the arrival city.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.