Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Västerbotten & Umeå public transport trip planner (Tabussen/Ultra). Plans bus journeys using ResRobot API. Supports stops, addresses, coordinates, regional and local routes throughout Västerbotten county.
Västerbotten & Umeå public transport trip planner (Tabussen/Ultra). Plans bus journeys using ResRobot API. Supports stops, addresses, coordinates, regional and local routes throughout Västerbotten county.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Plan public transport journeys in Västerbotten, Sweden - including Umeå local traffic (Ultra) and regional routes (Länstrafiken Västerbotten).
This skill uses the ResRobot API (Trafiklab) to provide journey planning for Tabussen/Ultra. ResRobot is Sweden's national public transport API covering all operators including Länstrafiken Västerbotten. Coverage: Ultra (Umeå local bus traffic) Länstrafiken Västerbotten (regional buses) Connections to/from other Swedish regions Train connections where applicable
Search for stops, stations, or points of interest. ./search-location.sh <query> [limit] ArgumentDescriptionqueryLocation name to search for (append ? for fuzzy search)limitNumber of results to show (default: 5, max: 10) Output includes: ID - The stop identifier (use this in journey search) Name - Official name of the stop Coordinates - Latitude, longitude Weight - Traffic volume indicator (higher = more traffic) Search tips: Use ? suffix for fuzzy/partial matching: "Vasaplan?" Exact search without ?: "Vasaplan" Include municipality for precision: "Umeå Vasaplan"
Plan a journey between two locations using their IDs. ./journey.sh <from-id> <to-id> [datetime] [mode] ArgumentDescriptionfrom-idOrigin stop ID (from search)to-idDestination stop IDdatetimeOptional: "18:30", "tomorrow 09:00", "2026-01-28 14:00"modeOptional: "depart" (default) or "arrive" Coordinate-based search: ./journey.sh "63.825#20.263" <to-id> [datetime] [mode] Use lat#lon format for coordinates (WGS84 decimal degrees).
Before searching, understand what the user wants:
User SaysIntentHow to Query"now", "next bus", "how do I get to"Travel NowNo datetime parameter"in 30 minutes", "in 1 hour"Depart LaterCalculate time, use depart mode"around 15:00", "sometime afternoon"Around TimeQuery with offset (see below)"arrive by 18:00", "need to be there at 9"Arrive ByUse arrive mode"tomorrow morning", "on Friday at 10"Future TimeUse 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 SaysCurrent: 14:00Query 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.
EmojiUse ForbusBus (Tabussen/Ultra)trainTrainwalkWalking segmentclockTime/durationclock1Departure timegoalArrival timepinStop/stationhouseOrigin (home/start)targetDestinationwarningDelay or disruptioncheckOn timearrows_counterclockwiseTransfer/change
Always include these key elements from the tool output: When to leave - The actual time user needs to start (including walking) Walking segments - Distance and time for any walking Transport departure - When the bus actually leaves Arrival time - When user reaches destination Line number and direction - Which bus to take
For a simple direct journey: **Leave now** from Vasaplan **Vasaplan** -> **Universitetet** Bus 1 (mot Mariehem) departs 09:07 Arrives 09:18 at Universitetet Total: 11 min For a journey with transfer: **Leave at 08:45** Walk 300m to Vasaplan (~4 min) **Vasaplan** -> **Umeå C** -> **Skellefteå** **Leg 1:** Bus 1 departs 08:51 Arrives Umeå C 09:05 Transfer at Umeå C (15 min) **Leg 2:** Bus 100 (mot Skellefteå) departs 09:20 Arrives Skellefteå busstation 11:45 Total: 3h | 1 change
Always show walking details: Distance in meters Include walking in the "leave time" calculation 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 Walk 5 min -> Bus 1 at 09:07 -> arrives 09:25 Total: 25 min **Option 2 - Leave in 15m (09:15)** Walk 5 min -> Bus 1 at 09:22 -> arrives 09:40 Total: 25 min **Option 3 - Leave in 30m (09:30)** Walk 5 min -> Bus 8 at 09:37 -> arrives 09:48 Total: 18 min | Faster but later departure Which works best for you?
Follow this workflow when a user asks for a trip:
Parse what the user wants: "How do I get to..." -> Travel now "I need to be there at 18:00" -> Arrive mode "Sometime around 3pm" -> Query 14:30, show range "In about an hour" -> Calculate from current time
Search for origin and destination separately: ./search-location.sh "Vasaplan?" ./search-location.sh "Universitetet?"
Check each result carefully: Exact or close match? - If the name matches what the user asked for, proceed. Multiple results returned? - The script shows up to 10 matches. If the first result isn't clearly correct, ask the user to confirm. Name significantly different? - If user asked for "university" and result shows "Umeå Universitet", confirm with user. No results found? - Try alternative strategies (see below).
When results don't match or are ambiguous, ask clarifying questions: I searched for "centrum" and found multiple locations: 1. Umeå Vasaplan (central bus hub) 2. Skellefteå centrum 3. Lycksele centrum Which one did you mean? When no results are found, try these strategies: Try with city name: # If "Storgatan 10" fails, try: ./search-location.sh "Storgatan 10, Umeå?" Try common variations: # "Universitetet" -> "Umeå universitet" # "Sjukhuset" -> "NUS" or "Norrlands universitetssjukhus" Use fuzzy search (add ?): ./search-location.sh "univ?"
Once you have confirmed IDs for both locations: ./journey.sh <from-id> <to-id> [datetime] [mode]
Use the formatting guide above to present results clearly. Always use actual numbers from the tool output - never estimate or speculate.
The search API is sensitive to formatting. Follow these rules:
User SaysSearch For"Vasaplan", "centrum""Umeå Vasaplan?""Universitetet", "uni""Umeå universitet?""NUS", "sjukhuset""Norrlands universitetssjukhus?""Ikea""IKEA Umeå?""Flygplatsen""Umeå Airport?""Järnvägsstationen", "tåget""Umeå centralstation?"
DestinationSearch ForSkellefteå"Skellefteå busstation?"Lycksele"Lycksele busstation?"Vindeln"Vindeln station?"Robertsfors"Robertsfors centrum?"Holmsund"Holmsund centrum?"
Include city name for better accuracy: ./search-location.sh "Storgatan 25, Umeå?" ./search-location.sh "Kungsgatan 10, Skellefteå?"
User: "How do I get from Vasaplan to NUS?" ./search-location.sh "Umeå Vasaplan" ./search-location.sh "NUS?" ./journey.sh 740020116 740023840 Response: **Leave now** from Vasaplan **Vasaplan** -> **Universitetssjukhuset** Bus 8 (mot Lyktvägen) departs 11:01 Arrives 11:06 Total: 5 min | Direct, no changes
User: "I need to get to Skellefteå from Umeå tomorrow at 8" ./search-location.sh "Umeå Vasaplan" ./search-location.sh "Skellefteå?" ./journey.sh 740020116 740000053 "tomorrow 08:00" Response: **Depart tomorrow at 08:04** from Vasaplan Walk 766m to Umeå Busstation (~11 min) **Umeå Busstation** -> **Skellefteå busstation** Bus 20 (Länstrafik mot Haparanda) departs 08:15 Arrives 10:40 at Skellefteå busstation Total: 2h 36min | Direct (with walk)
User: "I need to be at NUS by 08:00 tomorrow" ./search-location.sh "Umeå Vasaplan" ./search-location.sh "NUS?" ./journey.sh 740020116 740023840 "tomorrow 08:00" arrive Response: **Arrive by 08:00** at NUS **Vasaplan** -> **Universitetssjukhuset** Bus 9 departs **07:51** Arrives **07:56** - 4 min buffer Leave Vasaplan by 07:51 to arrive on time!
User: "I'm at Storgatan 50 in Umeå, how do I get to IKEA?" ./search-location.sh "Storgatan 50, Umeå?" # If no result, use coordinates ./journey.sh "63.826#20.263" 740066123
All times are Swedish local time (CET/CEST). FormatExampleMeaning(empty)Travel nowHH:MM"08:30"Today at 08:30tomorrow HH:MM"tomorrow 09:00"Tomorrow at 09:00YYYY-MM-DD HH:MM"2026-01-28 14:00"Specific date
============================================================== OPTION 1: Vasaplan -> Universitetet ============================================================== Date: 2026-01-28 Depart: 09:04 Arrive: 09:12 Changes: 0 LEGS: -> BUS Länstrafik - Buss 1 From: 09:04 Vasaplan (Umeå kn) To: 09:12 Universitetet (Umeå kn) Direction: mot Mariehem
TypeDescriptionBUSTabussen/Ultra/Länstrafik busJLTRegional bus (Länstrafik)JRERegional trainWALKWalking segment
OperatorDescriptionLänstrafiken VästerbottenRegional and local busesUltraUmeå local traffic (part of Länstrafiken)SJLong-distance trainsNorrtågRegional trains
The search returned no results. Strategies: Check spelling (Swedish: å, ä, ö) Try with city name suffix Use fuzzy search (add ?) Try common alternative names Ask user for clarification
No routes available. Strategies: Check if service operates at that hour (late night limited) Try different departure time Suggest alternative nearby stops Note that some regional routes have limited frequency
IssueSolution"Vasaplan" returns multipleUse "Umeå Vasaplan"Stop not foundTry fuzzy search with ?No late-night routesUltra has limited night serviceLong wait timesRegional routes may be hourly
StopIDNotesVasaplan740020116Central hubUniversitetssjukhuset (NUS)740023840HospitalUniversum740026881University areaUmeå Busstation-Regional bus departuresVästerslätt Centrum740045407Western suburb
StopIDNotesSkellefteå busstation740000053Regional hubLycksele busstation-Inland hubVindeln station-Train connectionRobertsfors centrum-Coastal route
This skill uses ResRobot API v2.1 from Trafiklab. Base URL: https://api.resrobot.se/v2.1/ Endpoints: Stop lookup: /location.name Journey planner: /trip Key Parameters: accessId - API key (required) format - json or xml originId / destId - Stop IDs date / time - Travel date/time searchForArrival - 1 for arrive-by searches Get API Key: Register at https://developer.trafiklab.se
Frequent service in central Umeå Lines 1-9 are most common Night buses (N-lines) on weekends Real-time info available in app
Line 100: Umeå - Skellefteå (frequent) Line 12/20: Coastal routes Lines 30-49: Inland routes Frequency varies by route
Vasaplan is the main hub for both Ultra and regional Many regional buses depart from Vasaplan, not train station Train station (Umeå C) is separate from bus station IKEA and Avion have good bus connections
Always ask when: Search returns no results: "I couldn't find [location]. Could you provide more details?" Multiple plausible matches: "I found several stops matching '[query]': [list]. Which one?" Result name very different from query: "You asked for '[user query]' but I found '[result name]'. Is this correct?" User request is vague: "From where in Umeå? Vasaplan (central), or another location?" Time is unclear: "When do you want to travel? Now, or at a specific time?"
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.