CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/logistics-exception-management/SKILL.md

The canonical home for this skill is logistics-exception-management in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 strong, expert-knowledge skill: concise specialized content with concrete thresholds/deadlines, clearly sequenced workflows with escalation checkpoints, and exemplary progressive disclosure via well-signaled one-level references.

DimensionReasoningScore

Conciseness

The body is dense and substantive with specialized facts Claude would not reliably know (Carmack Amendment, COGSA $500/package, 49 USC § 14706, terminal-manager $2,500 authority), organized as tight bullets and tables; only minor framing prose (the Role/Context paragraph) could be trimmed.

4 / 5

Actionability

Concrete, executable guidance throughout — specific dollar thresholds, statutory deadlines, email-template subjects with variables, and trigger timelines — though full template text and complete decision matrices are deferred to reference files, leaving minor gaps inline.

4 / 5

Workflow Clarity

Sequences are clear and explicit (severity classification across three axes, numbered priority list, Level 1-5 escalation chain) with the Automatic Escalation Triggers table acting as checkpoints and error-recovery hints in the edge cases; minor validation gaps remain but the destructive/batch cap does not apply to this advisory skill.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview that summarizes edge cases, templates, and frameworks inline and points to three real, one-level-deep reference files (edge-cases.md, communication-templates.md, decision-frameworks.md) with clearly signaled links, making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

65%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.

The description clearly scopes a specialized logistics niche and uses reasonably natural trigger terms, but it lacks any explicit 'when to use' guidance and relies on the generic verb 'handling' rather than naming concrete actions.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations (e.g., 'Use when triaging shipment delays, filing carrier claims, or resolving OS&D disputes').

Replace the generic 'handling' with concrete actions the skill performs (triage, document, file claims, escalate, negotiate settlements).

Include natural synonyms users say (claims, OS&D, lost shipment, refused delivery) to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes" names the domain plus several concrete exception categories, but the only action verb ("handling") is generic — no concrete actions like file, triage, document, or escalate are stated.

3 / 5

Completeness

The "what" is clear (handling freight exceptions across delays/damages/losses/disputes) but there is no "when"/"Use when..." trigger clause at all, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present ("shipment delays", "damages", "losses", "carrier disputes", "freight exceptions"), giving good keyword coverage, though common variations like "claims", "OS&D", or "lost shipment" are missing.

4 / 5

Distinctiveness Conflict Risk

The freight-exception/claims niche is highly specialized with distinct triggers (carrier disputes, shipment delays, damages), making conflict with unrelated skills minimal.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.