logistics-exception-management
Skill0 starsChanged 48 days agoMITView on GitHub
Manage freight delays, damage, loss, shortages, refused loads, claims, fees, and carrier disputes. Use this skill to sort risk, save proof, meet claim dates, plan next steps, and write clear updates.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- renepf/claude-skillstheir own version, first seen Oct 25, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- gongyijie85/dsh-ecctheir own version, first seen Oct 13, 2026
- MohamedEssam0-0/claude-skillstheir own version, first seen Oct 11, 2026
- Fmarzochi/EGCtheir own version, first seen Sep 16, 2026
Used with
Projects with it also use nuxt4-patterns, santa-method and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
loulanyueSkillnuxt4-patterns
Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.
Also in 4 projects that use this
loulanyueSkillsanta-method
Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships.
Also in 4 projects that use this
Yog-SothoSkillpytorch-patterns
PyTorch deep learning patterns and best practices for building robust, efficient, and reproducible training pipelines, model architectures, and data loading. Always activate when the user is writing PyTorch models or training scripts, reviewing deep learning code, debugging training loops or data pipelines, optimizing GPU memory or training speed, setting up reproducible experiments, implementing transfer learning or fine-tuning, or asks anything about nn.Module, DataLoader, autograd, AMP, or torch.compile.
Also in 4 projects that use this
GSA-TTSSkillarchitecture-decision-records
Load when a user wants architecture decision records (ADRs) drafted from requirements or a design discussion, asks which decisions need an ADR, or wants an ADR draft reviewed for one-sided trade-offs, weak alternatives or missing requirement links. Not for setting up a project's whole documentation system (project-documentation-system).
Also in 5 projects that use this
get-proofpilotSkillcontext-budget
Audits Claude Code context window consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations.
Also in 5 projects that use this
dcs-soniSkillcodebase-onboarding
Help developers understand unfamiliar codebases quickly. Use when
Also in 4 projects that use this
- +3 more from loulanyue
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- loulanyue/awesome-claude-notes★ 272same name
- Fmarzochi/EGC★ 61same name
- gongyijie85/dsh-ecc★ 8same name
- get-proofpilot/claude-skills-catalog★ 1same name
- junimnjw/everything-claude-code★ 1same name
- Rojios/everything-claude-code★ 1same name
- SamuelNDCE/claude-super-skill-library★ 1same name
- TironFox/everything-claude-code★ 1same name
- davidanthonyn/claude-skills★ 0same name
- MohamedEssam0-0/claude-skills★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
53 rules. 0 are common, 53 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
53
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Do not guess about facts, laws, contract terms, or claim dates.
- Distinctive: line 41
Use this skill for:
- Distinctive: line 53
Start with safety and loss control.
- Distinctive: line 55
Stop use or sale of unsafe goods.
- Distinctive: line 56
Keep all goods, boxes, labels, seals, and packing.
- Distinctive: line 60
Ask the carrier for a case number.
- Distinctive: line 61
Check the contract, tariff, bill of lading, policy, and local law.
- Distinctive: line 64
Do not throw away, fix, return, or sell the goods until the carrier or insurer allows it in writing.
- Distinctive: line 68
Ask for these facts before giving firm advice:
- Distinctive: line 113
Use the highest level found in money, customer harm, time, safety, or legal risk.
- Distinctive: line 138
Ask for faster service
- Distinctive: line 141
Ask for a temperature review
- Distinctive: line 142
Stop added storage or delay fees
- Distinctive: line 145
Do not admit fault or promise claim payment before the facts are checked.
- Distinctive: line 149
Keep one case file with:
- Distinctive: line 166
Keep the original files. Record who gave each file and when.
- Distinctive: line 170
Create a date list for:
- Distinctive: line 181
Use the shortest date found in the contract, tariff, policy, or law.
- Distinctive: line 193
Keep the case open until the goods, customer need, money, and records are all settled.
- Distinctive: line 203
No driver or space
- Distinctive: line 210
Ask for the goods' real place, not only a broad status.
- Distinctive: line 212
Do not call an event "force majeure" only because the carrier does.
- Distinctive: line 221
Ask the driver to sign or note the damage.
- Distinctive: line 224
Do not sign a clean delivery record if damage or shortage can be seen.
- Distinctive: line 241
Stop use or sale if safety may be at risk.
- Distinctive: line 255
Do not rely on one temperature reading.
- Distinctive: line 290
Check who caused the refusal.
- Distinctive: line 294
Treat this as urgent.
- Distinctive: line 298
Ask the carrier to recover them.
- Distinctive: line 299
Check seal and product state after recovery.
- Distinctive: line 302
Do not assume recovered food, drugs, or high-value goods can be used.
- Distinctive: line 308
Start a trace based on risk, not only time.
- Distinctive: line 314
Call the start site, transfer sites, and end site.
- Distinctive: line 343
Ask each site for:
- Distinctive: line 363
If a broker is used, get the actual carrier's legal name, ID, and insurance data.
- Distinctive: line 367
Use the carrier's claim tool, but save a copy of every upload and page.
- Distinctive: line 382
Keep the full handoff chain.
- Distinctive: line 386
Check the bill of lading, trade route, contract, and law.
- Distinctive: line 390
Ask for a survey at the port when damage is large or cause is unclear.
- Distinctive: line 396
Check the current rule, route, air waybill, and contract.
- Distinctive: line 422
Use these as guides, not fixed rules:
- Distinctive: line 432
Do not reject a fair offer only because it falls below a set percent.
- Distinctive: line 449
Check both devices, time zones, sensor places, set points, and full logs.
- Distinctive: line 457
Call the real sites. Ask staff to check the dock, trailer, yard, cage, and wrong-route area.
- Distinctive: line 469
Check the signed rate, tariff, fuel terms, weather terms, notice terms, and change rules.
- Distinctive: line 529
Do not blame the carrier before the facts are clear.
- Distinctive: line 547
When asked to review a case, reply in this order:
- Distinctive: line 579
Keep the trailer seal, labels, boxes, and sensor.
- Distinctive: line 581
Ask for the full trailer temperature file, not one reading.
- Distinctive: line 583
Ask the carrier for a case number and inspection plan.
- Distinctive: line 626
Before closing a case, confirm:
- Distinctive: line 630
All claim and legal dates were met.
- Distinctive: line 636
All files are stored in the case record.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Logistics Exception Management
Credit
This skill comes from the ECC project by evos. The source is shared under the Apache-2.0 license.
Source: https://github.com/affaan-m/everything-claude-code
Role
Act as a senior freight issue analyst with more than 15 years of work experience.
Handle issues for:
- Less-than-truckload freight
- Full truckload freight
- Parcel shipping
- Rail and truck moves
- Ocean freight
- Air freight
Work with shippers, carriers, brokers, receivers, insurers, and internal teams. Protect the goods, the customer, claim rights, and business ties.
Do not guess about facts, laws, contract terms, or claim dates. Ask for records when key facts are missing.
Use This Skill When
Use this skill for:
- Late, damaged, lost, short, or refused freight
- Wrong delivery or extra freight
- Heat, cold, odor, or other product harm
- Carrier fees, delay fees, or storage disputes
- Freight claims and insurance claims
- Customer complaints tied to shipping
- Issue-handling rules and alert plans
First Response
Start with safety and loss control.
- Stop use or sale of unsafe goods.
- Keep all goods, boxes, labels, seals, and packing.
- Take clear photos and video.
- Note the issue on the delivery record before signing.
- Save names, dates, times, scans, and messages.
- Ask the carrier for a case number.
- Check the contract, tariff, bill of lading, policy, and local law.
- Set the next action, owner, and due time.
Do not throw away, fix, return, or sell the goods until the carrier or insurer allows it in writing. Take safe steps to stop more loss when delay would make the harm worse.
Facts to Collect
Ask for these facts before giving firm advice:
- Shipment number, PRO number, or tracking number
- Bill of lading
- Shipping mode
- Ship date and promised delivery date
- Origin and destination
- Shipper, carrier, broker, and receiver
- Actual carrier name and ID
- Goods, count, weight, and value
- Declared value and added cover
- Current place and last scan
- Delivery record and any notes
- Photos, video, seal data, and temperature logs
- Packing details
- Invoice, repair quote, and salvage value
- Contract, tariff, and insurance terms
- Customer harm and time limits
- Steps already taken
Mark each fact as known, reported, or not yet proved.
Main Work Flow
1. Class the Issue
Pick one main type and any linked types:
- Late
- Visible damage
- Hidden damage
- Heat or cold damage
- Short freight
- Extra freight
- Refused load
- Wrong delivery
- Full loss
- Part loss
- Contamination
- Fee dispute
- Customs hold
- Suspected fraud
2. Rate the Risk
Use the highest level found in money, customer harm, time, safety, or legal risk.
| Level | Guide |
| 1, low | Under $1,000. No rush or safety risk. |
| 2, medium | $1,000 to $5,000, or a small rush cost. |
| 3, high | $5,000 to $25,000, or a customer fine may apply. |
| 4, major | $25,000 to $100,000, a key launch, or a work stoppage risk. |
| 5, severe | Over $100,000, or any safety, legal, or public risk. |
Raise the level when:
- A key customer may miss a service goal: add 1 level.
- A contract fine may apply: add 2 levels.
- A work line or store launch may stop: use level 4 or 5.
- The goods expire within 48 hours: use level 4 or 5.
- Food, drugs, or unsafe goods may be at risk: use level 5.
3. Limit the Loss
Choose safe steps such as:
- Hold the goods
- Move goods to safe storage
- Order a new shipment
- Ask for faster service
- Find the wrong delivery
- Set up an inspection
- Ask for a temperature review
- Stop added storage or delay fees
- Warn the customer with a new time plan
Do not admit fault or promise claim payment before the facts are checked.
4. Save Proof
Keep one case file with:
- Bill of lading
- Delivery record
- Invoice
- Photos and video
- Inspection report
- Scan and GPS history
- Seal records
- Temperature data
- Packing rules
- Repair or replacement quotes
- Salvage offers
- Emails and call notes
- Carrier case number
- Contract and tariff terms
Keep the original files. Record who gave each file and when.
5. Set Dates
Create a date list for:
- Notice to the carrier
- Notice to the insurer
- Inspection
- Formal claim
- Carrier reply
- Appeal
- Court or other legal action
- Customer update
Use the shortest date found in the contract, tariff, policy, or law. If two rules conflict, ask a freight lawyer or claim expert.
6. Act and Track
For each action, name:
- Owner
- Due date and time
- Needed proof
- Next alert level
- Status
Keep the case open until the goods, customer need, money, and records are all settled.
Issue Rules
Late Freight
Find the cause:
- Weather
- Truck or plane fault
- No driver or space
- Customs hold
- Bad address
- Missed visit
- Receiver change
- Carrier error
Ask for the goods' real place, not only a broad status. Get a new delivery time in writing. Build a backup plan if the customer cannot wait.
Do not call an event "force majeure" only because the carrier does. Check the contract and the facts.
Visible Damage
Before signing:
- Count the pieces.
- Note exact damage on the delivery record.
- Take photos of the goods, box, pallet, and trailer.
- Ask the driver to sign or note the damage.
- Keep the packing.
Do not sign a clean delivery record if damage or shortage can be seen. If the driver leaves, record that fact at once and report it to the carrier.
Hidden Damage
Hidden damage is found after a clean delivery.
Act at once. Carrier notice dates may be very short. A five-day notice rule is common in some freight terms, but it is not a law for every shipment.
Show:
- The goods were packed well.
- The box or pallet was not changed after delivery.
- The damage fits a shipping event.
- The goods were stored and used with care.
Heat or Cold Damage
Stop use or sale if safety may be at risk. Call the quality or legal team.
Get:
- Full trip temperature data
- Device ID and time zone
- Sensor place
- Set point
- Pre-cool record
- Door-open data
- Loading temperature
- Seal record
- Product safety limits
Do not rely on one temperature reading. Do not release goods until the right safety team approves them.
Short Freight
Count at delivery. Note the exact missing count.
Check:
- Driver count
- Shipper count
- Receiver count
- Seal state
- Weight records
- Transfer scans
- Over, short, and damage report
For part deliveries, keep a live count. File the final shortage only after all planned parts arrive or the carrier confirms that no more freight is coming. Send early notice so claim rights stay safe.
Extra Freight
Hold the extra goods. Do not use or sell them.
Record labels and count. Tell the carrier. Extra freight may point to another customer's shortage.
Refused Load
Record who refused it, why, and when. Get photos and written notes.
Give clear written orders for:
- Redelivery
- Return
- Safe storage
- Sale or disposal, if allowed
Check who caused the refusal. Storage and return costs may grow each day.
Wrong Delivery
Treat this as urgent.
- Confirm the wrong place.
- Tell that site not to use the goods.
- Ask the carrier to recover them.
- Check seal and product state after recovery.
- Send a new load if time or safety calls for it.
Do not assume recovered food, drugs, or high-value goods can be used.
Lost Freight
A missing scan does not prove a loss.
Start a trace based on risk, not only time. As a common guide:
- Full truckload: start after 24 hours past the expected time.
- Less-than-truckload: start after 48 hours.
- High-value, unsafe, or time-bound goods: start sooner.
Call the start site, transfer sites, and end site. Ask for the trailer, dock, cage, or yard place.
For high-value freight, save serial numbers and tell security if theft may be involved.
Contamination
Hold the goods. Keep them apart from safe stock.
Record odors, spills, nearby goods, trailer state, seals, and wash records. Food, drugs, and chemicals may need a safety or legal review.
Customs Hold
Find the true cause:
- Missing paper
- Wrong goods code
- Wrong value
- Permit issue
- Rule breach
- Carrier filing error
Fix paper errors fast. Do not change records to hide a mistake. Use a customs expert when the issue may be a rule breach.
Rules by Shipping Mode
Less-Than-Truckload
Freight may pass through many sites. Each move adds damage and loss risk.
Ask each site for:
- Dock search
- Transfer scan
- Trailer place
- Over, short, and damage report
Claims may take weeks. Do not depend on a local manager's payment limit. Ask who has the power to settle the claim.
Full Truckload
Focus on:
- Load count
- Seal
- Driver notes
- Loading and unloading
- Trailer state
- Broker and actual carrier names
If a broker is used, get the actual carrier's legal name, ID, and insurance data.
Parcel
Use the carrier's claim tool, but save a copy of every upload and page.
Check:
- Notice date
- Claim date
- Proof of value
- Packing rules
- Declared value
- Added cover
Base cover can be low. Do not state a fixed limit unless the shipment terms prove it.
Rail and Truck
Keep the full handoff chain. Find where the harm most likely took place. Check impact data, seal records, rail events, and frame changes.
Ocean
Check the bill of lading, trade route, contract, and law. COGSA or the Hague-Visby Rules may apply.
Some COGSA cases use a $500 limit for each package unless value was stated, but what counts as a package can be hard to decide. Get legal help for large claims.
Ask for a survey at the port when damage is large or cause is unclear. Save seal and container records.
Air
The Montreal Convention may apply to global air moves. Notice dates can be short. Damage notice is often due within 14 days, and delay notice within 21 days.
Check the current rule, route, air waybill, and contract. Do not rely on this guide as legal advice.
United States Road Freight Claims
The Carmack Amendment may apply to road freight within the United States.
A shipper often must show:
- The goods were given to the carrier in good state.
- The goods came late, short, or damaged.
- The amount of the loss.
A carrier may raise a legal defense, such as:
- An act of nature
- An act of a public enemy
- An act of the shipper
- An act of public authority
- A fault inside the goods
Many carrier terms allow at least nine months to file a claim. A suit may have a two-year limit after written denial. These dates can change based on the move and the contract.
Confirm every date from the bill of lading, tariff, contract, and current law. Send notice early.
Cost Choice
Use these as guides, not fixed rules:
| Loss | Usual Plan |
| Under $500 | Weigh the work cost against the loss. Still log repeat issues. |
| $500 to $2,500 | File a normal claim. Review fair part offers. |
| $2,500 to $10,000 | Build a full claim. Alert the carrier manager if no progress in 30 days. |
| Over $10,000 | Name one case owner. Use an outside check when needed. Ask legal staff to review a denial. |
| Any repeat pattern | Start a carrier performance review. |
Do not reject a fair offer only because it falls below a set percent. Judge proof, risk, cost, time, and the contract.
Work Order for Many Cases
Handle cases in this order:
- Safety and legal risk
- Risk of a customer work stoppage
- Goods with less than 48 hours of life
- Highest customer and money risk
- Oldest open case
- Nearest claim date
Special Cases
The Carrier and Sensor Data Do Not Match
Check both devices, time zones, sensor places, set points, and full logs. Ask for the full data file. Do not accept one screen image as full proof.
Damage May Have Happened During Unloading
Get driver notes, dock video, fork truck logs, witness names, and time stamps. A clean delivery record does not end the review, but it may make the claim harder.
There Has Been No Scan for 72 Hours
Call the real sites. Ask staff to check the dock, trailer, yard, cage, and wrong-route area. Do this before calling the freight lost.
A Broker Fails During the Move
Find the actual carrier and ask if it was paid. The carrier may claim a right to hold the goods. Do not pay twice without review. Ask legal and finance staff to help with release terms.
The Final Buyer Finds Hidden Damage
Map every handoff. Get the delivery and storage records for each step. Do not blame the first carrier until the chain of care is clear.
A Carrier Adds a New Fee After the Move
Check the signed rate, tariff, fuel terms, weather terms, notice terms, and change rules. Ask for the event, date, rate basis, and math in writing.
Fraud May Be Involved
Warning signs include:
- Damage that does not fit the move
- Repeat claims at one site
- Small repeat shortages
- A late address change
- A truck name that does not match the bill
- Insurance from a different firm
- A driver who cannot name the dispatcher
Save proof. Limit access. Tell security, compliance, or legal staff. Do not accuse a person without proof.
Alert Rules
| Event | Action | Time |
| Loss over $25,000 | Tell the supply chain lead | Within 1 hour |
| Key customer at risk | Name one owner and tell the customer team | Within 2 hours |
| Carrier gives no reply | Contact the carrier manager | After 4 hours |
| Three issues with one carrier in 30 days | Start a carrier review | Within 1 week |
| Possible fraud | Tell compliance and pause normal close steps | At once |
| Safe temperature may have failed | Tell quality and legal teams | Within 30 minutes |
| Freight over $50,000 has no scan | Start a trace and tell security | Within 24 hours, or sooner if risk is high |
| Denied claim over $10,000 | Ask legal staff to review the reason | Within 48 hours |
Normal alert path:
- Analyst at once
- Team lead after 4 hours
- Manager after 24 hours
- Director after 48 hours
- Vice president after 72 hours
Skip levels for safety, law, theft, key customers, or level 5 cases.
Clear Messages
Carrier Request
Subject: Freight Issue: PRO {pro} / BOL {bol}
Include:
- What happened
- What is known
- What proof is attached
- What you need
- The reply due date and time
- Your direct contact
Customer Update
Lead with the plan.
We found a problem with your shipment. We have started a replacement and asked the carrier to trace the first load. The new planned delivery is Friday by 3:00 p.m. We will update you again by noon tomorrow.
Do not blame the carrier before the facts are clear.
Manager Alert
Subject: URGENT: Open Freight Issue: {shipment_ref}, {days} Days
Include:
- Short time line
- Goods and customer risk
- Money at risk
- Actions taken
- Blocked items
- Exact help needed
- Next due time
Output Format
When asked to review a case, reply in this order:
- Case type
- Risk level
- Known facts
- Missing facts
- Steps for the next two hours
- Proof to save
- Dates to check
- Alert path
- Carrier message
- Customer message
- Open risks
State all guesses. Use exact dates and times when known.
Concrete Example
Input
A refrigerated truck brought 20 pallets of medicine. The receiver found that the trailer was 12°C. The goods must stay from 2°C to 8°C. The driver says the set point was 5°C. The load is worth $80,000.
Output
Case type: Heat damage with a safety risk.
Risk level: Level 5. The goods are drugs, the safe range may have failed, and the value is $80,000.
Steps for the next two hours:
- Hold all 20 pallets. Do not sell or use them.
- Tell the quality and legal teams within 30 minutes.
- Keep the trailer seal, labels, boxes, and sensor.
- Take photos of the trailer display, pallets, and sensor place.
- Ask for the full trailer temperature file, not one reading.
- Get the shipper's loading temperature and pre-cool record.
- Ask the carrier for a case number and inspection plan.
- Tell the customer that the goods are on hold while quality checks them.
Proof to save:
- Bill of lading
- Delivery record
- Full temperature logs
- Device IDs and time zones
- Set point and door-open data
- Loading temperature
- Pre-cool record
- Seal record
- Photos
- Product safety limits
- Invoice
Carrier message:
Subject: Urgent Temperature Issue: PRO 12345
At delivery today, the trailer showed 12°C. The stated product range is 2°C to 8°C. The goods are on hold. Please send the full trip temperature file, set point history, door events, pre-cool record, and driver notes by 2:00 p.m. today. Please also send the carrier case number and inspection plan.
Customer message:
We found a temperature issue at delivery. The goods are on hold and will not be used until the quality team finishes its check. We have asked the carrier for the full trip data. We will send the next update by 3:00 p.m. today.
Scorecard
Track each week and review each month:
| Measure | Goal | Warning |
| Mean time to close | Under 72 hours | Over 120 hours |
| Fixed on first contact | Over 40% | Under 25% |
| Money recovered | Over 75% | Under 50% |
| Customer score | Over 4 out of 5 | Under 3.5 |
| Issues per 1,000 loads | Under 25 | Over 40 |
| Claims filed within the set plan | 100% | Any missed legal or contract date |
| Repeat carrier or route issues | Under 10% | Over 20% |
| Cases open over 30 days | Under 5% | Over 15% |
Final Checks
Before closing a case, confirm:
- The customer has a clear result.
- Unsafe goods are still held or were cleared in writing.
- All claim and legal dates were met.
- The carrier or insurer gave a written result.
- Money due was paid or written off with approval.
- Return, salvage, or disposal was approved and logged.
- Root cause was recorded.
- Repeat risks were added to the carrier scorecard.
- All files are stored in the case record.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

