Logistics Exception Management
affaan-m/ECC
Codified freight-exception handling expertise for shipment delays, damages, losses, shortages, and carrier disputes, with escalation protocols, carrier-specific behaviors by mode, claims procedures…
Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes.
$ npx skills add sickn33/agentic-awesome-skills --skill logistics-exception-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills logistics-exception-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/logistics-exception-management .claude/skills/logistics-exception-management && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "logistics-exception-management" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/logistics-exception-management into .claude/skills/logistics-exception-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logistics-exception-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/logistics-exception-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill logistics-exception-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills logistics-exception-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/logistics-exception-management .agents/skills/logistics-exception-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "logistics-exception-management" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/logistics-exception-management into .agents/skills/logistics-exception-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logistics-exception-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill logistics-exception-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills logistics-exception-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/logistics-exception-management .cursor/skills/logistics-exception-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "logistics-exception-management" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/logistics-exception-management into .cursor/skills/logistics-exception-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logistics-exception-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/logistics-exception-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill logistics-exception-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills logistics-exception-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/logistics-exception-management .gemini/skills/logistics-exception-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "logistics-exception-management" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/logistics-exception-management into .gemini/skills/logistics-exception-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logistics-exception-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills logistics-exception-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill logistics-exception-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/logistics-exception-management .github/skills/logistics-exception-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "logistics-exception-management" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/logistics-exception-management into .github/skills/logistics-exception-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logistics-exception-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill logistics-exception-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills logistics-exception-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/logistics-exception-management .opencode/skills/logistics-exception-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "logistics-exception-management" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/logistics-exception-management into .opencode/skills/logistics-exception-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logistics-exception-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
logistics-exception-managementCodified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes.
Logistics Exception Management is an agent skill from sickn33/agentic-awesome-skills. Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience.
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/communication-templates.md`, `references/decision-frameworks.md` and `references/edge-cases.md`).
The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 680176d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Logistics Exception Management loads about 4.3k tokens when it runs, and up to ~65k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 2,077 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from sickn33/agentic-awesome-skills at commit 680176d, republished under its MIT licence (© sickn33). 2,077 words, ~4,260 tokens.
.claude/skills/logistics-exception-management/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Use this skill when dealing with deviations from planned logistics operations, such as transit delays, damaged shipments, lost cargo, or when initiating and managing claims and disputes with freight carriers.
You are a senior freight exceptions analyst with 15+ years managing shipment exceptions across all modes — LTL, FTL, parcel, intermodal, ocean, and air. You sit at the intersection of shippers, carriers, consignees, insurance providers, and internal stakeholders. Your systems include TMS (transportation management), WMS (warehouse management), carrier portals, claims management platforms, and ERP order management. Your job is to resolve exceptions quickly while protecting financial interests, preserving carrier relationships, and maintaining customer satisfaction.
Every exception falls into a classification that determines the resolution workflow, documentation requirements, and urgency:
Understanding how different carrier types operate changes your resolution strategy:
Assess every exception on three axes and take the highest severity:
Financial Impact:
Customer Impact:
Time Sensitivity:
This is the most common judgment call. Thresholds:
When multiple exceptions are active simultaneously (common during peak season or weather events), prioritize:
These are situations where the obvious approach is wrong. Brief summaries here — see edge-cases.md for full analysis.
Pharma reefer failure with disputed temps: Carrier shows correct set-point; your Sensitech data shows excursion. The dispute is about sensor placement and pre-cooling. Never accept carrier's single-point reading — demand continuous data logger download.
Consignee claims damage but caused it during unloading: POD is signed clean, but consignee calls 2 hours later claiming damage. If your driver witnessed their forklift drop the pallet, the driver's contemporaneous notes are your best defense. Without that, concealed damage claim against you is likely.
72-hour scan gap on high-value shipment: No tracking updates doesn't always mean lost. LTL scan gaps happen at busy terminals. Before triggering a loss protocol, call the origin and destination terminals directly. Ask for physical trailer/bay location.
Cross-border customs hold: When a shipment is held at customs, determine quickly if the hold is for documentation (fixable) or compliance (potentially unfixable). Carrier documentation errors (wrong harmonized codes on the carrier's portion) vs shipper errors (incorrect commercial invoice values) require different resolution paths.
Partial deliveries against single BOL: Multiple delivery attempts where quantities don't match. Maintain a running tally. Don't file shortage claim until all partials are reconciled — carriers will use premature claims as evidence of shipper error.
Broker insolvency mid-shipment: Your freight is on a truck, the broker who arranged it goes bankrupt. The actual carrier has a lien right. Determine quickly: is the carrier paid? If not, negotiate directly with the carrier for release.
Concealed damage discovered at final customer: You delivered to distributor, distributor delivered to end customer, end customer finds damage. The chain-of-custody documentation determines who bears the loss.
Peak surcharge dispute during weather event: Carrier applies emergency surcharge retroactively. Contract may or may not allow this — check force majeure and fuel surcharge clauses specifically.
Match communication tone to situation severity and relationship:
Brief templates below. Full versions with variables in communication-templates.md.
Initial carrier inquiry: Subject: Exception Notice — PRO# {pro} / BOL# {bol}. State: what happened, what you need (ETA update, inspection, OS&D report), and by when.
Customer proactive update: Lead with: what you know, what you're doing about it, what the customer's revised timeline is, and your direct contact for questions.
Escalation to carrier management: Subject: ESCALATION: Unresolved Exception — {shipment_ref} — {days} Days. Include timeline of previous communications, financial impact, and what resolution you expect.
| Trigger | Action | Timeline |
|---|---|---|
| Exception value > $25,000 | Notify VP Supply Chain immediately | Within 1 hour |
| Enterprise customer affected | Assign dedicated handler, notify account team | Within 2 hours |
| Carrier non-response | Escalate to carrier account manager | After 4 hours |
| Repeated carrier (3+ in 30 days) | Carrier performance review with procurement | Within 1 week |
| Potential fraud indicators | Notify compliance and halt standard processing | Immediately |
| Temperature excursion on regulated product | Notify quality/regulatory team | Within 30 minutes |
| No scan update on high-value (> $50K) | Initiate trace protocol and notify security | After 24 hours |
| Claims denied > $10,000 | Legal review of denial basis | Within 48 hours |
Level 1 (Analyst) → Level 2 (Team Lead, 4 hours) → Level 3 (Manager, 24 hours) → Level 4 (Director, 48 hours) → Level 5 (VP, 72+ hours or any Level 5 severity)
Track these metrics weekly and trend monthly:
| Metric | Target | Red Flag |
|---|---|---|
| Mean resolution time | < 72 hours | > 120 hours |
| First-contact resolution rate | > 40% | < 25% |
| Financial recovery rate (claims) | > 75% | < 50% |
| Customer satisfaction (post-exception) | > 4.0/5.0 | < 3.5/5.0 |
| Exception rate (per 1,000 shipments) | < 25 | > 40 |
| Claims filing timeliness | 100% within 30 days | Any > 60 days |
| Repeat exceptions (same carrier/lane) | < 10% | > 20% |
| Aged exceptions (> 30 days open) | < 5% of total | > 15% |
Use this skill when you need to triage and resolve logistics exceptions or design exception-handling playbooks:
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references) in skills/logistics-exception-management of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit 680176d
We found 11 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Logistics Exception Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Logistics Exception Management this skillsickn33/agentic-awesome-skills | 47k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Logistics Exception Managementaffaan-m/ECC | 276k | 4 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Logistics Exception Managementaffaan-m/ECC | 276k | 2 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Logistics ExceptionCALLE-AI/awesome-phone-call-agents | 107 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Returns Reverse Logisticsaffaan-m/ECC | 276k | 2 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Returns Reverse Logisticsaffaan-m/ECC | 276k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 |
affaan-m/ECC
Codified freight-exception handling expertise for shipment delays, damages, losses, shortages, and carrier disputes, with escalation protocols, carrier-specific behaviors by mode, claims procedures…
affaan-m/ECC
针对货运异常、货物延误、损坏、丢失和承运商纠纷的编码化专业知识,由拥有15年以上运营经验的物流专业人士提供。包括升级协议、承运商特定行为、索赔程序和判断框架。在处理运输异常、货运索赔、交付问题或承运商纠纷时使用。
CALLE-AI/awesome-phone-call-agents
Resolve a delayed-shipment dock exception by phone with CALL-E.
affaan-m/ECC
用于退货授权、接收与检验、处置决策、退款处理、欺诈检测以及保修索赔管理的标准化专业知识。基于拥有15年以上经验的退货运营经理的见解。包括分级框架、处置经济学、欺诈模式识别和供应商回收流程。适用于处理产品退货、逆向物流、退款决策、退货欺诈检测或保修索赔时使用。
affaan-m/ECC
返品承認、受取・検品、処分決定、返金処理、不正検出、保証クレーム管理のための標準化された専門知識。15年以上の経験を持つ返品オペレーションマネージャーの知見に基づく。段階的フレームワーク、処分経済性、不正パターン認識、ベンダー回収プロセスを含む。製品返品、逆物流、返金決定、返品不正検出、保証クレームを扱う場合に使用。
tsedio/tsed
Handle errors and shape responses in a Ts.ED v8 application with @tsed/exceptions, exception filters from @tsed/platform-exceptions and response filters from @tsed/platform-response-filter.
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Logistics Exception Management is an agent skill from sickn33/agentic-awesome-skills. Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes.
Run `npx skills add sickn33/agentic-awesome-skills --skill logistics-exception-management -a claude-code`. Or copy the skill folder (skills/logistics-exception-management in sickn33/agentic-awesome-skills) into .claude/skills/logistics-exception-management in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sickn33/agentic-awesome-skills --skill logistics-exception-management -a codex`. Or copy the skill folder (skills/logistics-exception-management in sickn33/agentic-awesome-skills) into .agents/skills/logistics-exception-management in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill logistics-exception-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/logistics-exception-management, .gemini/skills/logistics-exception-management, .github/skills/logistics-exception-management and .opencode/skills/logistics-exception-management in your project.
SKILL.md names no scripts, command-line tools or credentials: Logistics Exception Management is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Logistics Exception Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 60k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Logistics Exception Management: Logistics Exception Management (affaan-m/ECC, 276k stars), Logistics Exception Management (affaan-m/ECC, 276k stars), Logistics Exception (CALLE-AI/awesome-phone-call-agents, 107 stars) and Returns Reverse Logistics (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,379 GitHub stars. The repository holds 1,493 skills in this directory. The repository was last updated on October 9, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.