🧰 Itinerary Drive Leg Check
Reviews day-by-day stops with claimed drive times and distances, flags unrealistic legs and missing buffers, and uses only the numbers you supply — no live traffic invention.
What it does
Give the skill your day plan with stops and the drive times or distances you already looked up. It walks each leg, flags back-to-back squeezes, missing meal or bathroom buffers, and legs whose stated time doesn’t fit the distance you provided under a simple average-speed sanity check.
Use it when: you’re packing a national-park or road-trip day and want a second pass before you promise a sunset viewpoint.
Works with: Claude Code, Claude.ai (Skills upload), Cursor and Codex. Install the ZIP, then ask your agent to check the drive legs in your itinerary.
It does not invent live traffic, road closures or permit outcomes. If a time or distance is missing, it asks — it will not fill it in.
Output preview
Install
Unzip first. You get a folder named itinerary-drive-leg-check containing SKILL.md.
Claude Code
Put the folder in your personal skills directory, or in the project to share it with your team.
~/.claude/skills/itinerary-drive-leg-check/SKILL.md.claude/skills/itinerary-drive-leg-check/SKILL.mdClaude Code picks up new skills in the current session (run /reload-skills if the skills folder didn't exist when the session started). The skill loads when a task matches its description.
Claude.ai
Turn on code execution (Settings → Capabilities), then go to Customize → Skills, click +, then Create skill → Upload a skill, and select the ZIP. Full guide.
Cursor
Put the folder in your user or project skills directory. Cursor also reads .claude/skills.
~/.cursor/skills/itinerary-drive-leg-check/SKILL.md.cursor/skills/itinerary-drive-leg-check/SKILL.mdCodex
Put the folder in your user or repository skills directory, then restart Codex or run /skills to check it is listed.
~/.agents/skills/itinerary-drive-leg-check/SKILL.md.agents/skills/itinerary-drive-leg-check/SKILL.mdThese are the standard skill locations for each tool. The tools a skill is verified on are listed under “Tested on” above, if any.
Test log
| Date (UTC) | Tool | Model | Run | Result | Checks | Tokens in / out |
|---|---|---|---|---|---|---|
| Nov 3, 2026 | Codex | gpt-5.4-mini | Test | Failed | 1/4
| 0 / 0 |
Each row is a real run recorded by our test runner. For each tool, the latest test run decides whether it appears under “Tested on”. Baseline runs do the same task with no skill installed and never count.