{"id":15302,"plugin_id":"plugin_asdk_app_6aa1bdcc3dc88191ab776ae829b19175","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:11:09.344Z","digest":"28a8eedccd10783b25353456a1eb2fba0d4b7ed2bb5a95a6ab89bc4c3065cbc1","against":null,"payload":{"description":"Produce a concise dispatcher-to-driver or dispatcher-to-dispatcher road-freight handover and use HaulNavi EU calculations when cost or confirmed driving-time capacity matters.","included_files":[],"name":"dispatch-handover","skill_md_contents":"---\nname: dispatch-handover\ndescription: Produce a concise dispatcher-to-driver or dispatcher-to-dispatcher road-freight handover and use HaulNavi EU calculations when cost or confirmed driving-time capacity matters.\n---\n\nCreate a structured operational handover from information explicitly provided in the conversation. Do not request the full chat history.\n\nUse this order when the data exists: mission reference; pickup; delivery; cargo/handling notes; booking references; timing; vehicle/trailer; documents; route/parking notes; customer instructions; open issues; next action.\n\nWhen the user provides an estimated driving duration and a driving-time balance already confirmed by the driver, tachograph, TMS, or another authoritative system, call `plan_from_confirmed_available_driving_time`. Never calculate statutory driving/rest entitlement yourself.\n\nFor current legal or regulatory questions, use authoritative official sources (for example European Commission, national transport authority, UNECE) and clearly separate those facts from the operational handover.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}