Menu

Individual skill

logistics-incident-report

0upvotes

Write up a supply chain disruption — port delay, carrier failure, customs hold, or in-transit damage — as a decision-ready incident report. Use when asked to document a shipment delay, write up a logistics failure, report a customs hold, quantify a supply disruption, or draft the customer notice for a late delivery. Produces an impact-quantified incident report with containment actions, root cause, prevention items, and a customer-communication draft.

skills/logistics-incident-report/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,542
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Logistics Incident Report Skill

When freight goes wrong, the write-up has two jobs at once: give operations the facts to contain the damage today, and give the network the lesson so it doesn't repeat. This skill quantifies who and what is actually at risk (orders, customers, dollars — not just "a container is late"), separates containment from prevention, digs the root cause past "the carrier failed", and drafts the customer message so commercial teams aren't improvising under pressure.

## What This Skill Produces

- An incident summary with severity classification
- Impact quantification: orders, customers, revenue at risk, and production/stockout exposure
- A containment log: actions taken and still open, with owners and ETAs
- Root cause and contributing factors — past the proximate carrier/port event
- Prevention actions distinguishing this-lane fixes from network lessons
- A ready-to-send customer-communication draft

## Required Inputs
Back to top