logistics-exception-management

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 behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is tdg-personal/logistics-exception-management

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally actionable, dense body of logistics expertise with clear sequenced workflows and decision checkpoints, weakened only by being a single large monolith with no progressive file structure. The skill is well-organized but could benefit from splitting reference material into bundle files.

Suggestions

Split the large reference blocks (Exception Taxonomy, Carrier Behaviour by Mode, Key Edge Cases, Communication Templates) into files under references/ and surface them as clearly signaled one-level-deep links from the SKILL.md overview to improve progressive_disclosure.

Add a short 'Quick start / triage' section at the top that points to the decision frameworks, so the overview reads as a router into the detailed material rather than a flat dump.

Confirm the cited external facts (Carmack 9-month window, COGSA $500/package, Montreal 14/21-day limits) in a dated references file so time-sensitive figures are versioned outside the main body.

Dimension	Reasoning	Score
Conciseness	The body is information-dense domain expertise (carrier behaviors, Carmack deadlines, dollar thresholds, fraud red flags) with no padding about concepts Claude already knows; connective prose is minimal and every section carries unique reference value.	3 / 3
Actionability	Guidance is concrete and copy-paste ready — exact value bands ('< $500… Absorb', '$2,500–$10,000… reject settlements below 80%'), statutory deadlines ('9 months', '14-day notice for damage'), named carriers, and templated communication lines — fully actionable for an instruction-only skill.	3 / 3
Workflow Clarity	A clear 5-step 'How It Works' sequence is reinforced by checkpoint-style decision frameworks (severity classification, eat-the-cost thresholds, automatic escalation triggers table with timelines) and a priority-sequencing list for concurrent exceptions.	3 / 3
Progressive Disclosure	The file is a single ~220-line monolith with no references/, scripts/, or assets/ bundle and no signaled one-level-deep references; sections are well-organized, but large reference-style blocks (Core Knowledge, Edge Cases, Communication Templates) are inline rather than split out.	2 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities and pairs them with an explicit, naturally-worded 'Use when' trigger covering the logistics exception domain. It is specific, complete, and low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'handling freight exceptions, shipment delays, damages, losses, and carrier disputes' plus 'escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks' — rather than vague abstractions.	3 / 3
Completeness	Explicitly answers both what it does (handle exceptions/delays/damages/losses/disputes; includes protocols, behaviors, claims, frameworks) and when to use it via an explicit 'Use when…' trigger, so it clears the 3-anchor and is not the level-2 'when only implied'.	3 / 3
Trigger Term Quality	The 'Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes' clause covers natural terms a user would actually say, with good variation across the domain.	3 / 3
Distinctiveness Conflict Risk	The freight/logistics exception niche with domain-specific triggers (freight claims, carrier disputes, delivery issues) is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: affaan-m/ECC
Path: skills/logistics-exception-management/SKILL.md
Commit: 754b8dd

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.