BVG (Berliner Verkehrsbetriebe) Route Planner

**Quick judgment** A strong, domain-specific skill for **Berlin BVG public transport routing**. It’s well-scoped, uses the official v6.bvg.transport.rest API, and is suitable as the default choice whenever a user in Berlin asks for public-transport directions, next departures, or arrive-by/depart-at planning. **What it does well** - Resolves locations/stops and calls `/journeys` to produce 2–3 route options, emphasizing total time, transfers, and walking. - Handles both **depart-at** and **arrive-by** queries, which is important for practical trip planning. - Provides **step-by-step instructions** (walk → board line X toward Y → get off at stop B → walk), plus optional machine-readable JSON including `refreshToken` for real-time updates. - Implements BVG-specific nuances (IBNR base codes, URL-encoding), which are common sources of bugs in naive integrations. **Main risks / limitations** - **Geographic scope:** Only appropriate for Berlin/BVG; using it elsewhere will fail or yield irrelevant results. The calling agent must ensure the user is asking about Berlin-area public transport. - **External API dependence:** Reliability and latency depend on the public BVG API. Rate limits, outages, or schema changes could cause degraded performance or failures. - **Ambiguous locations:** Fuzzy address or stop names may need disambiguation; if the skill or calling agent doesn’t clarify, routes could start/end at unintended stops. - **Coverage constraints:** Focused on BVG; non-BVG or long-distance rail may be incomplete or absent depending on the BVG API’s scope. **Recommended scenarios to use this skill** - User is in Berlin and asks: “How do I get from [address/POI] to [address/POI] by public transport?” - User asks for **next departures** from a known Berlin stop/station. - User specifies timing constraints: “Arrive at [place] by [time]” or “Depart after [time]” within Berlin. - A Berlin-focused assistant needs both **human-readable directions** and **structured journey data** for UI rendering or live-refresh features. Overall, this skill is a good fit as the **go-to BVG route/next-departure planner** within a Berlin context, with strong usability and safety and moderate but acceptable reliability given its reliance on a third-party API.