2.6k
GitHub Stars
5
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill capmetro-skill- _meta.json638 B
- package-lock.json5.2 KB
- package.json957 B
- README.md7.9 KB
- SKILL.md7.3 KB
Overview
This skill provides real-time CapMetro transit information for Austin, including vehicle positions, next arrivals, service alerts, route details, and trip planning for buses and rail. It combines GTFS real-time feeds and GTFS static data so users get near live locations and scheduled times without any API key. The skill is designed for quick answers about routes, stops, delays, and fares.
How this skill works
The skill fetches open-access GTFS-RT feeds (vehicle positions, trip updates, and service alerts) updated about every 15 seconds and pairs them with local GTFS static files for stops, routes, and schedules. Helper scripts parse JSON or protobuf feeds, match vehicle/trip IDs to route and stop names, and compute next arrivals and delay estimates. If protobuf parsing fails, a JSON vehicle feed is available as a fallback; static GTFS is cached locally and refreshed on demand.
When to use it
- Ask when the next bus or train arrives at a specific stop or stop name.
- Check where a specific CapMetro vehicle or route currently is in Austin.
- Look up active service alerts, detours, or route disruptions for a route.
- Search for nearby stops or full route stop lists and schedules.
- Verify fares and basic fare products for planning a trip.
Best practices
- Refresh GTFS static data after service changes (typically quarterly) to keep stop and schedule info accurate.
- Provide a stop_id when possible for precise arrival times; use stop-name search when you don’t have the ID.
- Include route number and direction/headsign for filtered arrival queries to avoid ambiguity.
- Lead with next arrival and any active alerts when presenting results to users.
- Show scheduled vs estimated times for delays and use 12-hour time with AM/PM for readability.
Example use cases
- User asks: “When is the next 801 at the downtown stop?” — return next arrivals plus active alerts.
- User asks: “Where is the MetroRail right now?” — provide vehicle position and nearest landmark if possible.
- User asks: “Are there any detours on Route 10?” — show service alerts and affected stops.
- User asks: “Find stops near 30.27,-97.74” — list nearby stops and next arrival times.
- User asks: “How much is a MetroRail single ride?” — return fare table and payment options.
FAQ
No. All CapMetro feeds used are open-access on the Texas Open Data Portal and require no API key.
How fresh is the real-time data?
Vehicle position feeds update roughly every 15 seconds; service alerts and trip updates use the GTFS-RT feeds provided by the data portal.
What if arrivals or vehicle positions are missing?
If a feed fails or returns empty, the skill reports real-time data may be temporarily unavailable and falls back to JSON vehicle data where possible.