Conciseness

Mostly efficient: nearly every line carries domain-specific data Claude would not reliably know (dollar thresholds, the 9-month Carmack window, 30/120-day carrier response deadlines, settlement floors). Not 5 because of the role-play preamble ('You are a senior freight exceptions analyst with 15+ years...'), per-section intro sentences ('Understanding how different carrier types operate changes your resolution strategy'), and an Examples section that overlaps with Key Edge Cases; not 3 because padding is minor relative to the dense operational content.

Actionability

Fully actionable instruction-only guidance: exact dollar tiers with prescribed actions ('Reject settlements below 80%'), precise deadlines (5-day concealed damage, 14/21-day Montreal Convention notice), an escalation table with hour-level timelines, copy-paste-able subject-line templates ('ESCALATION: Unresolved Exception — {shipment_ref} — {days} Days'), and quoted example phrasings. Specific examples cover the common cases (damage claim, detention dispute, lost shipment).

Workflow Clarity

The 5-step How It Works sequence (classify → apply workflow → document → escalate → file/track) is clear, and checkpoints exist via the three-axis severity assessment, the automatic escalation trigger table, and time-based re-checks ('Escalate at 30-day mark if no resolution'). Not 5 because validation is implicit — there is no explicit verify step such as confirming documentation completeness against carrier requirements before filing a claim; not 3 because sequencing and most checkpoints are present and unambiguous.

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and all ~220 lines live inline in SKILL.md with good headers but content that should be separate is inline — Carrier Behaviour by Mode, Seasonal Patterns, Fraud Red Flags, and the edge-case playbooks are exactly the material that belongs in one-level-deep reference files. Not 2 because the section structure is clear and navigable, not monolithic; not 4 because the body far exceeds overview size and nothing is split out, even though the skill itself hints at it ('Brief summaries are included here so you can expand them into project-specific playbooks').

Specificity

Lists several concrete capability areas — 'escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks' plus 'handling freight exceptions, shipment delays, damages, losses, and carrier disputes' — with minor coverage gaps. Not 5 because the credential sentence 'Informed by logistics professionals with 15+ years operational experience' is marketing fluff that adds no capability information; not 3 because multiple specific capabilities are named beyond the domain itself.

Completeness

Explicitly answers both questions: what ('Codified expertise for handling freight exceptions... Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks') and when ('Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes'). The when-clause uses concrete trigger phrases, matching the anchor-5 example structure; the credential sentence keeps it from being any cleaner but both parts are fully explicit.

Trigger Term Quality

Comprehensive natural-term coverage with synonyms across the domain: 'shipping exceptions, freight claims, delivery issues, or carrier disputes' plus 'shipment delays, damages, losses'. These are exactly the phrases a logistics user would say; no obvious natural variants are missing (score 4 would require identifiable missing terms, and none stand out).

Distinctiveness Conflict Risk

Clear niche — freight exception and claims management — with distinct triggers like 'freight claims' and 'carrier disputes' that no common adjacent skill would own. 'Delivery issues' is slightly generic giving minor overlap risk with parcel-tracking skills, but in context of the freight-claims framing the conflict risk stays minimal, so 5 fits better than 4.