Conciseness

The body is dense, telegraphic, and consistently delivers non-obvious domain facts Claude cannot be assumed to know (Carmack filing deadlines, COGSA per-package limits, terminal manager authority thresholds, settlement percentage floors). It is not 5 because of trimmable material: the persona paragraph in 'Role and Context', a duplicated 'When to Use' section at both the top and bottom of the file, and some flavor text; it is well above 3 because nearly every line carries operational specifics rather than padding.

Actionability

Guidance is concrete and numerically specific throughout — 'file concealed damage claim within 5 days', 'Trigger trace at 24 hours past ETA for FTL, 48 hours for LTL', 'Accept partial settlements above 70%', 'Reject settlements below 90%' — with tone-calibrated example phrasings and an explicit escalation trigger table. It falls short of 5 because no single worked end-to-end example ties the pieces together, and sections like 'Seasonal and Cyclical Patterns' are descriptive context rather than direct instruction.

Workflow Clarity

Decision logic is present (three-axis severity classification, priority sequencing, a five-level escalation chain with timeframes), but there is no unified end-to-end resolution workflow from exception intake through classification, action, documentation, and claim closure. Checkpoints are implicit — e.g. 'Escalate at 30-day mark if no resolution' exists in one threshold list but verification/confirmation steps are not systematically built into the sequences. This matches the anchor for steps listed with validation gaps and implicit checkpoints.

Progressive Disclosure

Structure is exemplary: SKILL.md holds core operational knowledge while full detail is externalized to three real, one-level-deep references (edge-cases.md, decision-frameworks.md, communication-templates.md — all verified present), each clearly signaled at point of need with its purpose ('Brief summaries here — see edge-cases.md for full analysis'; 'Full versions with variables in communication-templates.md'). No nested references, no orphaned links, and inline content is appropriately summarized versions of the externalized material.

Specificity

The description lists several concrete capability areas — 'handling freight exceptions, shipment delays, damages, losses, and carrier disputes' — matching the anchor for several specific actions with minor gaps. It falls short of 5 because coverage omits common actions like claims filing, tracing lost shipments, and shortage/overage handling, and 'codified expertise' is a partially abstract framing.

Completeness

The 'what' is clear (handling freight exceptions, delays, damages, losses, and carrier disputes), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3, and the 'Informed by logistics professionals' sentence adds provenance rather than trigger context.

Trigger Term Quality

Natural user phrases are present ('shipment delays', 'damages', 'losses', 'carrier disputes'), giving good keyword coverage. It is not 5 because key synonyms users would naturally say are missing — most notably 'claims', 'lost shipment/cargo', 'damaged freight', and 'tracking' — and not 3 because multiple natural phrases beyond generic jargon are covered.

Distinctiveness Conflict Risk

The description occupies a clear niche — freight exception and carrier dispute handling — with domain-specific terms that would rarely trigger a wrong skill. It is not 4 because the vocabulary (freight exceptions, carrier disputes) is specific enough that overlap with general logistics or supply-chain skills is minimal.