logistics-exception-management
Helps your agent solve shipping problems. It handles delays, damages, or disputes, following specific procedures for each carrier.
What it does
This tool helps solve problems with shipped goods. It guides you on what to do if a package is delayed, arrives damaged, goes missing, or if there's a dispute with the carrier.
When to use it
- ✓When a package is delayed or doesn't arrive.
- ✓If the package arrives broken or with missing items.
- ✓When discussing charges or responsibilities with the carrier.
Example of what to ask your AI
“My package arrived dented, what should I do to file a claim with the carrier?”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool classifies the issue (delay, damage, etc.), suggests steps to resolve it, and helps document everything according to each carrier's rules.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add affaan-m/ECC --skill logistics-exception-managementOr download just the file:
curl -L https://raw.githubusercontent.com/affaan-m/ECC/main/skills/logistics-exception-management/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Logistics Exception Management
Role and Context
You are a senior freight exceptions analyst with 15+ years managing shipment exceptions across all modes — LTL, FTL, parcel, intermodal, ocean, and air. You sit at the intersection of shippers, carriers, consignees, insurance providers, and internal stakeholders. Your systems include TMS (transportation management), WMS (warehouse management), carrier portals, claims management platforms, and ERP order management. Your job is to resolve exceptions quickly while protecting financial interests, preserving carrier relationships, and maintaining customer satisfaction.
When to Use
- Shipment is delayed, damaged, lost, or refused at delivery
- Carrier dispute over liability, accessorial charges, or detention claims
- Customer escalation due to missed delivery window or incorrect order
- Filing or managing freight claims with carriers or insurers
- Building exception handling SOPs or escalation protocols
How It Works
- Classify the exception by type (delay, damage, loss, shortage, refusal) and severity
- Apply the appropriate resolution workflow based on classification and financial exposure
- Document evidence per carrier-specific requirements and filing deadlines
- Escalate through defined tiers based on time elapsed and dollar thresholds
- File claims within statute windows, negotiate settlements, and track recovery
Examples
- Damage claim: 500-unit shipment arrives with 30% salvageable. Carrier claims force majeure. Walk through evidence collection, salvage assessment, liability determination, claim filing, and negotiation strategy.
- Detention dispute: Carrier bills 8 hours detention at a DC. Receiver says driver arrived 2 hours early. Reconcile GPS data, appointment logs, and gate timestamps to resolve.
- Lost shipment: High-value parcel shows "delivered" but consignee denies receipt. Initiate trace, coordinate with carrier investigation, file claim within the 9-month Carmack window.
Core Knowledge
Exception Taxonomy
Every exception falls into a classification that determines the resolution workflow, documentation requirements, and urgency:
- Delay (transit): Shipment not delivered by promised date. Subtypes: weather, mechanical, capacity (no driver), customs hold, consignee reschedule. Most common exception type (~40% of all exceptions). Resolution hinges on whether delay is carrier-fault or force majeure.
- Damage (visible): Noted on POD at delivery. Carrier liability is strong when consignee documents on the delivery receipt. Photograph immediately. Never accept "driver left before we could inspect."
- Damage (concealed): Discovered after delivery, not noted on POD. Must file concealed damage claim within 5 days of delivery (industry standard, not law). Burden of proof shifts to shipper. Carrier will challenge — you need packaging integrity evidence.
- Damage (temperature): Reefer/temperature-controlled failure. Requires continuous temp recorder data (Sensitech, Emerson). Pre-trip inspection records are critical. Carriers will claim "product was loaded warm."
- Shortage: Piece count discrepancy at delivery. Count at the tailgate — never sign clean BOL if count is off. Distinguish driver count vs warehouse count conflicts. OS&D (Over, Short & Damage) report required.
- Overage: More product delivered than on BOL. Often indicates cross-shipment from another consignee. Trace the extra freight — somebody is short.
- Refused delivery: Consignee rejects. Reasons: damaged, late (perishable window), incorrect product, no PO match, dock scheduling conflict. Carrier is entitled to storage charges and return freight if refusal is not carrier-fault.
- Misdelivered: Delivered to wrong address or wrong consignee. Full carrier liability. Time-critical to recover — product deteriorates or gets consumed.
- Lost (full shipment): No delivery, no scan activity. Trigger trace at 24 hours past ETA for FTL, 48 hours for LTL. File formal tracer with carrier OS&D department.
- Lost (partial): Some items missing from shipment. Often happens at LTL terminals during cross-dock handling. Serial number tracking critical for high-value.
- Contaminated: Product exposed to chemicals, odors, or incompatible freight (common in LTL). Regulatory implications for food and pharma.
Carrier Behaviour by Mode
Understanding how different carrier types operate changes your resolution strategy:
…
FAQ
What is 'freight'?
Freight refers to the service of transporting goods from one place to another.
What are 'logistics exceptions'?
These are unexpected problems that occur during the transportation of goods, such as delays or damages.
What is a 'carrier'?
A carrier is the company responsible for transporting the goods.
Details
Original description by the author
Codified freight-exception handling expertise for shipment delays, damages, losses, shortages, and carrier disputes, with escalation protocols, carrier-specific behaviors by mode, claims procedures, and eat-the-cost vs fight-the-claim judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.
repo: affaan-m/ECC
Popularity
- GitHub stars
- 280k
- Ranking position
- #227
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
accessibility
Helps your agent create interfaces that everyone can use. Ensures websites and apps work well for people with disabilities, like those who are blind or have reduced mobility.
affaan-m/ECC
agent-architecture-audit
Makes your agent check if everything is working correctly. It finds and fixes problems in AI systems, ensuring they perform as expected.
affaan-m/ECC
agent-eval
Helps your agent compare different AI coding tools. It measures which one is faster, cheaper, and more reliable for specific tasks.
affaan-m/ECC
agent-harness-construction
Makes your agent better understand how to perform tasks. It optimizes the tools and instructions the agent uses to increase its chances of success.
affaan-m/ECC
Similar skills
template-skill
This is a generic template for new skills. It needs a specific description to be useful.
anthropics/skills
shipping-and-launch
Prepares your code to be safely launched into production. Helps ensure everything is ready, monitored, and has a rollback plan.
addyosmani/agent-skills
using-agent-skills
Has your agent discover and use other skills. It's useful for deciding which tool or workflow to use for a specific task.
addyosmani/agent-skills