skanetrafikenSkåne public transport trip planner (Skånetrafiken). Plans bus/train journeys with real-time delays. Supports stations, addresses, landmarks, and cross-border trips to Copenhagen.
Install via ClawdBot CLI:
clawdbot install rezkam/skanetrafikenPlan public transport journeys in Skåne, Sweden with real-time departure information.
Search for stations, addresses, or points of interest.
./search-location.sh <query> [limit]
| Argument | Description |
|----------|-------------|
| query | Location name to search for |
| limit | Number of results to show (default: 3, max: 10) |
Output includes:
ID - The location identifier (use this in journey search)Name - Official name of the locationType - STOP_AREA (station), ADDRESS, or POI (point of interest)Area - Region/municipalityCoordinates - Latitude, longitudeWhen to increase limit:
Plan a journey between two locations using their IDs.
./journey.sh <from-id> <from-type> <to-id> <to-type> [datetime] [mode]
| Argument | Description |
|----------|-------------|
| from-id | Origin location ID (from search) or coordinates (lat#lon) |
| from-type | STOP_AREA, ADDRESS, POI, or LOCATION (for coordinates) |
| to-id | Destination location ID or coordinates |
| to-type | Type of destination |
| datetime | Optional: "18:30", "tomorrow 09:00", "2026-01-15 09:00" |
| mode | Optional: "depart" (default) or "arrive" |
Important: The Journey API only accepts STOP_AREA and LOCATION types. For ADDRESS or POI results, use the coordinates as lat#lon with type LOCATION.
Before searching, understand what the user wants:
| User Says | Intent | How to Query |
|-----------|--------|--------------|
| "now", "next bus", "how do I get to" | Travel Now | No datetime parameter |
| "in 30 minutes", "in 1 hour", "after lunch" | Depart Later | Calculate time, use depart mode |
| "around 15:00", "sometime afternoon" | Around Time | Query with offset (see below) |
| "arrive by 18:00", "need to be there at 9" | Arrive By | Use arrive mode |
| "tomorrow morning", "on Friday at 10" | Future Time | Use specific datetime |
When user wants options "around" a time, query 15-30 minutes earlier to show options before and after:
# User: "I want to travel around 15:00"
# Query at 14:30 to get options spanning 14:30-16:00+
./journey.sh ... "14:30" depart
Convert relative times to absolute:
| User Says | Current: 14:00 | Query Time |
|-----------|----------------|------------|
| "in 30m" | → | "14:30" |
| "in 1h" | → | "15:00" |
| "in 2 hours" | → | "16:00" |
When presenting journey results to users, use these emojis and formatting guidelines.
| Emoji | Use For |
|-------|---------|
| 🚂 | Train (Pågatåg, Öresundståg) |
| 🚌 | Bus |
| 🚇 | Metro (Copenhagen) |
| 🚋 | Tram |
| ⛴️ | Ferry |
| 🚶 | Walking segment |
| ⏱️ | Time/duration |
| 🕐 | Departure time |
| 🏁 | Arrival time |
| 📍 | Stop/station |
| 🏠 | Origin (home/start) |
| 🎯 | Destination |
| ⚠️ | Delay or disruption |
| ✅ | On time |
| 🔄 | Transfer/change |
| 🛤️ | Platform/track |
Always include these key elements from the tool output:
For a simple direct journey:
🏠 **Leave home at 09:00**
🚶 Walk 450m to Möllevångstorget (5 min)
📍 **Möllevångstorget** → 🎯 **Malmö C**
🚌 Bus 5 departs 09:07 from Möllevångstorget
🏁 Arrives 09:18 at Malmö C
⏱️ Total: 18 min
For a journey with transfer:
🏠 **Leave at 08:45**
🚶 Walk 300m to Västra Hamnen (4 min)
📍 **Västra Hamnen** → 🔄 **Malmö C** → 🎯 **Lund C**
**Leg 1:**
🚌 Bus 2 departs 08:51 [🛤️ Läge A]
🏁 Arrives Malmö C 09:05
🔄 Transfer at Malmö C (6 min)
**Leg 2:**
🚂 Pågatåg departs 09:11 [🛤️ Spår 4]
🏁 Arrives Lund C 09:23
⏱️ Total: 38 min | 🔄 1 change
With delays:
🕐 **Depart 14:30** from Triangeln
🚂 Öresundståg 1042 → København H
⚠️ +8 min delay (expected 14:38 instead of 14:30)
🏁 Arrives ~15:25 (normally 15:17)
CRITICAL: Always show walking details from the tool output:
line.distance)Example tool output:
→ WALK 450m from Kalendegatan to Möllevångstorget
Format as:
🚶 Walk 450m to Möllevångstorget (~5 min)
Walk time estimate: ~100m per minute (normal walking speed)
When showing journey options, make timing crystal clear:
I found 3 options for you:
**Option 1 - Leave now (09:00)** ✅ Recommended
🚶 5 min walk → 🚌 Bus 5 at 09:07 → arrives 09:25
⏱️ Total: 25 min
**Option 2 - Leave in 15m (09:15)**
🚶 5 min walk → 🚌 Bus 5 at 09:22 → arrives 09:40
⏱️ Total: 25 min
**Option 3 - Leave in 30m (09:30)**
🚶 5 min walk → 🚂 Train at 09:37 → arrives 09:48
⏱️ Total: 18 min | Faster but later departure
Use clear notation for departure times:
| Notation | Meaning |
|----------|---------|
| "now" | Immediately |
| "in 15m" | 15 minutes from now |
| "in 1h" | 1 hour from now |
| "at 14:30" | Specific time |
Follow this workflow when a user asks for a trip:
Parse what the user wants:
Search for origin and destination separately:
./search-location.sh "Malmö C"
./search-location.sh "Emporia"
Check each result carefully:
When results don't match or are ambiguous, ask clarifying questions:
I searched for "centrum" and found multiple locations:
1. Malmö Centrum (bus stop)
2. Lund Centrum (bus stop)
3. Helsingborg Centrum (bus stop)
Which one did you mean?
When no results are found, try these strategies:
# If "Storgatan 10" fails, try:
./search-location.sh "Storgatan 10, Malmö"
# If "Malmö station" fails, try:
./search-location.sh "Malmö C"
# If "Emporia, Malmö" fails, try:
./search-location.sh "Emporia"
lat#lon format directlyThe Journey API only accepts:
STOP_AREA - Bus/train stations (use ID directly)LOCATION - GPS coordinates as lat#lonIf search returns ADDRESS or POI:
lat#lon with type LOCATIONExample:
# Search returns: ID: 123, Type: ADDRESS, Coordinates: 55.605, 13.003
# Use in journey as:
./journey.sh "55.605#13.003" LOCATION 9021012080000000 STOP_AREA
Once you have confirmed IDs/coordinates for both locations:
./journey.sh <from-id> <from-type> <to-id> <to-type> [datetime] [mode]
Use the emoji guide above to present results clearly. Always use actual numbers from the tool output - never speculate or estimate.
The search API is sensitive to formatting. Follow these rules:
Use the landmark name WITHOUT city name.
# CORRECT
./search-location.sh "Emporia"
./search-location.sh "Triangeln"
./search-location.sh "Turning Torso"
# WRONG - city name breaks POI search
./search-location.sh "Emporia, Malmö" # May return wrong location!
./search-location.sh "Triangeln, Malmö" # Unnecessary, may fail
Include city name for better accuracy.
# CORRECT
./search-location.sh "Kalendegatan 12, Malmö"
./search-location.sh "Storgatan 25, Lund"
./search-location.sh "Drottninggatan 5, Helsingborg"
# RISKY - may be ambiguous
./search-location.sh "Kalendegatan 12" # Works if unambiguous
Use "C" suffix for central stations.
# CORRECT
./search-location.sh "Malmö C"
./search-location.sh "Lund C"
./search-location.sh "Helsingborg C"
./search-location.sh "Malmö Hyllie"
./search-location.sh "Malmö Triangeln"
# WRONG
./search-location.sh "Malmö" # Ambiguous!
./search-location.sh "Malmö Central" # Not official name
./search-location.sh "Lund station" # Not official name
Use Danish names or common alternatives.
# All work
./search-location.sh "København H"
./search-location.sh "Nørreport"
./search-location.sh "Copenhagen Airport"
./search-location.sh "Köpenhamn"
User: "How do I get from Malmö C to Lund C?"
./search-location.sh "Malmö C"
./search-location.sh "Lund C"
./journey.sh 9021012080000000 STOP_AREA 9021012080040000 STOP_AREA
Response:
🏠 **Leave now** from Malmö C
📍 **Malmö C** → 🎯 **Lund C**
🚂 Öresundståg 1324 departs 09:04 [🛤️ Spår 2b]
🏁 Arrives 09:16 at Lund C [🛤️ Spår 1]
⏱️ Total: 12 min | ✅ Direct, no changes
User: "I need to go from Kalendegatan 12 in Malmö to Emporia"
./search-location.sh "Kalendegatan 12, Malmö"
./search-location.sh "Emporia"
./journey.sh "55.595#13.001" LOCATION "55.563#12.973" LOCATION
Response:
🏠 **Leave at 10:05**
🚶 Walk 320m to Möllevångstorget (~3 min)
📍 **Möllevångstorget** → 🎯 **Emporia**
🚌 Bus 32 departs 10:10
🏁 Arrives 10:28 at Emporia
🚶 Walk 150m to destination (~2 min)
⏱️ Total: 25 min
User: "I need to be at Copenhagen central by 18:00 tomorrow"
./search-location.sh "Malmö C"
./search-location.sh "København H"
./journey.sh 9021012080000000 STOP_AREA 9921000008600626 STOP_AREA "tomorrow 18:00" arrive
Response:
🎯 **Arrive by 18:00** at København H
📍 **Malmö C** → 🎯 **København H**
🚂 Öresundståg departs **17:21** [🛤️ Spår 1]
🏁 Arrives **17:56** ✅ 4 min buffer
⏱️ Journey: 35 min
💡 Leave Malmö C by 17:21 to arrive on time!
User: "I want to travel to Lund around 15:00"
# Query 30 min earlier to show options around 15:00
./journey.sh 9021012080000000 STOP_AREA 9021012080040000 STOP_AREA "14:30"
Response:
Options around 15:00 for Malmö C → Lund C:
**Option 1 - Depart 14:34** (in 25m)
🚂 Pågatåg → arrives 14:52
⏱️ 18 min
**Option 2 - Depart 14:49** (in 40m)
🚂 Öresundståg → arrives 15:01
⏱️ 12 min
**Option 3 - Depart 15:04** (in 55m) ✅ Closest to 15:00
🚂 Pågatåg → arrives 15:22
⏱️ 18 min
Which works best for you?
User: "I want to leave in about an hour"
# Current time: 13:00, so query for 14:00
./journey.sh ... "14:00"
Response:
Options departing around 14:00 (in ~1h):
**Leave at 13:55** (in 55m)
🚶 5 min walk → 🚌 Bus 5 at 14:02 → arrives 14:25
**Leave at 14:10** (in 1h 10m)
🚶 5 min walk → 🚂 Train at 14:17 → arrives 14:35
Let me know which one works!
When tool output shows delays:
From: 14:30 Malmö C [+8 min late]
Response:
📍 **Malmö C** → 🎯 **Lund C**
🚂 Öresundståg 1042
⚠️ **Running 8 min late**
🕐 Scheduled: 14:30 → Expected: ~14:38
🏁 Arrives ~14:50 (normally 14:42)
Always ask when:
All times are Swedish local time (CET/CEST).
| Format | Example | Meaning |
|--------|---------|---------|
| _(empty)_ | | Travel now |
| HH:MM | "18:30" | Today at 18:30 |
| tomorrow HH:MM | "tomorrow 09:00" | Tomorrow at 09:00 |
| YYYY-MM-DD HH:MM | "2026-01-15 09:00" | Specific date |
══════════════════════════════════════════════════════════════
OPTION 1: Malmö C → Lund C
══════════════════════════════════════════════════════════════
Date: 2026-01-14
Depart: 09:04
Arrive: 09:16
Changes: 0
LEGS:
→ ORESUND Öresundståg 1324
From: 09:04 Malmö C [Spår 2b]
To: 09:16 Lund C [Spår 1]
Direction: mot Helsingborg C
| Type | Emoji | Description |
|------|-------|-------------|
| TRAIN | 🚂 | Pågatåg (regional train) |
| ORESUND | 🚂 | Öresundståg (cross-border train) |
| BUS | 🚌 | City or regional bus |
| WALK | 🚶 | Walking segment |
| TRAM | 🚋 | Tram/light rail |
| METRO | 🚇 | Copenhagen Metro |
| FERRY | ⛴️ | Ferry |
| Indicator | Emoji | Meaning |
|-----------|-------|---------|
| _(none)_ | ✅ | On time |
| [+X min late] | ⚠️ | Delayed |
| [-X min early] | ℹ️ | Running early |
| [PASSED] | ❌ | Already departed |
| AVVIKELSE | 🚨 | Service disruption |
The search returned no results.
Strategies:
No routes available.
Strategies:
| Location Type | Search Format | Journey Type |
|--------------|---------------|--------------|
| Train station | "Malmö C" | STOP_AREA |
| Bus stop | "Möllevångstorget" | STOP_AREA |
| Address | "Street 12, City" | Use coords → LOCATION |
| Landmark/POI | "Emporia" (no city!) | Use coords → LOCATION |
| Coordinates | 55.605#13.003 | LOCATION |
AI Usage Analysis
Analysis is being generated… refresh in a few seconds.
Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).
Reorder Foodora orders + track ETA/status with ordercli. Never confirm without explicit user approval. Triggers: order food, reorder, track ETA.
Google Maps integration for OpenClaw with Routes API. Use for: (1) Distance/travel time calculations with traffic prediction, (2) Turn-by-turn directions, (3...
Flight tracking and scheduling. Track live flights in real-time by region, callsign, or airport using OpenSky Network. Search flight schedules between airports. Use for queries like "What flights are over Switzerland?" or "When do flights from Hamburg arrive in Zurich?" or "Track flight SWR123".
Use when the user asks to "find flights", "compare itineraries", "search hidden-city routes", "check cheapest dates", "explore destinations", "search hotels"...
Comprehensive travel planning, booking, and management skill. Use when needing to plan international trips, manage multi-destination itineraries, handle family travel logistics, optimize travel costs, and coordinate complex travel arrangements.