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

81%

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

75%Weight 40%Scale 1-5

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

A high-quality, domain-expert skill body that adds genuine logistics knowledge Claude lacks, with concrete thresholds, escalation tables, and clear structure. It is an instruction/judgment skill rather than a code skill, and guidance is actionable; minor tightening and optional external playbook files would push it higher.

Suggestions

Tighten the 'Role and Context' paragraph and a few expanded edge cases to reduce token overhead without losing the domain expertise.

Consider extracting the Key Edge Cases and full Communication Templates into referenced bundle files (e.g., references/edge-cases.md) to improve progressive disclosure and keep the main SKILL.md leaner.

Add explicit validate->fix->retry checkpoint phrasing in the claims and trace workflows to strengthen workflow clarity for destructive/time-critical operations.

Dimension	Reasoning	Score
Conciseness	Mostly efficient domain-specific knowledge (taxonomy, carrier behaviors, Carmack deadlines) that Claude would not already know; a few sections like the prose role paragraph and some expanded edge-case explanations could be tightened.	4 / 5
Actionability	Concrete actionable guidance throughout — dollar thresholds, time windows, specific actions ('call the origin and destination terminals directly', 'demand continuous data logger download') — with minor gaps where guidance stays at a directive level.	4 / 5
Workflow Clarity	Clear sequenced 'How It Works' steps plus escalation chains and triggers with explicit timelines; validation checkpoints are embedded (e.g., 'never sign clean BOL if count is off', 'Before triggering a loss protocol, call terminals') though presented as guidance rather than formal validate->fix->retry loops.	4 / 5
Progressive Disclosure	Well-organized into clear sections with explicit signaling that edge cases and templates are 'brief summaries' to be expanded into project-specific playbooks; no bundle files exist so structure relies on in-body organization, which is strong with minor room to externalize detailed playbooks.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

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, well-targeted description that clearly states capabilities and explicit trigger conditions in third person. Minor keyword breadth could be added, but it is clear and distinct.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks') with minor gaps; not a full enumeration of all sub-actions but well beyond 1-2.	4 / 5
Completeness	Explicitly answers both what it does (handle freight exceptions, delays, damages, losses, disputes) and when with a concrete 'Use when...' clause listing trigger scenarios.	5 / 5
Trigger Term Quality	Good natural trigger coverage ('shipping exceptions, freight claims, delivery issues, or carrier disputes'); a few common synonyms (e.g., 'damage', 'shortage', 'OS&D') are missing.	4 / 5
Distinctiveness Conflict Risk	Clear narrow niche (freight/logistics exception management) with distinct triggers; minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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	14 / 16 Passed

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

Reviewed: 3 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.