{"id":47241,"plugin_id":"plugin_asdk_app_6abcd58cbfa88191ae9d5642bc45d9e6","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:32:44.758Z","digest":"79cbff38d79d4a42afd5365804e0c59945853a901adec7e6996a5b1d40078122","against":null,"payload":{"description":"Plan how cargo moves between real places — ports, terminals, inland cities — and show the route on NoMap's map. Use when someone asks how to ship, move, route or send freight between locations, asks how far apart two places are for a shipment, asks which legs or modes a movement needs, or asks to see a freight route on a map.","included_files":[{"relative_path":"references/tool-results.md","size_in_bytes":2396}],"name":"plan-freight-route","skill_md_contents":"---\nname: plan-freight-route\ndescription: Plan how cargo moves between real places — ports, terminals, inland cities — and show the route on NoMap's map. Use when someone asks how to ship, move, route or send freight between locations, asks how far apart two places are for a shipment, asks which legs or modes a movement needs, or asks to see a freight route on a map.\n---\n\nUse this skill for any request about moving cargo between places. It covers a\nsingle question (\"how far is Rotterdam to Shanghai?\") and a full planning\nconversation (\"we need these turbines from Hamburg to a site near Chennai\").\n\n## Plan the route\n\nCall `plan_route` **once** with the user's request in plain language. Pass the\nwhole journey in one call, including intermediate stops and a transport mode\nwhen the user named one: `\"Rotterdam to Shanghai via Kolkata\"`,\n`\"Munich to Rotterdam by rail\"`. Do not split a journey into one call per leg —\nthe tool calculates the stops itself, and separate calls produce distances that\ndo not add up.\n\nReport what comes back, in this shape:\n\n1. The places in order, each with the UN/LOCODE the tool returned.\n2. One line per leg: the mode, the endpoints, the distance.\n3. The total distance when there is more than one leg.\n4. The \"Open in NoMap\" link.\n5. The overview caveat.\n\n### Facts you must not invent\n\n- **Never write a UN/LOCODE the tool did not return.** These identify real\n  facilities and a plausible-looking guess is a wrong one. If a place has no\n  code in the result, name it without a code.\n- **Never state a distance, duration or cost the tool did not give you.** No\n  estimating from geography, no arithmetic across legs beyond the total.\n- **Report the mode the tool calculated, not the mode that was requested.**\n  When a `modeFallbacks` entry appears, a corridor for the requested mode was\n  not available and the distance shown belongs to the mode actually used. Say\n  so plainly: \"rail was requested, but the 2,787 km figure is a road routing.\"\n  Presenting a road distance under a rail label is the specific error this\n  rule exists to prevent.\n- Distances are planning overviews, not navigational advice. Carry that\n  caveat into your answer; do not present figures as sailing or driving\n  directions.\n\n### When a place cannot be identified\n\nThe tool returns an error naming what it could not resolve, often with\ncandidate places. Do not pick one and continue. Show the candidates, ask the\nuser which they meant, then call `plan_route` again with a clearer query. If\nthere are no candidates, ask for the country or the nearest port or city.\n\n## Show the route\n\nWhen the user wants to see the route — \"show me\", \"map\", \"picture\", \"what does\nthat look like\" — call `route_map` with the same query.\n\n**Display exactly what the tool returns.** Never draw, generate, sketch or\nrecreate a map of your own, and never substitute another image, however\nconvenient. An invented map misrepresents a calculated corridor, which is the\nwhole reason this tool exists.\n\nLeave `inlineImage` false. Set it only if you can decode a base64 image block\ninto a picture — a client that inlines base64 as text turns a map into roughly\n180,000 tokens of gibberish and shows the user nothing.\n\nUse `stats: \"none\"` when the user wants only the corridor; the default `\"all\"`\ndraws the full planning card with the distance panels.\n\n## Search and fetch\n\n`search` and `fetch` exist for flows that need a result identifier before the\ndetail — deep-research style retrieval. `search` resolves a request into\nresults carrying an id; `fetch` returns the full route for one of those ids.\n\nFor an ordinary planning request, call `plan_route` instead. It returns the\nsame route in one step.\n\n## Stay inside the workflow\n\nThese tools calculate routes between places. They do not know about live\nvessel positions, freight rates, customs or tariff rules, permits, vessel\navailability or delivery dates. When a request needs one of those, answer from\nyour own knowledge if you can and say plainly that it does not come from\nNoMap — do not imply the tools confirmed it.\n\nSee `references/tool-results.md` for the fields each tool returns and how to\nread them.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}