Travel assistant for NanoClaw: byAir flight notifications (delay, gate, connection risk, inbound aircraft delay, time-to-leave, arrival logistics), traffic-aware drive planning for in-person meetings (auto drive blocks + leave-by traffic rechecks), travel-booking gap checks, and nightly TripIt sync. Per-chat overlay plugin.
68
85%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Background library bundle — not a workflow and not an action router. It has no steps and must never be executed or invoked; do not parallelize or freelance over it.
This skill is retired. The unified drive-engine (#156) now plans and writes every Drive: block — both airport and meeting drives — from one place, so drive-planner's own sweep is disabled (its cadence is removed) and it no longer creates or notifies. It stays declared only because drive-engine's reconcile sweep reuses its proven meeting-detection code as a library.
scan.py — meeting-event classification. Public surface: scan, actionable, MeetingClass, TransitLeg.fetch_events.py — the primary-calendar window fetch (CalendarFetcher).skip_state.py — active-skip loading (load_active_skips).drive-engine's reconcile_sweep.py puts this bundle on sys.path (runtime mount tessl__drive-planner, dev-clone sibling fallback) and imports from it:
from scan import scan
from fetch_events import CalendarFetcher
from skip_state import load_active_skipsThe classification rules and leg logic live in those modules and their tests — do not restate them here. Any drive blocks drive-planner created before retirement remain on the calendar for the operator to remove; drive-engine does not touch them.
.tessl-plugin
skills
check-travel-bookings
drive-engine
drive-planner
drive-planner-recheck
flight-assist
references
nightly-travel-sync
sync-tripit
travel-core