Pp Infotbm

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/travel/infotbm/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

TBM Bordeaux — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the infotbm-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install infotbm --cli-only

2. Verify: infotbm-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer):

go install github.com/mvanhorn/printing-press-library/library/travel/infotbm/cmd/infotbm-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

When to Use This CLI

Use when an agent needs Bordeaux transit information — schedules, real-time arrivals, route planning, or disruption monitoring. Ideal for commute automation, travel planning, and transit-aware applications in the Bordeaux Métropole area.

Anti-triggers

Do not use this CLI for:

• Journey planning outside Bordeaux Métropole
• Ticket purchase or fare payment
• Real-time traffic or driving directions
• Historical ridership or usage statistics

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Schedule intelligence

• schedule diff — Surface trips that are scheduled in GTFS but absent from live real-time data — the buses that exist on paper but never showed up

  When an agent needs to know whether a scheduled service is actually running today, this is the only command that answers definitively

  infotbm-pp-cli schedule diff --stop BEQUI --line A --json

• lines stops — Print the ordered stop list for a line and direction, optionally with scheduled departure times

  When an agent needs the exact stop order for a tram line to plan boarding points or give directions, this is the canonical answer

  infotbm-pp-cli lines stops --line A --direction 0 --json

• schedule changes — Compare GTFS sync snapshots to detect added, removed, or modified routes on a line

  When an agent manages a commuter's routine, this proactively detects schedule changes that would break their timing

  infotbm-pp-cli schedule changes --line C --since 7d --json

• lines frequency — Compute average headways per hour from the SIRI estimated timetable

  When an agent evaluates transit reliability for scheduling, this shows the real-world gaps between departures by time of day

  infotbm-pp-cli lines frequency --line B --json

Journey intelligence

• trips last-departure — Find the latest departure from a stop that still reaches your destination before a cutoff time

  When an agent plans evening activities, this answers 'what is the absolute latest I can leave and still get home by transit'

  infotbm-pp-cli trips last-departure --from Victoire --to Pessac --before 23:30 --json

• trips reroute — When your current connection is delayed, compute the best alternate onward path using live vehicle data

  When an agent detects a delay notification, this computes the optimal recovery without re-planning from scratch

  infotbm-pp-cli trips reroute --at "Gare Saint-Jean" --to Meriadeck --delay 8 --json

• trips plan — Plan multi-modal journeys across tram, bus, and ferry using local GTFS data with live disruption awareness

  When an agent needs transit directions in Bordeaux without relying on third-party map APIs, this plans the route locally

  infotbm-pp-cli trips plan --from Victoire --to "Gare Saint-Jean" --depart 08:15 --json

Commute intelligence

• alerts impact — Filter all active disruptions to only those affecting your specific lines or stops

  When an agent monitors a commuter's daily lines, this filters noise to only relevant disruptions

  infotbm-pp-cli alerts impact --lines A,C,15 --json

Command Reference

agencies —

• infotbm-pp-cli agencies — Transit agencies in the Bordeaux network

alerts —

• infotbm-pp-cli alerts — Active service disruption alerts

fares —

• infotbm-pp-cli fares — Fare structure including pricing and transfer rules

feed-info —

• infotbm-pp-cli feed-info — GTFS feed metadata including validity dates and timestamps

kml —

• infotbm-pp-cli kml — KML geographic data export with route geometry and stop locations

realtime —

• infotbm-pp-cli realtime stop — Real-time departure information at a specific stop
• infotbm-pp-cli realtime vehicles — Real-time vehicle positions across the network

routes —

• infotbm-pp-cli routes — All transit routes/lines in the TBM network

server-info —

• infotbm-pp-cli server-info — API version and build information

siri —

• infotbm-pp-cli siri check-status — SIRI service health check
• infotbm-pp-cli siri estimated-timetable — Estimated real-time timetable for a line
• infotbm-pp-cli siri general-message — General service messages and disruption information
• infotbm-pp-cli siri lines-discovery — Discover all lines with destinations and transport modes
• infotbm-pp-cli siri stop-monitoring — Real-time arrival/departure monitoring at a stop
• infotbm-pp-cli siri stoppoints-discovery — Discover all stop points with coordinates and serving lines

stops —

• infotbm-pp-cli stops — All transit stops in the TBM network

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

infotbm-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Hand-written Extensions

These command groups are hand-wired outside the generated endpoint surface. They are listed here for discoverability and are intentionally outside ## Command Reference so the verify-skill unknown-command check does not treat them as generator-owned paths.

• infotbm-pp-cli schedule — Offline schedule lookups from local GTFS data (subcommands: diff, changes)
• infotbm-pp-cli trips — Journey planning commands (subcommands: plan, last-departure, reroute)
• infotbm-pp-cli lines — Line analysis commands (subcommands: stops, frequency)

Recipes

Morning commute check

infotbm-pp-cli realtime stop --stop-id bordeaux:StopPoint:BP:3648:LOC --json --select items.lineName,items.destinationName,items.expectedDepartureTime

Check next departures at your stop with only the fields that matter