Seoul Subway

**Judgement:** High-quality, well-scoped Seoul Subway skill with strong coverage of real-time data and key static info, suitable as a primary transit capability for Seoul-focused assistants. **Strengths:** - Rich feature set: arrivals, station lookup, route planning, alerts, last trains (77 key stations), exits, accessibility, quick exits, restrooms. - Bilingual (KO/EN) with natural-language trigger examples and landmark→station mapping, ideal for both residents and visitors. - Simple, consolidated HTTP interface via a proxy (no API keys), with clear parameter and response documentation. - Thoughtful privacy and security notes: proxy only sees station/route parameters and standard headers; source is open on GitHub. **Key Risks / Limitations:** - Reliance on a third-party Vercel proxy and upstream public transit APIs means availability and latency are not guaranteed. - Some datasets (last trains, exits, etc.) are static and limited to 77 major stations; information may become stale over time or be incomplete for less central stations. - The proxy necessarily observes user IP and request metadata; while reasonable for this use case, it is still an external data sink. **Recommended Scenarios:** - Seoul-focused travel or daily-commute assistants where subway guidance is a central feature. - Tourist helpers that need landmark-based directions, exits, and accessibility hints around major stations. - General-purpose Korean/English chat agents that should answer “how do I get there by subway?” questions for the Seoul metro with minimal setup. - Not ideal for: global transit coverage, non-Seoul networks, or applications requiring hard uptime guarantees and fully first-party data handling.