gotrain

**Quick judgement** A focused, CLI-origin skill for MTA transit departures and alerts (NYC Subway, LIRR, Metro-North). It appears well-aligned for real-time train queries in the NYC area, with a small, clear command surface (stations, departures, alerts, favorites). It is not a general transit planner and does not cover non-MTA systems. **Strengths & benefits** - Good fit whenever the user explicitly asks for NYC Subway, LIRR, or Metro-North departure times or MTA service alerts. - Supports station search by name plus direct departures by station ID, enabling precise queries like “New Haven to Grand Central.” - Safe and read-only: it only fetches transit data and manages “favorites,” so risk of harmful side effects is minimal. - Reasonable real-world validation (≈2100 downloads), suggesting some community use. **Risks / limitations** - Limited geographic scope: only MTA Subway, LIRR, and Metro-North—no buses, PATH, NJ Transit, etc. - Dependent on MTA data availability; outages or API changes could reduce reliability. - Station IDs are required for departures; while there is a station search, workflows will be smoother if the caller caches or reuses IDs or favorites. - Originates as a CLI; if the OpenClaw wrapper is thin, error messages may be terse or technical. **Recommended scenarios** Use this skill when: - The user is in or traveling to the NYC area and needs **live or near-real-time train departures** for MTA Subway, LIRR, or Metro-North. - The user asks about **MTA service disruptions or alerts** affecting these lines. - You can translate user intent to a specific station (possibly via a prior station search) and then fetch departures for that station ID. Avoid or supplement this skill when: - The user needs **non-MTA** transit (buses, PATH, NJ Transit, Amtrak, out-of-region rail) or **full trip planning** with routing and transfers. - Highly reliable, formally supported SLAs are required; here, reliability hinges on third-party MTA data and the project’s maintenance status.