1.7k Downloads
Overview
Provides an LLM-controllable trip planner for Skåne (Sweden) and Copenhagen area public transport using Skånetrafiken’s real‑time journey and location APIs.
Key Advantages
1.Well-structured two-step workflow: separate location search and journey planning with clear argument contracts.
2.Rich, concrete guidance for the LLM on time intent handling (now, depart later, arrive by, around a time, relative times).
3.Supports multiple location types (stations, addresses, POIs, coordinates) with clear conversion rules for the journey API.
4.Real-time departures with delays/disruptions surfaced, including explicit deviation notation (e.g., [+8 min late]).
5.Detailed response-format instructions (emojis, walking segments, transfers, delays) for highly readable user outputs.
Use Cases
- Interactive trip planning within Skåne and between Skåne and Copenhagen (e.g., Malmö C ↔ Lund C, Malmö ↔ København H).
- Helping users choose between several journey options around a given time window, including transfers and travel time trade-offs.
- Planning trips from precise street addresses or POIs (e.g., “Kalendegatan 12, Malmö” → “Emporia”) by auto-converting to coordinates for the journey API.
- Handling “arrive by” scenarios where the agent must back-calculate suitable departures and provide buffer times.
- Assisting users when searches are ambiguous (e.g., multiple ‘centrum’ stops) by listing options and requesting clarification.
Evaluation Scores
8.5
/ 10
Reliability
7.8
Functionality
8.5
Usability
9.2
Safety
9.0
Performance
7.5
Compatibility
8.0
Based on 1 evaluation · Latest: 3/20/2026
Download Trend
Loading...
Evaluation History (1)
8.5/103/20/2026▼
OS: linux-x64LLM: deepseek/deepseek-v3.2
**Overall judgment:** High-quality, mature trip-planning skill focused on Skånetrafiken, with strong LLM-oriented documentation. Well-suited as the primary public transport planner for Skåne and cross-border journeys to Copenhagen.
**Strengths**
- Clear, minimal API surface (`search-location.sh` and `journey.sh`) that maps well to typical agent workflows.
- Extensive instructions for interpreting user time intent (now / depart later / arrive by / around / relative times) and converting to concrete query datetimes.
- Robust handling of different location types (STOP_AREA, ADDRESS, POI, LOCATION) with explicit conversion rules to satisfy the Journey API’s stricter requirements.
- Highly user-friendly response-format guidance (emojis, walking distances, walking-time estimation, transfers, delays) that makes it easy for an LLM to present readable itineraries.
- Error-handling patterns explicitly described for ambiguous locations, no results, and cross-border naming issues.
**Key risks / limitations**
- **Geographic scope:** Primarily limited to Skåne and common Copenhagen destinations; not a general-purpose global transport planner.
- **External dependency:** Reliability and latency are tied to Skånetrafiken’s backend and network stability; no explicit retry/backoff strategy is described.
- **Search sensitivity:** POI and station search is formatting-sensitive (e.g., “Emporia” vs “Emporia, Malmö”; correct “C” station names required). An agent that ignores these rules may see degraded results.
- **Time semantics:** The skill expects the LLM to correctly parse and normalize relative and vague time expressions into explicit datetimes; misinterpretation here can lead to suboptimal journey suggestions.
**Recommended scenarios**
- Assistants aimed at residents or visitors in Skåne/Copenhagen who frequently use public transport.
- Travel-planning chatbots that need to reason about different departure options, transfers, and delays in real time.
- Multimodal city guides where the LLM must convert free-form location and time queries into precise, actionable transit instructions.
Comments (0)
No comments yet. Be the first!