logistics-exception-management

Codify freight exception workflows for claims, escalations, and carrier disputes.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/vrcms/everything-qwen-code --skill logistics-exception-management-vrcms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logistics-exception-management
Source: https://github.com/vrcms/everything-qwen-code/tree/main/.qwen/skills/logistics-exception-management
Command: npx skills add https://github.com/vrcms/everything-qwen-code --skill logistics-exception-management-vrcms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the operational complexity of managing freight exceptions, such as shipment delays, damages, losses, and carrier disputes, by providing a structured, expert-informed framework for resolution.

Core Features & Use Cases

  • Exception Taxonomy: Classifies issues into specific categories like transit delays, concealed damage, or temperature excursions to determine the correct resolution path.
  • Escalation Protocols: Provides clear, time-bound guidelines for escalating issues based on financial impact, customer tier, and severity.
  • Use Case: When a high-value shipment arrives with concealed damage, use this skill to guide the documentation process, determine liability under the Carmack Amendment, and draft a formal claim to the carrier.

Quick Start

Use the logistics-exception-management skill to analyze a damaged shipment report and generate a formal claim strategy based on the carrier mode and financial impact.

Frequently Asked Questions about logistics-exception-management

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

FAQPage Schema
How do I manage freight exceptions and carrier disputes for damaged shipments?

To manage freight exceptions, classify the issue using an exception taxonomy to determine the correct resolution path, document the damage, and file a formal claim against the carrier based on liability frameworks like the Carmack Amendment.

What is the process for filing a freight claim under the Carmack Amendment?

Filing a freight claim under the Carmack Amendment requires codifying expert logistics knowledge to guide the documentation process, determining carrier liability for transit damages, and generating a formal claim strategy based on transport mode and financial impact.

How do I escalate a shipment delay based on financial impact and customer tier?

Escalating a shipment delay involves applying time-bound escalation protocols that trigger based on the financial impact, customer tier, and severity of the transit delay to ensure timely logistics exception resolution.

How do I classify concealed damage and temperature excursions in supply chain logistics?

Classifying concealed damage and temperature excursions in supply chain logistics requires using an exception taxonomy to categorize the specific issue, which determines the correct operational workflow and resolution path for the freight claim.

Can I use this approach for carrier performance analysis across all transport modes?

Yes, you can use this approach for carrier performance analysis across all transport modes, as it supports operational workflows for claims filing and escalation management while codifying expert logistics knowledge for carrier management.

When should I escalate a carrier liability dispute versus filing a standard claim?

You should escalate a carrier liability dispute instead of filing a standard claim when the financial impact and customer tier severity meet specific time-bound escalation protocol thresholds defined within the logistics exception management framework.