Wiener Linien

**Judgement:** A strong, focused skill for Vienna public transport that leverages the official Wiener Linien real-time API. It is well-suited as the default tool when a user asks about live departures, disruptions, or elevator status within Vienna’s U-Bahn, tram, or bus network. **Strengths** - High-quality, official real-time data for departures and disruptions. - Good coverage of operational aspects: departures, disruptions, elevator/escalator outages, and service news. - Supports accessibility-related information (barrierFree flag and elevator status). **Key Limitations / Risks** - The underlying API is stop-centric and line-centric; it does not provide full journey planning (no full door-to-door routing, transfers, or optimal route calculation). - Precise stop identification often relies on RBL stop IDs; if the skill does not implement robust name matching or disambiguation, user queries with vague station names may be ambiguous or fail. - Subject to Wiener Linien API availability and rate limits (e.g., error code 316), which can degrade reliability during outages or heavy use. **Recommended Scenarios** - Use when a user in Vienna asks for: next departures, live delays, or platform-specific times for U-Bahn, tram, or bus. - Use for disruption and elevator-outage checks (especially for accessibility-sensitive users). - Use to answer “Are there any problems on line X?” or “Is the elevator at station Y working?” - Avoid positioning it as a full journey planner; for multi-leg route planning across the city, combine with or defer to a dedicated routing or mapping solution if available.