[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78RHVF0GYEXTPMKNCRAZHS3":3,"skill-same:01M78RHVF0GYEXTPMKNCRAZHS3":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M78RHVF0GYEXTPMKNCRAZHS3","tabussen",null,"Västerbotten & Umeå public transport trip planner (Tabussen\u002FUltra). Plans bus journeys using ResRobot API. Supports stops, addresses, coordinates, regional and local routes throughout Västerbotten county.","meghal86\u002Fstacksignal","meghal86","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F37388715?v=4","01M6CS2EW8SK89GH52R2ZEN8QQ","01M728J5CGY456EETEFG6HJBTM",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftabussen\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tabussen\ndescription: Västerbotten & Umeå public transport trip planner (Tabussen\u002FUltra). Plans bus journeys using ResRobot API. Supports stops, addresses, coordinates, regional and local routes throughout Västerbotten county.\nlicense: MIT\ncompatibility: Requires curl, jq. Works with Claude Code and compatible agents.\nmetadata:\n  author: simskii\n  version: \"1.0.0\"\n  region: sweden-vasterbotten\n---\n\n# Tabussen Trip Planner\n\nPlan public transport journeys in Västerbotten, Sweden - including Umeå local traffic (Ultra) and regional routes (Länstrafiken Västerbotten).\n\n## Overview\n\nThis skill uses the **ResRobot API** (Trafiklab) to provide journey planning for Tabussen\u002FUltra. ResRobot is Sweden's national public transport API covering all operators including Länstrafiken Västerbotten.\n\n**Coverage:**\n- Ultra (Umeå local bus traffic)\n- Länstrafiken Västerbotten (regional buses)\n- Connections to\u002Ffrom other Swedish regions\n- Train connections where applicable\n\n## Commands\n\n### 1. Search Location\n\nSearch for stops, stations, or points of interest.\n\n```bash\n.\u002Fsearch-location.sh \u003Cquery> [limit]\n```\n\n| Argument | Description |\n|----------|-------------|\n| `query` | Location name to search for (append `?` for fuzzy search) |\n| `limit` | Number of results to show (default: 5, max: 10) |\n\n**Output includes:**\n- `ID` - The stop identifier (use this in journey search)\n- `Name` - Official name of the stop\n- `Coordinates` - Latitude, longitude\n- `Weight` - Traffic volume indicator (higher = more traffic)\n\n**Search tips:**\n- Use `?` suffix for fuzzy\u002Fpartial matching: `\"Vasaplan?\"` \n- Exact search without `?`: `\"Vasaplan\"`\n- Include municipality for precision: `\"Umeå Vasaplan\"`\n\n### 2. Journey Search\n\nPlan a journey between two locations using their IDs.\n\n```bash\n.\u002Fjourney.sh \u003Cfrom-id> \u003Cto-id> [datetime] [mode]\n```\n\n| Argument | Description |\n|----------|-------------|\n| `from-id` | Origin stop ID (from search) |\n| `to-id` | Destination stop ID |\n| `datetime` | Optional: `\"18:30\"`, `\"tomorrow 09:00\"`, `\"2026-01-28 14:00\"` |\n| `mode` | Optional: `\"depart\"` (default) or `\"arrive\"` |\n\n**Coordinate-based search:**\n```bash\n.\u002Fjourney.sh \"63.825#20.263\" \u003Cto-id> [datetime] [mode]\n```\nUse `lat#lon` format for coordinates (WGS84 decimal degrees).\n\n---\n\n## Understanding User Time Intent\n\nBefore searching, understand what the user wants:\n\n### Intent Types\n\n| User Says | Intent | How to Query |\n|-----------|--------|--------------|\n| \"now\", \"next bus\", \"how do I get to\" | **Travel Now** | No datetime parameter |\n| \"in 30 minutes\", \"in 1 hour\" | **Depart Later** | Calculate time, use `depart` mode |\n| \"around 15:00\", \"sometime afternoon\" | **Around Time** | Query with offset (see below) |\n| \"arrive by 18:00\", \"need to be there at 9\" | **Arrive By** | Use `arrive` mode |\n| \"tomorrow morning\", \"on Friday at 10\" | **Future Time** | Use specific datetime |\n\n### Handling \"Around Time\" Queries\n\nWhen user wants options \"around\" a time, query 15-30 minutes earlier to show options before and after:\n\n```bash\n# User: \"I want to travel around 15:00\"\n# Query at 14:30 to get options spanning 14:30-16:00+\n.\u002Fjourney.sh ... \"14:30\" depart\n```\n\n### Relative Time Calculations\n\nConvert relative times to absolute:\n\n| User Says | Current: 14:00 | Query Time |\n|-----------|----------------|------------|\n| \"in 30m\" | -> | \"14:30\" |\n| \"in 1h\" | -> | \"15:00\" |\n| \"in 2 hours\" | -> | \"16:00\" |\n\n---\n\n## LLM Response Formatting\n\nWhen presenting journey results to users, use these emojis and formatting guidelines.\n\n### Emoji Reference\n\n| Emoji | Use For |\n|-------|---------|\n| `bus` | Bus (Tabussen\u002FUltra) |\n| `train` | Train |\n| `walk` | Walking segment |\n| `clock` | Time\u002Fduration |\n| `clock1` | Departure time |\n| `goal` | Arrival time |\n| `pin` | Stop\u002Fstation |\n| `house` | Origin (home\u002Fstart) |\n| `target` | Destination |\n| `warning` | Delay or disruption |\n| `check` | On time |\n| `arrows_counterclockwise` | Transfer\u002Fchange |\n\n### Response Structure\n\n**Always include these key elements from the tool output:**\n\n1. **When to leave** - The actual time user needs to start (including walking)\n2. **Walking segments** - Distance and time for any walking\n3. **Transport departure** - When the bus actually leaves\n4. **Arrival time** - When user reaches destination\n5. **Line number and direction** - Which bus to take\n\n### Example Response Format\n\n**For a simple direct journey:**\n```\n**Leave now** from Vasaplan\n\n**Vasaplan** -> **Universitetet**\nBus 1 (mot Mariehem) departs 09:07\nArrives 09:18 at Universitetet\n\nTotal: 11 min\n```\n\n**For a journey with transfer:**\n```\n**Leave at 08:45**\n\nWalk 300m to Vasaplan (~4 min)\n\n**Vasaplan** -> **Umeå C** -> **Skellefteå**\n\n**Leg 1:**\nBus 1 departs 08:51\nArrives Umeå C 09:05\n\nTransfer at Umeå C (15 min)\n\n**Leg 2:**\nBus 100 (mot Skellefteå) departs 09:20\nArrives Skellefteå busstation 11:45\n\nTotal: 3h | 1 change\n```\n\n### Walking Segment Details\n\n**Always show walking details:**\n- Distance in meters\n- Include walking in the \"leave time\" calculation\n- Walk time estimate: ~100m per minute (normal walking speed)\n\n### Presenting Multiple Options\n\nWhen showing journey options, make timing crystal clear:\n\n```\nI found 3 options for you:\n\n**Option 1 - Leave now (09:00)** Recommended\nWalk 5 min -> Bus 1 at 09:07 -> arrives 09:25\nTotal: 25 min\n\n**Option 2 - Leave in 15m (09:15)**\nWalk 5 min -> Bus 1 at 09:22 -> arrives 09:40\nTotal: 25 min\n\n**Option 3 - Leave in 30m (09:30)**\nWalk 5 min -> Bus 8 at 09:37 -> arrives 09:48\nTotal: 18 min | Faster but later departure\n\nWhich works best for you?\n```\n\n---\n\n## LLM Workflow: How to Plan a Trip\n\nFollow this workflow when a user asks for a trip:\n\n### Step 1: Understand Time Intent\n\nParse what the user wants:\n- **\"How do I get to...\"** -> Travel now\n- **\"I need to be there at 18:00\"** -> Arrive mode\n- **\"Sometime around 3pm\"** -> Query 14:30, show range\n- **\"In about an hour\"** -> Calculate from current time\n\n### Step 2: Search for Both Locations\n\nSearch for origin and destination separately:\n\n```bash\n.\u002Fsearch-location.sh \"Vasaplan?\"\n.\u002Fsearch-location.sh \"Universitetet?\"\n```\n\n### Step 3: Validate Search Results\n\n**Check each result carefully:**\n\n1. **Exact or close match?** - If the name matches what the user asked for, proceed.\n\n2. **Multiple results returned?** - The script shows up to 10 matches. If the first result isn't clearly correct, ask the user to confirm.\n\n3. **Name significantly different?** - If user asked for \"university\" and result shows \"Umeå Universitet\", confirm with user.\n\n4. **No results found?** - Try alternative strategies (see below).\n\n### Step 4: Handle Ambiguous or Failed Searches\n\n**When results don't match or are ambiguous, ask clarifying questions:**\n\n```\nI searched for \"centrum\" and found multiple locations:\n1. Umeå Vasaplan (central bus hub)\n2. Skellefteå centrum\n3. Lycksele centrum\n\nWhich one did you mean?\n```\n\n**When no results are found, try these strategies:**\n\n1. **Try with city name:**\n   ```bash\n   # If \"Storgatan 10\" fails, try:\n   .\u002Fsearch-location.sh \"Storgatan 10, Umeå?\"\n   ```\n\n2. **Try common variations:**\n   ```bash\n   # \"Universitetet\" -> \"Umeå universitet\"\n   # \"Sjukhuset\" -> \"NUS\" or \"Norrlands universitetssjukhus\"\n   ```\n\n3. **Use fuzzy search (add ?):**\n   ```bash\n   .\u002Fsearch-location.sh \"univ?\"\n   ```\n\n### Step 5: Execute Journey Search\n\nOnce you have confirmed IDs for both locations:\n\n```bash\n.\u002Fjourney.sh \u003Cfrom-id> \u003Cto-id> [datetime] [mode]\n```\n\n### Step 6: Format Response\n\nUse the formatting guide above to present results clearly. **Always use actual numbers from the tool output - never estimate or speculate.**\n\n---\n\n## Query Formatting Rules\n\n**The search API is sensitive to formatting. Follow these rules:**\n\n### Common Stop Names in Umeå\n\n| User Says | Search For |\n|-----------|------------|\n| \"Vasaplan\", \"centrum\" | `\"Umeå Vasaplan?\"` |\n| \"Universitetet\", \"uni\" | `\"Umeå universitet?\"` |\n| \"NUS\", \"sjukhuset\" | `\"Norrlands universitetssjukhus?\"` |\n| \"Ikea\" | `\"IKEA Umeå?\"` |\n| \"Flygplatsen\" | `\"Umeå Airport?\"` |\n| \"Järnvägsstationen\", \"tåget\" | `\"Umeå centralstation?\"` |\n\n### Regional Destinations\n\n| Destination | Search For |\n|-------------|------------|\n| Skellefteå | `\"Skellefteå busstation?\"` |\n| Lycksele | `\"Lycksele busstation?\"` |\n| Vindeln | `\"Vindeln station?\"` |\n| Robertsfors | `\"Robertsfors centrum?\"` |\n| Holmsund | `\"Holmsund centrum?\"` |\n\n### Street Addresses\n\nInclude city name for better accuracy:\n```bash\n.\u002Fsearch-location.sh \"Storgatan 25, Umeå?\"\n.\u002Fsearch-location.sh \"Kungsgatan 10, Skellefteå?\"\n```\n\n---\n\n## Examples\n\n### Example 1: Travel Now (Umeå Local)\n\nUser: \"How do I get from Vasaplan to NUS?\"\n\n```bash\n.\u002Fsearch-location.sh \"Umeå Vasaplan\"\n.\u002Fsearch-location.sh \"NUS?\"\n.\u002Fjourney.sh 740020116 740023840\n```\n\n**Response:**\n```\n**Leave now** from Vasaplan\n\n**Vasaplan** -> **Universitetssjukhuset**\nBus 8 (mot Lyktvägen) departs 11:01\nArrives 11:06\n\nTotal: 5 min | Direct, no changes\n```\n\n### Example 2: Regional Journey\n\nUser: \"I need to get to Skellefteå from Umeå tomorrow at 8\"\n\n```bash\n.\u002Fsearch-location.sh \"Umeå Vasaplan\"\n.\u002Fsearch-location.sh \"Skellefteå?\"\n.\u002Fjourney.sh 740020116 740000053 \"tomorrow 08:00\"\n```\n\n**Response:**\n```\n**Depart tomorrow at 08:04** from Vasaplan\n\nWalk 766m to Umeå Busstation (~11 min)\n\n**Umeå Busstation** -> **Skellefteå busstation**\nBus 20 (Länstrafik mot Haparanda) departs 08:15\nArrives 10:40 at Skellefteå busstation\n\nTotal: 2h 36min | Direct (with walk)\n```\n\n### Example 3: Arrive By Time\n\nUser: \"I need to be at NUS by 08:00 tomorrow\"\n\n```bash\n.\u002Fsearch-location.sh \"Umeå Vasaplan\"\n.\u002Fsearch-location.sh \"NUS?\"\n.\u002Fjourney.sh 740020116 740023840 \"tomorrow 08:00\" arrive\n```\n\n**Response:**\n```\n**Arrive by 08:00** at NUS\n\n**Vasaplan** -> **Universitetssjukhuset**\nBus 9 departs **07:51**\nArrives **07:56** - 4 min buffer\n\nLeave Vasaplan by 07:51 to arrive on time!\n```\n\n### Example 4: From Address\u002FCoordinates\n\nUser: \"I'm at Storgatan 50 in Umeå, how do I get to IKEA?\"\n\n```bash\n.\u002Fsearch-location.sh \"Storgatan 50, Umeå?\"\n# If no result, use coordinates\n.\u002Fjourney.sh \"63.826#20.263\" 740066123\n```\n\n---\n\n## DateTime Formats\n\nAll times are Swedish local time (CET\u002FCEST).\n\n| Format | Example | Meaning |\n|--------|---------|---------|\n| _(empty)_ | | Travel now |\n| `HH:MM` | `\"08:30\"` | Today at 08:30 |\n| `tomorrow HH:MM` | `\"tomorrow 09:00\"` | Tomorrow at 09:00 |\n| `YYYY-MM-DD HH:MM` | `\"2026-01-28 14:00\"` | Specific date |\n\n---\n\n## Output Format\n\n### Journey Option (Raw Tool Output)\n\n```\n==============================================================\nOPTION 1: Vasaplan -> Universitetet\n==============================================================\nDate:    2026-01-28\nDepart:  09:04\nArrive:  09:12\nChanges: 0\n\nLEGS:\n  -> BUS Länstrafik - Buss 1\n    From: 09:04 Vasaplan (Umeå kn)\n    To:   09:12 Universitetet (Umeå kn)\n    Direction: mot Mariehem\n```\n\n### Transport Types\n\n| Type | Description |\n|------|-------------|\n| `BUS` | Tabussen\u002FUltra\u002FLänstrafik bus |\n| `JLT` | Regional bus (Länstrafik) |\n| `JRE` | Regional train |\n| `WALK` | Walking segment |\n\n### Operators in Västerbotten\n\n| Operator | Description |\n|----------|-------------|\n| Länstrafiken Västerbotten | Regional and local buses |\n| Ultra | Umeå local traffic (part of Länstrafiken) |\n| SJ | Long-distance trains |\n| Norrtåg | Regional trains |\n\n---\n\n## Error Handling\n\n### \"No locations found\"\n\nThe search returned no results.\n\n**Strategies:**\n1. Check spelling (Swedish: å, ä, ö)\n2. Try with city name suffix\n3. Use fuzzy search (add ?)\n4. Try common alternative names\n5. Ask user for clarification\n\n### \"No journeys found\"\n\nNo routes available.\n\n**Strategies:**\n1. Check if service operates at that hour (late night limited)\n2. Try different departure time\n3. Suggest alternative nearby stops\n4. Note that some regional routes have limited frequency\n\n### Common Issues\n\n| Issue | Solution |\n|-------|----------|\n| \"Vasaplan\" returns multiple | Use \"Umeå Vasaplan\" |\n| Stop not found | Try fuzzy search with ? |\n| No late-night routes | Ultra has limited night service |\n| Long wait times | Regional routes may be hourly |\n\n---\n\n## Quick Reference\n\n### Popular Umeå Stops (Ultra)\n\n| Stop | ID | Notes |\n|------|-----|-------|\n| Vasaplan | 740020116 | Central hub |\n| Universitetssjukhuset (NUS) | 740023840 | Hospital |\n| Universum | 740026881 | University area |\n| Umeå Busstation | - | Regional bus departures |\n| Västerslätt Centrum | 740045407 | Western suburb |\n\n### Key Regional Stops\n\n| Stop | ID | Notes |\n|------|-----|-------|\n| Skellefteå busstation | 740000053 | Regional hub |\n| Lycksele busstation | - | Inland hub |\n| Vindeln station | - | Train connection |\n| Robertsfors centrum | - | Coastal route |\n\n---\n\n## API Details (For Script Development)\n\nThis skill uses ResRobot API v2.1 from Trafiklab.\n\n**Base URL:** `https:\u002F\u002Fapi.resrobot.se\u002Fv2.1\u002F`\n\n**Endpoints:**\n- Stop lookup: `\u002Flocation.name`\n- Journey planner: `\u002Ftrip`\n\n**Key Parameters:**\n- `accessId` - API key (required)\n- `format` - json or xml\n- `originId` \u002F `destId` - Stop IDs\n- `date` \u002F `time` - Travel date\u002Ftime\n- `searchForArrival` - 1 for arrive-by searches\n\n**Get API Key:** Register at https:\u002F\u002Fdeveloper.trafiklab.se\n\n---\n\n## Notes on Västerbotten Traffic\n\n### Ultra (Umeå Local)\n- Frequent service in central Umeå\n- Lines 1-9 are most common\n- Night buses (N-lines) on weekends\n- Real-time info available in app\n\n### Länstrafiken (Regional)\n- Line 100: Umeå - Skellefteå (frequent)\n- Line 12\u002F20: Coastal routes\n- Lines 30-49: Inland routes\n- Frequency varies by route\n\n### Tips for Users\n- Vasaplan is the main hub for both Ultra and regional\n- Many regional buses depart from Vasaplan, not train station\n- Train station (Umeå C) is separate from bus station\n- IKEA and Avion have good bus connections\n\n---\n\n## When to Ask Clarifying Questions\n\n**Always ask when:**\n\n1. **Search returns no results:**\n   - \"I couldn't find [location]. Could you provide more details?\"\n\n2. **Multiple plausible matches:**\n   - \"I found several stops matching '[query]': [list]. Which one?\"\n\n3. **Result name very different from query:**\n   - \"You asked for '[user query]' but I found '[result name]'. Is this correct?\"\n\n4. **User request is vague:**\n   - \"From where in Umeå? Vasaplan (central), or another location?\"\n\n5. **Time is unclear:**\n   - \"When do you want to travel? Now, or at a specific time?\"\n","# Tabussen Trip Planner\n\nPlan public transport journeys in Västerbotten, Sweden - including Umeå local traffic (Ultra) and regional routes (Länstrafiken Västerbotten).\n\n## Overview\n\nThis skill uses the **ResRobot API** (Trafiklab) to provide journey planning for Tabussen\u002FUltra. ResRobot is Sweden's national public transport API covering all operators including Länstrafiken Västerbotten.\n\n**Coverage:**\n- Ultra (Umeå local bus traffic)\n- Länstrafiken Västerbotten (regional buses)\n- Connections to\u002Ffrom other Swedish regions\n- Train connections where applicable\n\n## Commands\n\n### 1. Search Location\n\nSearch for stops, stations, or points of interest.\n\n```bash\n.\u002Fsearch-location.sh \u003Cquery> [limit]\n```\n\n| Argument | Description |\n|----------|-------------|\n| `query` | Location name to search for (append `?` for fuzzy search) |\n| `limit` | Number of results to show (default: 5, max: 10) |\n\n**Output includes:**\n- `ID` - The stop identifier (use this in journey search)\n- `Name` - Official name of the stop\n- `Coordinates` - Latitude, longitude\n- `Weight` - Traffic volume indicator (higher = more traffic)\n\n**Search tips:**\n- Use `?` suffix for fuzzy\u002Fpartial matching: `\"Vasaplan?\"` \n- Exact search without `?`: `\"Vasaplan\"`\n- Include municipality for precision: `\"Umeå Vasaplan\"`\n\n### 2. Journey Search\n\nPlan a journey between two locations using their IDs.\n\n```bash\n.\u002Fjourney.sh \u003Cfrom-id> \u003Cto-id> [datetime] [mode]\n```\n\n| Argument | Description |\n|----------|-------------|\n| `from-id` | Origin stop ID (from search) |\n| `to-id` | Destination stop ID |\n| `datetime` | Optional: `\"18:30\"`, `\"tomorrow 09:00\"`, `\"2026-01-28 14:00\"` |\n| `mode` | Optional: `\"depart\"` (default) or `\"arrive\"` |\n\n**Coordinate-based search:**\n```bash\n.\u002Fjourney.sh \"63.825#20.263\" \u003Cto-id> [datetime] [mode]\n```\nUse `lat#lon` format for coordinates (WGS84 decimal degrees).\n\n---\n\n## Understanding User Time Intent\n\nBefore searching, understand what the user wants:\n\n### Intent Types\n\n| User Says | Intent | How to Query |\n|-----------|--------|--------------|\n| \"now\", \"next bus\", \"how do I get to\" | **Travel Now** | No datetime parameter |\n| \"in 30 minutes\", \"in 1 hour\" | **Depart Later** | Calculate time, use `depart` mode |\n| \"around 15:00\", \"sometime afternoon\" | **Around Time** | Query with offset (see below) |\n| \"arrive by 18:00\", \"need to be there at 9\" | **Arrive By** | Use `arrive` mode |\n| \"tomorrow morning\", \"on Friday at 10\" | **Future Time** | Use specific datetime |\n\n### Handling \"Around Time\" Queries\n\nWhen user wants options \"around\" a time, query 15-30 minutes earlier to show options before and after:\n\n```bash\n# User: \"I want to travel around 15:00\"\n# Query at 14:30 to get options spanning 14:30-16:00+\n.\u002Fjourney.sh ... \"14:30\" depart\n```\n\n### Relative Time Calculations\n\nConvert relative times to absolute:\n\n| User Says | Current: 14:00 | Query Time |\n|-----------|----------------|------------|\n| \"in 30m\" | -> | \"14:30\" |\n| \"in 1h\" | -> | \"15:00\" |\n| \"in 2 hours\" | -> | \"16:00\" |\n\n---\n\n## LLM Response Formatting\n\nWhen presenting journey results to users, use these emojis and formatting guidelines.\n\n### Emoji Reference\n\n| Emoji | Use For |\n|-------|---------|\n| `bus` | Bus (Tabussen\u002FUltra) |\n| `train` | Train |\n| `walk` | Walking segment |\n| `clock` | Time\u002Fduration |\n| `clock1` | Departure time |\n| `goal` | Arrival time |\n| `pin` | Stop\u002Fstation |\n| `house` | Origin (home\u002Fstart) |\n| `target` | Destination |\n| `warning` | Delay or disruption |\n| `check` | On time |\n| `arrows_counterclockwise` | Transfer\u002Fchange |\n\n### Response Structure\n\n**Always include these key elements from the tool output:**\n\n1. **When to leave** - The actual time user needs to start (including walking)\n2. **Walking segments** - Distance and time for any walking\n3. **Transport departure** - When the bus actually leaves\n4. **Arrival time** - When user reaches destination\n5. **Line number and direction** - Which bus to take\n\n### Example Response Format\n\n**For a simple direct journey:**\n```\n**Leave now** from Vasaplan\n\n**Vasaplan** -> **Universitetet**\nBus 1 (mot Mariehem) departs 09:07\nArrives 09:18 at Universitetet\n\nTotal: 11 min\n```\n\n**For a journey with transfer:**\n```\n**Leave at 08:45**\n\nWalk 300m to Vasaplan (~4 min)\n\n**Vasaplan** -> **Umeå C** -> **Skellefteå**\n\n**Leg 1:**\nBus 1 departs 08:51\nArrives Umeå C 09:05\n\nTransfer at Umeå C (15 min)\n\n**Leg 2:**\nBus 100 (mot Skellefteå) departs 09:20\nArrives Skellefteå busstation 11:45\n\nTotal: 3h | 1 change\n```\n\n### Walking Segment Details\n\n**Always show walking details:**\n- Distance in meters\n- Include walking in the \"leave time\" calculation\n- Walk time estimate: ~100m per minute (normal walking speed)\n\n### Presenting Multiple Options\n\nWhen showing journey options, make timing crystal clear:\n\n```\nI found 3 options for you:\n\n**Option 1 - Leave now (09:00)** Recommended\nWalk 5 min -> Bus 1 at 09:07 -> arrives 09:25\nTotal: 25 min\n\n**Option 2 - Leave in 15m (09:15)**\nWalk 5 min -> Bus 1 at 09:22 -> arrives 09:40\nTotal: 25 min\n\n**Option 3 - Leave in 30m (09:30)**\nWalk 5 min -> Bus 8 at 09:37 -> arrives 09:48\nTotal: 18 min | Faster but later departure\n\nWhich works best for you?\n```\n\n---\n\n## LLM Workflow: How to Plan a Trip\n\nFollow this workflow when a user asks for a trip:\n\n### Step 1: Understand Time Intent\n\nParse what the user wants:\n- **\"How do I get to...\"** -> Travel now\n- **\"I need to be there at 18:00\"** -> Arrive mode\n- **\"Sometime around 3pm\"** -> Query 14:30, show range\n- **\"In about an hour\"** -> Calculate from current time\n\n### Step 2: Search for Both Locations\n\nSearch for origin and destination separately:\n\n```bash\n.\u002Fsearch-location.sh \"Vasaplan?\"\n.\u002Fsearch-location.sh \"Universitetet?\"\n```\n\n### Step 3: Validate Search Results\n\n**Check each result carefully:**\n\n1. **Exact or close match?** - If the name matches what the user asked for, proceed.\n\n2. **Multiple results returned?** - The script shows up to 10 matches. If the first result isn't clearly correct, ask the user to confirm.\n\n3. **Name significantly different?** - If user asked for \"university\" and result shows \"Umeå Universitet\", confirm with user.\n\n4. **No results found?** - Try alternative strategies (see below).\n\n### Step 4: Handle Ambiguous or Failed Searches\n\n**When results don't match or are ambiguous, ask clarifying questions:**\n\n```\nI searched for \"centrum\" and found multiple locations:\n1. Umeå Vasaplan (central bus hub)\n2. Skellefteå centrum\n3. Lycksele centrum\n\nWhich one did you mean?\n```\n\n**When no results are found, try these strategies:**\n\n1. **Try with city name:**\n   ```bash\n   # If \"Storgatan 10\" fails, try:\n   .\u002Fsearch-location.sh \"Storgatan 10, Umeå?\"\n   ```\n\n2. **Try common variations:**\n   ```bash\n   # \"Universitetet\" -> \"Umeå universitet\"\n   # \"Sjukhuset\" -> \"NUS\" or \"Norrlands universitetssjukhus\"\n   ```\n\n3. **Use fuzzy search (add ?):**\n   ```bash\n   .\u002Fsearch-location.sh \"univ?\"\n   ```\n\n### Step 5: Execute Journey Search\n\nOnce you have confirmed IDs for both locations:\n\n```bash\n.\u002Fjourney.sh \u003Cfrom-id> \u003Cto-id> [datetime] [mode]\n```\n\n### Step 6: Format Response\n\nUse the formatting guide above to present results clearly. **Always use actual numbers from the tool output - never estimate or speculate.**\n\n---\n\n## Query Formatting Rules\n\n**The search API is sensitive to formatting. Follow these rules:**\n\n### Common Stop Names in Umeå\n\n| User Says | Search For |\n|-----------|------------|\n| \"Vasaplan\", \"centrum\" | `\"Umeå Vasaplan?\"` |\n| \"Universitetet\", \"uni\" | `\"Umeå universitet?\"` |\n| \"NUS\", \"sjukhuset\" | `\"Norrlands universitetssjukhus?\"` |\n| \"Ikea\" | `\"IKEA Umeå?\"` |\n| \"Flygplatsen\" | `\"Umeå Airport?\"` |\n| \"Järnvägsstationen\", \"tåget\" | `\"Umeå centralstation?\"` |\n\n### Regional Destinations\n\n| Destination | Search For |\n|-------------|------------|\n| Skellefteå | `\"Skellefteå busstation?\"` |\n| Lycksele | `\"Lycksele busstation?\"` |\n| Vindeln | `\"Vindeln station?\"` |\n| Robertsfors | `\"Robertsfors centrum?\"` |\n| Holmsund | `\"Holmsund centrum?\"` |\n\n### Street Addresses\n\nInclude city name for better accuracy:\n```bash\n.\u002Fsearch-location.sh \"Storgatan 25, Umeå?\"\n.\u002Fsearch-location.sh \"Kungsgatan 10, Skellefteå?\"\n```\n\n---\n\n## Examples\n\n### Example 1: Travel Now (Umeå Local)\n\nUser: \"How do I get from Vasaplan to NUS?\"\n\n```bash\n.\u002Fsearch-location.sh \"Umeå Vasaplan\"\n.\u002Fsearch-location.sh \"NUS?\"\n.\u002Fjourney.sh 740020116 740023840\n```\n\n**Response:**\n```\n**Leave now** from Vasaplan\n\n**Vasaplan** -> **Universitetssjukhuset**\nBus 8 (mot Lyktvägen) departs 11:01\nArrives 11:06\n\nTotal: 5 min | Direct, no changes\n```\n\n### Example 2: Regional Journey\n\nUser: \"I need to get to Skellefteå from Umeå tomorrow at 8\"\n\n```bash\n.\u002Fsearch-location.sh \"Umeå Vasaplan\"\n.\u002Fsearch-location.sh \"Skellefteå?\"\n.\u002Fjourney.sh 740020116 740000053 \"tomorrow 08:00\"\n```\n\n**Response:**\n```\n**Depart tomorrow at 08:04** from Vasaplan\n\nWalk 766m to Umeå Busstation (~11 min)\n\n**Umeå Busstation** -> **Skellefteå busstation**\nBus 20 (Länstrafik mot Haparanda) departs 08:15\nArrives 10:40 at Skellefteå busstation\n\nTotal: 2h 36min | Direct (with walk)\n```\n\n### Example 3: Arrive By Time\n\nUser: \"I need to be at NUS by 08:00 tomorrow\"\n\n```bash\n.\u002Fsearch-location.sh \"Umeå Vasaplan\"\n.\u002Fsearch-location.sh \"NUS?\"\n.\u002Fjourney.sh 740020116 740023840 \"tomorrow 08:00\" arrive\n```\n\n**Response:**\n```\n**Arrive by 08:00** at NUS\n\n**Vasaplan** -> **Universitetssjukhuset**\nBus 9 departs **07:51**\nArrives **07:56** - 4 min buffer\n\nLeave Vasaplan by 07:51 to arrive on time!\n```\n\n### Example 4: From Address\u002FCoordinates\n\nUser: \"I'm at Storgatan 50 in Umeå, how do I get to IKEA?\"\n\n```bash\n.\u002Fsearch-location.sh \"Storgatan 50, Umeå?\"\n# If no result, use coordinates\n.\u002Fjourney.sh \"63.826#20.263\" 740066123\n```\n\n---\n\n## DateTime Formats\n\nAll times are Swedish local time (CET\u002FCEST).\n\n| Format | Example | Meaning |\n|--------|---------|---------|\n| _(empty)_ | | Travel now |\n| `HH:MM` | `\"08:30\"` | Today at 08:30 |\n| `tomorrow HH:MM` | `\"tomorrow 09:00\"` | Tomorrow at 09:00 |\n| `YYYY-MM-DD HH:MM` | `\"2026-01-28 14:00\"` | Specific date |\n\n---\n\n## Output Format\n\n### Journey Option (Raw Tool Output)\n\n```\n==============================================================\nOPTION 1: Vasaplan -> Universitetet\n==============================================================\nDate:    2026-01-28\nDepart:  09:04\nArrive:  09:12\nChanges: 0\n\nLEGS:\n  -> BUS Länstrafik - Buss 1\n    From: 09:04 Vasaplan (Umeå kn)\n    To:   09:12 Universitetet (Umeå kn)\n    Direction: mot Mariehem\n```\n\n### Transport Types\n\n| Type | Description |\n|------|-------------|\n| `BUS` | Tabussen\u002FUltra\u002FLänstrafik bus |\n| `JLT` | Regional bus (Länstrafik) |\n| `JRE` | Regional train |\n| `WALK` | Walking segment |\n\n### Operators in Västerbotten\n\n| Operator | Description |\n|----------|-------------|\n| Länstrafiken Västerbotten | Regional and local buses |\n| Ultra | Umeå local traffic (part of Länstrafiken) |\n| SJ | Long-distance trains |\n| Norrtåg | Regional trains |\n\n---\n\n## Error Handling\n\n### \"No locations found\"\n\nThe search returned no results.\n\n**Strategies:**\n1. Check spelling (Swedish: å, ä, ö)\n2. Try with city name suffix\n3. Use fuzzy search (add ?)\n4. Try common alternative names\n5. Ask user for clarification\n\n### \"No journeys found\"\n\nNo routes available.\n\n**Strategies:**\n1. Check if service operates at that hour (late night limited)\n2. Try different departure time\n3. Suggest alternative nearby stops\n4. Note that some regional routes have limited frequency\n\n### Common Issues\n\n| Issue | Solution |\n|-------|----------|\n| \"Vasaplan\" returns multiple | Use \"Umeå Vasaplan\" |\n| Stop not found | Try fuzzy search with ? |\n| No late-night routes | Ultra has limited night service |\n| Long wait times | Regional routes may be hourly |\n\n---\n\n## Quick Reference\n\n### Popular Umeå Stops (Ultra)\n\n| Stop | ID | Notes |\n|------|-----|-------|\n| Vasaplan | 740020116 | Central hub |\n| Universitetssjukhuset (NUS) | 740023840 | Hospital |\n| Universum | 740026881 | University area |\n| Umeå Busstation | - | Regional bus departures |\n| Västerslätt Centrum | 740045407 | Western suburb |\n\n### Key Regional Stops\n\n| Stop | ID | Notes |\n|------|-----|-------|\n| Skellefteå busstation | 740000053 | Regional hub |\n| Lycksele busstation | - | Inland hub |\n| Vindeln station | - | Train connection |\n| Robertsfors centrum | - | Coastal route |\n\n---\n\n## API Details (For Script Development)\n\nThis skill uses ResRobot API v2.1 from Trafiklab.\n\n**Base URL:** `https:\u002F\u002Fapi.resrobot.se\u002Fv2.1\u002F`\n\n**Endpoints:**\n- Stop lookup: `\u002Flocation.name`\n- Journey planner: `\u002Ftrip`\n\n**Key Parameters:**\n- `accessId` - API key (required)\n- `format` - json or xml\n- `originId` \u002F `destId` - Stop IDs\n- `date` \u002F `time` - Travel date\u002Ftime\n- `searchForArrival` - 1 for arrive-by searches\n\n**Get API Key:** Register at https:\u002F\u002Fdeveloper.trafiklab.se\n\n---\n\n## Notes on Västerbotten Traffic\n\n### Ultra (Umeå Local)\n- Frequent service in central Umeå\n- Lines 1-9 are most common\n- Night buses (N-lines) on weekends\n- Real-time info available in app\n\n### Länstrafiken (Regional)\n- Line 100: Umeå - Skellefteå (frequent)\n- Line 12\u002F20: Coastal routes\n- Lines 30-49: Inland routes\n- Frequency varies by route\n\n### Tips for Users\n- Vasaplan is the main hub for both Ultra and regional\n- Many regional buses depart from Vasaplan, not train station\n- Train station (Umeå C) is separate from bus station\n- IKEA and Avion have good bus connections\n\n---\n\n## When to Ask Clarifying Questions\n\n**Always ask when:**\n\n1. **Search returns no results:**\n   - \"I couldn't find [location]. Could you provide more details?\"\n\n2. **Multiple plausible matches:**\n   - \"I found several stops matching '[query]': [list]. Which one?\"\n\n3. **Result name very different from query:**\n   - \"You asked for '[user query]' but I found '[result name]'. Is this correct?\"\n\n4. **User request is vague:**\n   - \"From where in Umeå? Vasaplan (central), or another location?\"\n\n5. **Time is unclear:**\n   - \"When do you want to travel? Now, or at a specific time?\"\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"author":24,"region":25,"version":26},"simskii","sweden-vasterbotten","1.0.0","Requires curl, jq. Works with Claude Code and compatible agents.","main","54afe4b75ed2eb8f0feabb2f5b57dfa4bcbb3c44",".agents\u002Fskills\u002Ftabussen","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal","https:\u002F\u002Fgithub.com\u002Fmeghal86","2026-05-17 14:11:28",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add meghal86\u002Fstacksignal --skill tabussen",{"tool":40,"command":41},"bunx","bunx skills add meghal86\u002Fstacksignal --skill tabussen",{"tool":43,"command":44},"pnpm","pnpm dlx skills add meghal86\u002Fstacksignal --skill tabussen","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftabussen\u002FSKILL.md",true,[48,54,60],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"_meta.json","REFERENCE","参考文档",269,"https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftabussen\u002F_meta.json",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"journey.sh","SCRIPT","脚本",7589,"https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftabussen\u002Fjourney.sh",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"search-location.sh",2316,"https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftabussen\u002Fsearch-location.sh",[65,73,81,89,97,104],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M78XH0FRP65NYEDHF2BT7NB1","zvukogram","Text-to-Speech via Zvukogram API with SSML support. Use when you need to generate speech from text, create podcasts, voice notifications, or work with audio. Supports speed control, stress marks, English word transcription, and audio fragment merging.","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzvukogram\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzvukogram\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M78XEND5ASXYB6MN8AQQGJAF","zohomail","Zoho Mail API integration with managed OAuth. Send, receive, and manage emails, folders, and labels.\nUse this skill when users want to send emails, read messages, manage folders, or work with email labels in Zoho Mail.\nFor other third party apps, use the api-gateway skill (https:\u002F\u002Fclawhub.ai\u002Fbyungkyu\u002Fapi-gateway).\nRequires network access and valid Maton API key.","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzohomail\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzohomail\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M78XEBBV3C6DRZFAJXP6RDKS","zoho-recruit","Zoho Recruit API integration with managed OAuth. Manage candidates, job openings, interviews, and recruitment workflows.\nUse this skill when users want to read, create, update, or search recruitment data like candidates, job openings, interviews, and applications in Zoho Recruit.\nFor other third party apps, use the api-gateway skill (https:\u002F\u002Fclawhub.ai\u002Fbyungkyu\u002Fapi-gateway).\nRequires network access and valid Maton API key.","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-recruit\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-recruit\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M78XE5CQG75DZWYSKGXFR99T","zoho-people","Zoho People API integration with managed OAuth. Manage employees, departments, designations, attendance, and leave.\nUse this skill when users want to read, create, update, or query HR data like employees, departments, designations, and forms in Zoho People.\nFor other third party apps, use the api-gateway skill (https:\u002F\u002Fclawhub.ai\u002Fbyungkyu\u002Fapi-gateway).\nRequires network access and valid Maton API key.","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-people\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-people\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M78XDZKMZAJYFJJFT7MR5ZN2","zoho-mail","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-mail\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-mail\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M78XDST8JK0WVDA1F3VPNWXD","zoho-inventory","Zoho Inventory API integration with managed OAuth. Manage items, sales orders, invoices, purchase orders, bills, contacts, and shipments.\nUse this skill when users want to read, create, update, or delete inventory items, sales orders, invoices, purchase orders, bills, or other inventory records in Zoho Inventory.\nFor other third party apps, use the api-gateway skill (https:\u002F\u002Fclawhub.ai\u002Fbyungkyu\u002Fapi-gateway).\nRequires network access and valid Maton API key.","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-inventory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmeghal86\u002Fstacksignal\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzoho-inventory\u002FSKILL.md",[],[]]