Logistics Exception Management
- 1.4k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of logistics-exception-management by affaan-m - installs and ranking accrue to the original listing.
logistics-exception-management is an ECC agent skill that codifies senior freight-analyst workflows for classifying shipment exceptions, filing claims, and resolving carrier disputes for developers building or operating
About
logistics-exception-management is an Apache-2.0 ECC agent skill (version 1.0.0) that encodes 15+ years of freight operations expertise into structured exception-handling playbooks. The skill walks an agent through a five-step workflow: classify exceptions by type and severity, apply mode-specific resolution paths, document carrier evidence, escalate by dollar and time thresholds, and file claims inside statutory windows such as the 9-month Carmack Amendment deadline. Coverage spans six transport modes—LTL, FTL, parcel, intermodal, ocean, and air—with decision frameworks for eat-the-cost versus fight-the-claim calls, eight automatic escalation triggers, and eight weekly KPI targets. Developers reach for logistics-exception-management when building logistics SOP generators, claims automation, carrier-dispute assistants, or AI support for supply-chain operations teams integrating TMS, WMS, and ERP order systems.
- 15+ years of logistics professional expertise distilled into judgment frameworks
- Handles delays, damages, losses, refused deliveries, and carrier liability disputes
- Includes escalation protocols and carrier-specific behaviors
- Protects financial interests while preserving carrier relationships and customer satisfaction
- Works across LTL, FTL, parcel, intermodal, ocean, and air freight modes
Logistics Exception Management by the numbers
- 1,364 all-time installs (skills.sh)
- +83 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill logistics-exception-managementAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you resolve freight damage claims and carrier disputes?
Get expert, codified guidance when handling real-world shipping exceptions, freight claims, carrier disputes, and delivery issues.
Who is it for?
Developers building logistics SaaS, TMS integrations, or AI agents that must reason about real freight exceptions, claims deadlines, and carrier escalation protocols.
Skip if: Developers who only need generic REST API tutorials or have no freight, shipping, or supply-chain domain requirements in their product.
When should I use this skill?
A shipment is delayed, damaged, lost, or refused; a carrier disputes liability or detention; or the team needs logistics exception SOPs and claims guidance.
What you get
Exception classification, resolution workflow steps, Carmack Amendment claim packets, carrier escalation emails, SOP drafts, and severity-tier decisions.
- Exception classification and severity assessment
- Carrier inquiry and escalation email drafts
- Claims documentation checklists and SOP outlines
By the numbers
- Skill version 1.0.0 under Apache-2.0 license
- Covers 6 transport modes: LTL, FTL, parcel, intermodal, ocean, and air
- Documents 8 automatic escalation triggers and 8 weekly performance KPIs
Files
logistics-exception-management - 日本語翻訳進行中
このファイルの翻訳は実装中です。英語版は元のスキルファイルを参照してください。
詳細は：D:/tmp/everything-claude-code/skills/logistics-exception-management/SKILL.md
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.591k39.6k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.494kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.493kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.492kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.492k
Twitter AutomationAutomate X/Twitter posts, scheduling, and engagement via X API integration441k669How it compares
Choose logistics-exception-management over generic customer-support skills when the task requires freight-specific claims law, mode-by-mode carrier behavior, and structured eat-cost versus fight-claim decision logic.
FAQ
What transport modes does logistics-exception-management cover?
logistics-exception-management covers six transport modes: LTL, FTL, parcel, intermodal, ocean, and air. Each mode section documents carrier behavior, claims portals, liability rules, and typical resolution timelines so agents pick the right workflow.
What is the US freight claim filing deadline?
logistics-exception-management cites the Carmack Amendment 9-month filing window from delivery date under 49 USC § 14706 for US domestic surface freight. Missing that deadline time-bars a claim regardless of merit.
When should developers invoke logistics-exception-management?
Developers should invoke logistics-exception-management when shipments are delayed, damaged, lost, or refused; when carriers dispute liability or detention; or when building exception SOPs, claims automation, or TMS-linked escalation workflows.