{
  "schemaVersion": "1.0",
  "item": {
    "slug": "skanetrafiken",
    "name": "Skanetrafiken Trip Planner",
    "source": "tencent",
    "type": "skill",
    "category": "通讯协作",
    "sourceUrl": "https://clawhub.ai/rezkam/skanetrafiken",
    "canonicalUrl": "https://clawhub.ai/rezkam/skanetrafiken",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/skanetrafiken",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=skanetrafiken",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "README.md",
      "SKILL.md",
      "journey.sh",
      "search-location.sh"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/skanetrafiken"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/skanetrafiken",
    "agentPageUrl": "https://openagent3.xyz/skills/skanetrafiken/agent",
    "manifestUrl": "https://openagent3.xyz/skills/skanetrafiken/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/skanetrafiken/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Skånetrafiken Trip Planner",
        "body": "Plan public transport journeys in Skåne, Sweden with real-time departure information."
      },
      {
        "title": "1. Search Location",
        "body": "Search for stations, addresses, or points of interest.\n\n./search-location.sh <query> [limit]\n\nArgumentDescriptionqueryLocation name to search forlimitNumber of results to show (default: 3, max: 10)\n\nOutput includes:\n\nID - The location identifier (use this in journey search)\nName - Official name of the location\nType - STOP_AREA (station), ADDRESS, or POI (point of interest)\nArea - Region/municipality\nCoordinates - Latitude, longitude\n\nWhen to increase limit:\n\nFirst result doesn't match user's intent\nUser's query is ambiguous (e.g., \"station\", \"centrum\")\nNeed to show user multiple options to choose from"
      },
      {
        "title": "2. Journey Search",
        "body": "Plan a journey between two locations using their IDs.\n\n./journey.sh <from-id> <from-type> <to-id> <to-type> [datetime] [mode]\n\nArgumentDescriptionfrom-idOrigin location ID (from search) or coordinates (lat#lon)from-typeSTOP_AREA, ADDRESS, POI, or LOCATION (for coordinates)to-idDestination location ID or coordinatesto-typeType of destinationdatetimeOptional: \"18:30\", \"tomorrow 09:00\", \"2026-01-15 09:00\"modeOptional: \"depart\" (default) or \"arrive\"\n\nImportant: The Journey API only accepts STOP_AREA and LOCATION types. For ADDRESS or POI results, use the coordinates as lat#lon with type LOCATION."
      },
      {
        "title": "Understanding User Time Intent",
        "body": "Before searching, understand what the user wants:"
      },
      {
        "title": "Intent Types",
        "body": "User SaysIntentHow to Query\"now\", \"next bus\", \"how do I get to\"Travel NowNo datetime parameter\"in 30 minutes\", \"in 1 hour\", \"after lunch\"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"
      },
      {
        "title": "Handling \"Around Time\" Queries",
        "body": "When user wants options \"around\" a time, query 15-30 minutes earlier to show options before and after:\n\n# User: \"I want to travel around 15:00\"\n# Query at 14:30 to get options spanning 14:30-16:00+\n./journey.sh ... \"14:30\" depart"
      },
      {
        "title": "Relative Time Calculations",
        "body": "Convert relative times to absolute:\n\nUser SaysCurrent: 14:00Query Time\"in 30m\"→\"14:30\"\"in 1h\"→\"15:00\"\"in 2 hours\"→\"16:00\""
      },
      {
        "title": "LLM Response Formatting",
        "body": "When presenting journey results to users, use these emojis and formatting guidelines."
      },
      {
        "title": "Emoji Reference",
        "body": "EmojiUse 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"
      },
      {
        "title": "Response Structure",
        "body": "Always include these key elements from the tool output:\n\nWhen to leave - The actual time user needs to start (including walking)\nWalking segments - Distance and time for any walking\nTransport departure - When the bus/train actually leaves\nArrival time - When user reaches destination\nAny delays - Show deviation from schedule"
      },
      {
        "title": "Example Response Format",
        "body": "For a simple direct journey:\n\n🏠 **Leave home at 09:00**\n\n🚶 Walk 450m to Möllevångstorget (5 min)\n\n📍 **Möllevångstorget** → 🎯 **Malmö C**\n🚌 Bus 5 departs 09:07 from Möllevångstorget\n🏁 Arrives 09:18 at Malmö C\n\n⏱️ Total: 18 min\n\nFor a journey with transfer:\n\n🏠 **Leave at 08:45**\n\n🚶 Walk 300m to Västra Hamnen (4 min)\n\n📍 **Västra Hamnen** → 🔄 **Malmö C** → 🎯 **Lund C**\n\n**Leg 1:**\n🚌 Bus 2 departs 08:51 [🛤️ Läge A]\n🏁 Arrives Malmö C 09:05\n\n🔄 Transfer at Malmö C (6 min)\n\n**Leg 2:**\n🚂 Pågatåg departs 09:11 [🛤️ Spår 4]\n🏁 Arrives Lund C 09:23\n\n⏱️ Total: 38 min | 🔄 1 change\n\nWith delays:\n\n🕐 **Depart 14:30** from Triangeln\n\n🚂 Öresundståg 1042 → København H\n⚠️ +8 min delay (expected 14:38 instead of 14:30)\n🏁 Arrives ~15:25 (normally 15:17)"
      },
      {
        "title": "Walking Segment Details",
        "body": "CRITICAL: Always show walking details from the tool output:\n\nDistance in meters (from line.distance)\nInclude walking in the \"leave time\" calculation\nShow walking at start AND end of journey\n\nExample tool output:\n\n→ WALK 450m from Kalendegatan to Möllevångstorget\n\nFormat as:\n\n🚶 Walk 450m to Möllevångstorget (~5 min)\n\nWalk time estimate: ~100m per minute (normal walking speed)"
      },
      {
        "title": "Presenting Multiple Options",
        "body": "When showing journey options, make timing crystal clear:\n\nI found 3 options for you:\n\n**Option 1 - Leave now (09:00)** ✅ Recommended\n🚶 5 min walk → 🚌 Bus 5 at 09:07 → arrives 09:25\n⏱️ Total: 25 min\n\n**Option 2 - Leave in 15m (09:15)**\n🚶 5 min walk → 🚌 Bus 5 at 09:22 → arrives 09:40\n⏱️ Total: 25 min\n\n**Option 3 - Leave in 30m (09:30)**\n🚶 5 min walk → 🚂 Train at 09:37 → arrives 09:48\n⏱️ Total: 18 min | Faster but later departure"
      },
      {
        "title": "Time Offset Notation",
        "body": "Use clear notation for departure times:\n\nNotationMeaning\"now\"Immediately\"in 15m\"15 minutes from now\"in 1h\"1 hour from now\"at 14:30\"Specific time"
      },
      {
        "title": "LLM Workflow: How to Plan a Trip",
        "body": "Follow this workflow when a user asks for a trip:"
      },
      {
        "title": "Step 1: Understand Time Intent",
        "body": "Parse what the user wants:\n\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"
      },
      {
        "title": "Step 2: Search for Both Locations",
        "body": "Search for origin and destination separately:\n\n./search-location.sh \"Malmö C\"\n./search-location.sh \"Emporia\""
      },
      {
        "title": "Step 3: Validate Search Results",
        "body": "Check each result carefully:\n\nExact or close match? - If the name matches what the user asked for, proceed.\n\n\nMultiple results returned? - The script shows up to 10 matches. If the first result isn't clearly correct, ask the user to confirm.\n\n\nName significantly different? - If user asked for \"the mall near Hyllie\" and result shows \"Emporia\", confirm with user: \"I found Emporia shopping center near Hyllie. Is this correct?\"\n\n\nNo results found? - Try alternative strategies (see below)."
      },
      {
        "title": "Step 4: Handle Ambiguous or Failed Searches",
        "body": "When results don't match or are ambiguous, ask clarifying questions:\n\nI searched for \"centrum\" and found multiple locations:\n1. Malmö Centrum (bus stop)\n2. Lund Centrum (bus stop)\n3. Helsingborg Centrum (bus stop)\n\nWhich one did you mean?\n\nWhen no results are found, try these strategies:\n\nTry with city name for addresses:\n# If \"Storgatan 10\" fails, try:\n./search-location.sh \"Storgatan 10, Malmö\"\n\n\n\nTry official station names:\n# If \"Malmö station\" fails, try:\n./search-location.sh \"Malmö C\"\n\n\n\nTry landmark name only (without city):\n# If \"Emporia, Malmö\" fails, try:\n./search-location.sh \"Emporia\"\n\n\n\nUse coordinates as last resort:\n\nIf you know the approximate location, use lat#lon format directly\nAsk user: \"I couldn't find that location. Can you provide the address or coordinates?\""
      },
      {
        "title": "Step 5: Convert Types for Journey API",
        "body": "The Journey API only accepts:\n\nSTOP_AREA - Bus/train stations (use ID directly)\nLOCATION - GPS coordinates as lat#lon\n\nIf search returns ADDRESS or POI:\n\nUse the coordinates from search result\nFormat as lat#lon with type LOCATION\n\nExample:\n\n# Search returns: ID: 123, Type: ADDRESS, Coordinates: 55.605, 13.003\n# Use in journey as:\n./journey.sh \"55.605#13.003\" LOCATION 9021012080000000 STOP_AREA"
      },
      {
        "title": "Step 6: Execute Journey Search",
        "body": "Once you have confirmed IDs/coordinates for both locations:\n\n./journey.sh <from-id> <from-type> <to-id> <to-type> [datetime] [mode]"
      },
      {
        "title": "Step 7: Format Response with Emojis",
        "body": "Use the emoji guide above to present results clearly. Always use actual numbers from the tool output - never speculate or estimate."
      },
      {
        "title": "Query Formatting Rules",
        "body": "The search API is sensitive to formatting. Follow these rules:"
      },
      {
        "title": "Landmarks and POIs: Name Only",
        "body": "Use the landmark name WITHOUT city name.\n\n# CORRECT\n./search-location.sh \"Emporia\"\n./search-location.sh \"Triangeln\"\n./search-location.sh \"Turning Torso\"\n\n# WRONG - city name breaks POI search\n./search-location.sh \"Emporia, Malmö\"        # May return wrong location!\n./search-location.sh \"Triangeln, Malmö\"      # Unnecessary, may fail"
      },
      {
        "title": "Street Addresses: Include City",
        "body": "Include city name for better accuracy.\n\n# CORRECT\n./search-location.sh \"Kalendegatan 12, Malmö\"\n./search-location.sh \"Storgatan 25, Lund\"\n./search-location.sh \"Drottninggatan 5, Helsingborg\"\n\n# RISKY - may be ambiguous\n./search-location.sh \"Kalendegatan 12\"       # Works if unambiguous"
      },
      {
        "title": "Train Stations: Use Official Names",
        "body": "Use \"C\" suffix for central stations.\n\n# CORRECT\n./search-location.sh \"Malmö C\"\n./search-location.sh \"Lund C\"\n./search-location.sh \"Helsingborg C\"\n./search-location.sh \"Malmö Hyllie\"\n./search-location.sh \"Malmö Triangeln\"\n\n# WRONG\n./search-location.sh \"Malmö\"                 # Ambiguous!\n./search-location.sh \"Malmö Central\"         # Not official name\n./search-location.sh \"Lund station\"          # Not official name"
      },
      {
        "title": "Copenhagen (Cross-border)",
        "body": "Use Danish names or common alternatives.\n\n# All work\n./search-location.sh \"København H\"\n./search-location.sh \"Nørreport\"\n./search-location.sh \"Copenhagen Airport\"\n./search-location.sh \"Köpenhamn\""
      },
      {
        "title": "Example 1: Travel Now",
        "body": "User: \"How do I get from Malmö C to Lund C?\"\n\n./search-location.sh \"Malmö C\"\n./search-location.sh \"Lund C\"\n./journey.sh 9021012080000000 STOP_AREA 9021012080040000 STOP_AREA\n\nResponse:\n\n🏠 **Leave now** from Malmö C\n\n📍 **Malmö C** → 🎯 **Lund C**\n🚂 Öresundståg 1324 departs 09:04 [🛤️ Spår 2b]\n🏁 Arrives 09:16 at Lund C [🛤️ Spår 1]\n\n⏱️ Total: 12 min | ✅ Direct, no changes"
      },
      {
        "title": "Example 2: Address with Walking",
        "body": "User: \"I need to go from Kalendegatan 12 in Malmö to Emporia\"\n\n./search-location.sh \"Kalendegatan 12, Malmö\"\n./search-location.sh \"Emporia\"\n./journey.sh \"55.595#13.001\" LOCATION \"55.563#12.973\" LOCATION\n\nResponse:\n\n🏠 **Leave at 10:05**\n\n🚶 Walk 320m to Möllevångstorget (~3 min)\n\n📍 **Möllevångstorget** → 🎯 **Emporia**\n🚌 Bus 32 departs 10:10\n🏁 Arrives 10:28 at Emporia\n\n🚶 Walk 150m to destination (~2 min)\n\n⏱️ Total: 25 min"
      },
      {
        "title": "Example 3: Arrive By Time",
        "body": "User: \"I need to be at Copenhagen central by 18:00 tomorrow\"\n\n./search-location.sh \"Malmö C\"\n./search-location.sh \"København H\"\n./journey.sh 9021012080000000 STOP_AREA 9921000008600626 STOP_AREA \"tomorrow 18:00\" arrive\n\nResponse:\n\n🎯 **Arrive by 18:00** at København H\n\n📍 **Malmö C** → 🎯 **København H**\n🚂 Öresundståg departs **17:21** [🛤️ Spår 1]\n🏁 Arrives **17:56** ✅ 4 min buffer\n\n⏱️ Journey: 35 min\n\n💡 Leave Malmö C by 17:21 to arrive on time!"
      },
      {
        "title": "Example 4: Around Time Query",
        "body": "User: \"I want to travel to Lund around 15:00\"\n\n# Query 30 min earlier to show options around 15:00\n./journey.sh 9021012080000000 STOP_AREA 9021012080040000 STOP_AREA \"14:30\"\n\nResponse:\n\nOptions around 15:00 for Malmö C → Lund C:\n\n**Option 1 - Depart 14:34** (in 25m)\n🚂 Pågatåg → arrives 14:52\n⏱️ 18 min\n\n**Option 2 - Depart 14:49** (in 40m)\n🚂 Öresundståg → arrives 15:01\n⏱️ 12 min\n\n**Option 3 - Depart 15:04** (in 55m) ✅ Closest to 15:00\n🚂 Pågatåg → arrives 15:22\n⏱️ 18 min\n\nWhich works best for you?"
      },
      {
        "title": "Example 5: Relative Time",
        "body": "User: \"I want to leave in about an hour\"\n\n# Current time: 13:00, so query for 14:00\n./journey.sh ... \"14:00\"\n\nResponse:\n\nOptions departing around 14:00 (in ~1h):\n\n**Leave at 13:55** (in 55m)\n🚶 5 min walk → 🚌 Bus 5 at 14:02 → arrives 14:25\n\n**Leave at 14:10** (in 1h 10m)\n🚶 5 min walk → 🚂 Train at 14:17 → arrives 14:35\n\nLet me know which one works!"
      },
      {
        "title": "Example 6: Journey with Delays",
        "body": "When tool output shows delays:\n\nFrom: 14:30 Malmö C [+8 min late]\n\nResponse:\n\n📍 **Malmö C** → 🎯 **Lund C**\n🚂 Öresundståg 1042\n⚠️ **Running 8 min late**\n🕐 Scheduled: 14:30 → Expected: ~14:38\n🏁 Arrives ~14:50 (normally 14:42)"
      },
      {
        "title": "When to Ask Clarifying Questions",
        "body": "Always ask when:\n\nSearch returns no results:\n\n\"I couldn't find [location]. Could you provide more details like the full address or nearby landmarks?\"\n\n\n\nMultiple plausible matches:\n\n\"I found several locations matching '[query]': [list]. Which one did you mean?\"\n\n\n\nResult name very different from query:\n\n\"You asked for '[user query]' but the closest match I found is '[result name]'. Is this correct?\"\n\n\n\nUser request is vague:\n\n\"From Malmö\" - \"Which location in Malmö? The central station (Malmö C), or a specific address?\"\n\n\n\nCross-border ambiguity:\n\n\"Copenhagen\" could mean different stations - confirm if they want København H (central), Airport, or another station.\n\n\n\nTime is unclear:\n\n\"When do you want to travel? Now, or at a specific time?\""
      },
      {
        "title": "DateTime Formats",
        "body": "All times are Swedish local time (CET/CEST).\n\nFormatExampleMeaning(empty)Travel nowHH:MM\"18:30\"Today at 18:30tomorrow HH:MM\"tomorrow 09:00\"Tomorrow at 09:00YYYY-MM-DD HH:MM\"2026-01-15 09:00\"Specific date"
      },
      {
        "title": "Journey Option (Raw Tool Output)",
        "body": "══════════════════════════════════════════════════════════════\nOPTION 1: Malmö C → Lund C\n══════════════════════════════════════════════════════════════\nDate:    2026-01-14\nDepart:  09:04\nArrive:  09:16\nChanges: 0\n\nLEGS:\n  → ORESUND Öresundståg 1324\n    From: 09:04 Malmö C [Spår 2b]\n    To:   09:16 Lund C [Spår 1]\n    Direction: mot Helsingborg C"
      },
      {
        "title": "Transport Types",
        "body": "TypeEmojiDescriptionTRAIN🚂Pågatåg (regional train)ORESUND🚂Öresundståg (cross-border train)BUS🚌City or regional busWALK🚶Walking segmentTRAM🚋Tram/light railMETRO🚇Copenhagen MetroFERRY⛴️Ferry"
      },
      {
        "title": "Status Indicators",
        "body": "IndicatorEmojiMeaning(none)✅On time[+X min late]⚠️Delayed[-X min early]ℹ️Running early[PASSED]❌Already departedAVVIKELSE🚨Service disruption"
      },
      {
        "title": "\"No locations found\"",
        "body": "The search returned no results.\n\nStrategies:\n\nCheck spelling (Swedish: å, ä, ö)\nTry official station names with \"C\" for central\nFor landmarks, remove city suffix\nFor addresses, add city name\nAsk user for clarification"
      },
      {
        "title": "\"No journeys found\"",
        "body": "No routes available.\n\nStrategies:\n\nCheck if service operates at that hour (late night/early morning limited)\nTry different departure time\nSuggest alternative nearby stops"
      },
      {
        "title": "Quick Reference",
        "body": "Location TypeSearch FormatJourney TypeTrain station\"Malmö C\"STOP_AREABus stop\"Möllevångstorget\"STOP_AREAAddress\"Street 12, City\"Use coords → LOCATIONLandmark/POI\"Emporia\" (no city!)Use coords → LOCATIONCoordinates55.605#13.003LOCATION"
      }
    ],
    "body": "Skånetrafiken Trip Planner\n\nPlan public transport journeys in Skåne, Sweden with real-time departure information.\n\nCommands\n1. Search Location\n\nSearch for stations, addresses, or points of interest.\n\n./search-location.sh <query> [limit]\n\nArgument\tDescription\nquery\tLocation name to search for\nlimit\tNumber of results to show (default: 3, max: 10)\n\nOutput includes:\n\nID - The location identifier (use this in journey search)\nName - Official name of the location\nType - STOP_AREA (station), ADDRESS, or POI (point of interest)\nArea - Region/municipality\nCoordinates - Latitude, longitude\n\nWhen to increase limit:\n\nFirst result doesn't match user's intent\nUser's query is ambiguous (e.g., \"station\", \"centrum\")\nNeed to show user multiple options to choose from\n2. Journey Search\n\nPlan a journey between two locations using their IDs.\n\n./journey.sh <from-id> <from-type> <to-id> <to-type> [datetime] [mode]\n\nArgument\tDescription\nfrom-id\tOrigin location ID (from search) or coordinates (lat#lon)\nfrom-type\tSTOP_AREA, ADDRESS, POI, or LOCATION (for coordinates)\nto-id\tDestination location ID or coordinates\nto-type\tType of destination\ndatetime\tOptional: \"18:30\", \"tomorrow 09:00\", \"2026-01-15 09:00\"\nmode\tOptional: \"depart\" (default) or \"arrive\"\n\nImportant: The Journey API only accepts STOP_AREA and LOCATION types. For ADDRESS or POI results, use the coordinates as lat#lon with type LOCATION.\n\nUnderstanding User Time Intent\n\nBefore searching, understand what the user wants:\n\nIntent Types\nUser Says\tIntent\tHow to Query\n\"now\", \"next bus\", \"how do I get to\"\tTravel Now\tNo datetime parameter\n\"in 30 minutes\", \"in 1 hour\", \"after lunch\"\tDepart Later\tCalculate time, use depart mode\n\"around 15:00\", \"sometime afternoon\"\tAround Time\tQuery with offset (see below)\n\"arrive by 18:00\", \"need to be there at 9\"\tArrive By\tUse arrive mode\n\"tomorrow morning\", \"on Friday at 10\"\tFuture Time\tUse specific datetime\nHandling \"Around Time\" Queries\n\nWhen user wants options \"around\" a time, query 15-30 minutes earlier to show options before and after:\n\n# User: \"I want to travel around 15:00\"\n# Query at 14:30 to get options spanning 14:30-16:00+\n./journey.sh ... \"14:30\" depart\n\nRelative Time Calculations\n\nConvert relative times to absolute:\n\nUser Says\tCurrent: 14:00\tQuery Time\n\"in 30m\"\t→\t\"14:30\"\n\"in 1h\"\t→\t\"15:00\"\n\"in 2 hours\"\t→\t\"16:00\"\nLLM Response Formatting\n\nWhen presenting journey results to users, use these emojis and formatting guidelines.\n\nEmoji Reference\nEmoji\tUse For\n🚂\tTrain (Pågatåg, Öresundståg)\n🚌\tBus\n🚇\tMetro (Copenhagen)\n🚋\tTram\n⛴️\tFerry\n🚶\tWalking segment\n⏱️\tTime/duration\n🕐\tDeparture time\n🏁\tArrival time\n📍\tStop/station\n🏠\tOrigin (home/start)\n🎯\tDestination\n⚠️\tDelay or disruption\n✅\tOn time\n🔄\tTransfer/change\n🛤️\tPlatform/track\nResponse Structure\n\nAlways include these key elements from the tool output:\n\nWhen to leave - The actual time user needs to start (including walking)\nWalking segments - Distance and time for any walking\nTransport departure - When the bus/train actually leaves\nArrival time - When user reaches destination\nAny delays - Show deviation from schedule\nExample Response Format\n\nFor a simple direct journey:\n\n🏠 **Leave home at 09:00**\n\n🚶 Walk 450m to Möllevångstorget (5 min)\n\n📍 **Möllevångstorget** → 🎯 **Malmö C**\n🚌 Bus 5 departs 09:07 from Möllevångstorget\n🏁 Arrives 09:18 at Malmö C\n\n⏱️ Total: 18 min\n\n\nFor a journey with transfer:\n\n🏠 **Leave at 08:45**\n\n🚶 Walk 300m to Västra Hamnen (4 min)\n\n📍 **Västra Hamnen** → 🔄 **Malmö C** → 🎯 **Lund C**\n\n**Leg 1:**\n🚌 Bus 2 departs 08:51 [🛤️ Läge A]\n🏁 Arrives Malmö C 09:05\n\n🔄 Transfer at Malmö C (6 min)\n\n**Leg 2:**\n🚂 Pågatåg departs 09:11 [🛤️ Spår 4]\n🏁 Arrives Lund C 09:23\n\n⏱️ Total: 38 min | 🔄 1 change\n\n\nWith delays:\n\n🕐 **Depart 14:30** from Triangeln\n\n🚂 Öresundståg 1042 → København H\n⚠️ +8 min delay (expected 14:38 instead of 14:30)\n🏁 Arrives ~15:25 (normally 15:17)\n\nWalking Segment Details\n\nCRITICAL: Always show walking details from the tool output:\n\nDistance in meters (from line.distance)\nInclude walking in the \"leave time\" calculation\nShow walking at start AND end of journey\n\nExample tool output:\n\n→ WALK 450m from Kalendegatan to Möllevångstorget\n\n\nFormat as:\n\n🚶 Walk 450m to Möllevångstorget (~5 min)\n\n\nWalk time estimate: ~100m per minute (normal walking speed)\n\nPresenting Multiple Options\n\nWhen showing journey options, make timing crystal clear:\n\nI found 3 options for you:\n\n**Option 1 - Leave now (09:00)** ✅ Recommended\n🚶 5 min walk → 🚌 Bus 5 at 09:07 → arrives 09:25\n⏱️ Total: 25 min\n\n**Option 2 - Leave in 15m (09:15)**\n🚶 5 min walk → 🚌 Bus 5 at 09:22 → arrives 09:40\n⏱️ Total: 25 min\n\n**Option 3 - Leave in 30m (09:30)**\n🚶 5 min walk → 🚂 Train at 09:37 → arrives 09:48\n⏱️ Total: 18 min | Faster but later departure\n\nTime Offset Notation\n\nUse clear notation for departure times:\n\nNotation\tMeaning\n\"now\"\tImmediately\n\"in 15m\"\t15 minutes from now\n\"in 1h\"\t1 hour from now\n\"at 14:30\"\tSpecific time\nLLM Workflow: How to Plan a Trip\n\nFollow this workflow when a user asks for a trip:\n\nStep 1: Understand Time Intent\n\nParse what the user wants:\n\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\nStep 2: Search for Both Locations\n\nSearch for origin and destination separately:\n\n./search-location.sh \"Malmö C\"\n./search-location.sh \"Emporia\"\n\nStep 3: Validate Search Results\n\nCheck each result carefully:\n\nExact or close match? - If the name matches what the user asked for, proceed.\n\nMultiple results returned? - The script shows up to 10 matches. If the first result isn't clearly correct, ask the user to confirm.\n\nName significantly different? - If user asked for \"the mall near Hyllie\" and result shows \"Emporia\", confirm with user: \"I found Emporia shopping center near Hyllie. Is this correct?\"\n\nNo results found? - Try alternative strategies (see below).\n\nStep 4: Handle Ambiguous or Failed Searches\n\nWhen results don't match or are ambiguous, ask clarifying questions:\n\nI searched for \"centrum\" and found multiple locations:\n1. Malmö Centrum (bus stop)\n2. Lund Centrum (bus stop)\n3. Helsingborg Centrum (bus stop)\n\nWhich one did you mean?\n\n\nWhen no results are found, try these strategies:\n\nTry with city name for addresses:\n\n# If \"Storgatan 10\" fails, try:\n./search-location.sh \"Storgatan 10, Malmö\"\n\n\nTry official station names:\n\n# If \"Malmö station\" fails, try:\n./search-location.sh \"Malmö C\"\n\n\nTry landmark name only (without city):\n\n# If \"Emporia, Malmö\" fails, try:\n./search-location.sh \"Emporia\"\n\n\nUse coordinates as last resort:\n\nIf you know the approximate location, use lat#lon format directly\nAsk user: \"I couldn't find that location. Can you provide the address or coordinates?\"\nStep 5: Convert Types for Journey API\n\nThe Journey API only accepts:\n\nSTOP_AREA - Bus/train stations (use ID directly)\nLOCATION - GPS coordinates as lat#lon\n\nIf search returns ADDRESS or POI:\n\nUse the coordinates from search result\nFormat as lat#lon with type LOCATION\n\nExample:\n\n# Search returns: ID: 123, Type: ADDRESS, Coordinates: 55.605, 13.003\n# Use in journey as:\n./journey.sh \"55.605#13.003\" LOCATION 9021012080000000 STOP_AREA\n\nStep 6: Execute Journey Search\n\nOnce you have confirmed IDs/coordinates for both locations:\n\n./journey.sh <from-id> <from-type> <to-id> <to-type> [datetime] [mode]\n\nStep 7: Format Response with Emojis\n\nUse the emoji guide above to present results clearly. Always use actual numbers from the tool output - never speculate or estimate.\n\nQuery Formatting Rules\n\nThe search API is sensitive to formatting. Follow these rules:\n\nLandmarks and POIs: Name Only\n\nUse the landmark name WITHOUT city name.\n\n# CORRECT\n./search-location.sh \"Emporia\"\n./search-location.sh \"Triangeln\"\n./search-location.sh \"Turning Torso\"\n\n# WRONG - city name breaks POI search\n./search-location.sh \"Emporia, Malmö\"        # May return wrong location!\n./search-location.sh \"Triangeln, Malmö\"      # Unnecessary, may fail\n\nStreet Addresses: Include City\n\nInclude city name for better accuracy.\n\n# CORRECT\n./search-location.sh \"Kalendegatan 12, Malmö\"\n./search-location.sh \"Storgatan 25, Lund\"\n./search-location.sh \"Drottninggatan 5, Helsingborg\"\n\n# RISKY - may be ambiguous\n./search-location.sh \"Kalendegatan 12\"       # Works if unambiguous\n\nTrain Stations: Use Official Names\n\nUse \"C\" suffix for central stations.\n\n# CORRECT\n./search-location.sh \"Malmö C\"\n./search-location.sh \"Lund C\"\n./search-location.sh \"Helsingborg C\"\n./search-location.sh \"Malmö Hyllie\"\n./search-location.sh \"Malmö Triangeln\"\n\n# WRONG\n./search-location.sh \"Malmö\"                 # Ambiguous!\n./search-location.sh \"Malmö Central\"         # Not official name\n./search-location.sh \"Lund station\"          # Not official name\n\nCopenhagen (Cross-border)\n\nUse Danish names or common alternatives.\n\n# All work\n./search-location.sh \"København H\"\n./search-location.sh \"Nørreport\"\n./search-location.sh \"Copenhagen Airport\"\n./search-location.sh \"Köpenhamn\"\n\nExamples\nExample 1: Travel Now\n\nUser: \"How do I get from Malmö C to Lund C?\"\n\n./search-location.sh \"Malmö C\"\n./search-location.sh \"Lund C\"\n./journey.sh 9021012080000000 STOP_AREA 9021012080040000 STOP_AREA\n\n\nResponse:\n\n🏠 **Leave now** from Malmö C\n\n📍 **Malmö C** → 🎯 **Lund C**\n🚂 Öresundståg 1324 departs 09:04 [🛤️ Spår 2b]\n🏁 Arrives 09:16 at Lund C [🛤️ Spår 1]\n\n⏱️ Total: 12 min | ✅ Direct, no changes\n\nExample 2: Address with Walking\n\nUser: \"I need to go from Kalendegatan 12 in Malmö to Emporia\"\n\n./search-location.sh \"Kalendegatan 12, Malmö\"\n./search-location.sh \"Emporia\"\n./journey.sh \"55.595#13.001\" LOCATION \"55.563#12.973\" LOCATION\n\n\nResponse:\n\n🏠 **Leave at 10:05**\n\n🚶 Walk 320m to Möllevångstorget (~3 min)\n\n📍 **Möllevångstorget** → 🎯 **Emporia**\n🚌 Bus 32 departs 10:10\n🏁 Arrives 10:28 at Emporia\n\n🚶 Walk 150m to destination (~2 min)\n\n⏱️ Total: 25 min\n\nExample 3: Arrive By Time\n\nUser: \"I need to be at Copenhagen central by 18:00 tomorrow\"\n\n./search-location.sh \"Malmö C\"\n./search-location.sh \"København H\"\n./journey.sh 9021012080000000 STOP_AREA 9921000008600626 STOP_AREA \"tomorrow 18:00\" arrive\n\n\nResponse:\n\n🎯 **Arrive by 18:00** at København H\n\n📍 **Malmö C** → 🎯 **København H**\n🚂 Öresundståg departs **17:21** [🛤️ Spår 1]\n🏁 Arrives **17:56** ✅ 4 min buffer\n\n⏱️ Journey: 35 min\n\n💡 Leave Malmö C by 17:21 to arrive on time!\n\nExample 4: Around Time Query\n\nUser: \"I want to travel to Lund around 15:00\"\n\n# Query 30 min earlier to show options around 15:00\n./journey.sh 9021012080000000 STOP_AREA 9021012080040000 STOP_AREA \"14:30\"\n\n\nResponse:\n\nOptions around 15:00 for Malmö C → Lund C:\n\n**Option 1 - Depart 14:34** (in 25m)\n🚂 Pågatåg → arrives 14:52\n⏱️ 18 min\n\n**Option 2 - Depart 14:49** (in 40m)\n🚂 Öresundståg → arrives 15:01\n⏱️ 12 min\n\n**Option 3 - Depart 15:04** (in 55m) ✅ Closest to 15:00\n🚂 Pågatåg → arrives 15:22\n⏱️ 18 min\n\nWhich works best for you?\n\nExample 5: Relative Time\n\nUser: \"I want to leave in about an hour\"\n\n# Current time: 13:00, so query for 14:00\n./journey.sh ... \"14:00\"\n\n\nResponse:\n\nOptions departing around 14:00 (in ~1h):\n\n**Leave at 13:55** (in 55m)\n🚶 5 min walk → 🚌 Bus 5 at 14:02 → arrives 14:25\n\n**Leave at 14:10** (in 1h 10m)\n🚶 5 min walk → 🚂 Train at 14:17 → arrives 14:35\n\nLet me know which one works!\n\nExample 6: Journey with Delays\n\nWhen tool output shows delays:\n\nFrom: 14:30 Malmö C [+8 min late]\n\n\nResponse:\n\n📍 **Malmö C** → 🎯 **Lund C**\n🚂 Öresundståg 1042\n⚠️ **Running 8 min late**\n🕐 Scheduled: 14:30 → Expected: ~14:38\n🏁 Arrives ~14:50 (normally 14:42)\n\nWhen to Ask Clarifying Questions\n\nAlways ask when:\n\nSearch returns no results:\n\n\"I couldn't find [location]. Could you provide more details like the full address or nearby landmarks?\"\n\nMultiple plausible matches:\n\n\"I found several locations matching '[query]': [list]. Which one did you mean?\"\n\nResult name very different from query:\n\n\"You asked for '[user query]' but the closest match I found is '[result name]'. Is this correct?\"\n\nUser request is vague:\n\n\"From Malmö\" - \"Which location in Malmö? The central station (Malmö C), or a specific address?\"\n\nCross-border ambiguity:\n\n\"Copenhagen\" could mean different stations - confirm if they want København H (central), Airport, or another station.\n\nTime is unclear:\n\n\"When do you want to travel? Now, or at a specific time?\"\nDateTime Formats\n\nAll times are Swedish local time (CET/CEST).\n\nFormat\tExample\tMeaning\n(empty)\t\tTravel now\nHH:MM\t\"18:30\"\tToday at 18:30\ntomorrow HH:MM\t\"tomorrow 09:00\"\tTomorrow at 09:00\nYYYY-MM-DD HH:MM\t\"2026-01-15 09:00\"\tSpecific date\nOutput Format\nJourney Option (Raw Tool Output)\n══════════════════════════════════════════════════════════════\nOPTION 1: Malmö C → Lund C\n══════════════════════════════════════════════════════════════\nDate:    2026-01-14\nDepart:  09:04\nArrive:  09:16\nChanges: 0\n\nLEGS:\n  → ORESUND Öresundståg 1324\n    From: 09:04 Malmö C [Spår 2b]\n    To:   09:16 Lund C [Spår 1]\n    Direction: mot Helsingborg C\n\nTransport Types\nType\tEmoji\tDescription\nTRAIN\t🚂\tPågatåg (regional train)\nORESUND\t🚂\tÖresundståg (cross-border train)\nBUS\t🚌\tCity or regional bus\nWALK\t🚶\tWalking segment\nTRAM\t🚋\tTram/light rail\nMETRO\t🚇\tCopenhagen Metro\nFERRY\t⛴️\tFerry\nStatus Indicators\nIndicator\tEmoji\tMeaning\n(none)\t✅\tOn time\n[+X min late]\t⚠️\tDelayed\n[-X min early]\tℹ️\tRunning early\n[PASSED]\t❌\tAlready departed\nAVVIKELSE\t🚨\tService disruption\nError Handling\n\"No locations found\"\n\nThe search returned no results.\n\nStrategies:\n\nCheck spelling (Swedish: å, ä, ö)\nTry official station names with \"C\" for central\nFor landmarks, remove city suffix\nFor addresses, add city name\nAsk user for clarification\n\"No journeys found\"\n\nNo routes available.\n\nStrategies:\n\nCheck if service operates at that hour (late night/early morning limited)\nTry different departure time\nSuggest alternative nearby stops\nQuick Reference\nLocation Type\tSearch Format\tJourney Type\nTrain station\t\"Malmö C\"\tSTOP_AREA\nBus stop\t\"Möllevångstorget\"\tSTOP_AREA\nAddress\t\"Street 12, City\"\tUse coords → LOCATION\nLandmark/POI\t\"Emporia\" (no city!)\tUse coords → LOCATION\nCoordinates\t55.605#13.003\tLOCATION"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/rezkam/skanetrafiken",
    "publisherUrl": "https://clawhub.ai/rezkam/skanetrafiken",
    "owner": "rezkam",
    "version": "1.2.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/skanetrafiken",
    "downloadUrl": "https://openagent3.xyz/downloads/skanetrafiken",
    "agentUrl": "https://openagent3.xyz/skills/skanetrafiken/agent",
    "manifestUrl": "https://openagent3.xyz/skills/skanetrafiken/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/skanetrafiken/agent.md"
  }
}