fix: address CodeRabbit review feedback

- Rename SKILL.md to <skill-name>.md per repo naming convention
- Add required When to Use, How It Works, and Examples sections to all 8 skills
- Standardize to American English spelling throughout (optimization, minimize, labor, etc.)
- Fix "different than" to "different from" in returns-reverse-logistics

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
nocodemf
2026-02-25 18:07:07 +03:00
parent 6e48f43e4e
commit fb94c645f7
8 changed files with 234 additions and 49 deletions

View File

@@ -4,7 +4,7 @@ description: >
Codified expertise for handling freight exceptions, shipment delays,
damages, losses, and carrier disputes. Informed by logistics professionals
with 15+ years operational experience. Includes escalation protocols,
carrier-specific behaviours, claims procedures, and judgment frameworks.
carrier-specific behaviors, claims procedures, and judgment frameworks.
Use when handling shipping exceptions, freight claims, delivery issues,
or carrier disputes.
license: Apache-2.0
@@ -23,6 +23,28 @@ metadata:
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
1. Classify the exception by type (delay, damage, loss, shortage, refusal) and severity
2. Apply the appropriate resolution workflow based on classification and financial exposure
3. Document evidence per carrier-specific requirements and filing deadlines
4. Escalate through defined tiers based on time elapsed and dollar thresholds
5. 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