logistics-exception-management

Classify freight exceptions and guide compliant claims across all shipping modes.

Updated May 9, 2026
One-click install
npx skills add https://github.com/RambleRainbow/jd --skill logistics-exception-management-ramblerainbow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logistics-exception-management
Source: https://github.com/RambleRainbow/jd/tree/main/.claude/skills/logistics-exception-management
Command: npx skills add https://github.com/RambleRainbow/jd --skill logistics-exception-management-ramblerainbow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of inconsistent, non-compliant handling of freight exceptions (delays, damage, loss, carrier disputes) that lead to unrecovered financial losses, strained carrier relationships, and customer SLA breaches, by codifying 15+ years of expert logistics operational knowledge.

Core Features & Use Cases

  • Mode-Specific Exception Resolution: Provides tailored workflows for all freight modes (LTL, FTL, parcel, intermodal, ocean, air) covering exception classification, evidence collection, and liability determination.
  • Compliant Claims & Escalation Management: Guides users through statutory claims filing deadlines (e.g., 9-month Carmack Amendment window), carrier-specific requirements, and tiered escalation protocols for unresolved issues.
  • Use Case: For a temperature-controlled pharma shipment with a disputed reefer excursion, the skill guides you to demand continuous temperature logger data instead of accepting the carrier's single-point set-point reading to prove liability.

Quick Start

Use the logistics-exception-management skill to resolve the delayed PRO#67890 FTL shipment by classifying the exception type, gathering the required BOL and delivery receipt documentation, and escalating to the carrier account manager if no updated ETA is provided within 4 hours.

Frequently Asked Questions about logistics-exception-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I file a freight damage claim before the Carmack Amendment deadline expires?

Freight damage claims must be filed within the 9-month Carmack Amendment window. This skill provides compliant claims workflows, carrier-specific requirements, and tiered escalation protocols to ensure timely liability determination and financial recovery.

How do I resolve carrier disputes for shipment delays across different freight modes?

Resolving carrier disputes for shipment delays requires classifying the exception type and gathering BOL documentation. This skill offers tailored workflows for LTL, FTL, parcel, intermodal, ocean, and air freight to manage escalations and strained carrier relationships.

What is the process for handling concealed damage and refused deliveries in logistics operations?

Handling concealed damage and refused deliveries requires structured evidence collection and exception classification. This skill guides you through mode-specific workflows to determine carrier liability and prevent unrecovered financial losses.

How do I manage cross-border customs holds and carrier detention disputes?

Managing cross-border customs holds and carrier detention disputes requires tiered escalation protocols. This skill helps you navigate international freight conventions and carrier-specific procedures to resolve exceptions and maintain compliance.

How do I prove carrier liability for a temperature-controlled pharma shipment reefer excursion?

Proving carrier liability for a reefer excursion requires demanding continuous temperature logger data. This skill guides you to reject single-point set-point readings and gather proper evidence to support your freight claims.

Can I use a single workflow for freight exceptions across parcel, ocean, and air freight?

A single workflow cannot cover all freight modes due to varying regulations. This skill provides tailored workflows for parcel, ocean, air, LTL, FTL, and intermodal freight to ensure compliant exception classification and resolution.