LI
Logistics Incident Report
🔵 Stable🕐 updated 2026-10-06
🔷 SkillSpec L3
pm-supplychain
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.
▶ Run it free — no key needed
📝 Grade your existing draft
⬇ Add to Claude (works in Duet)
📱 Use as an app
View SKILL.md ↗
What changed
🗣 Say this to your agent
“Document a shipment delay.”“Write up a logistics failure.”“Report a customs hold.”“Quantify a supply disruption.”“Draft the customer notice for a late delivery.”
What to give it
▸What happened — event type (port congestion, carrier failure, customs hold, damage, weather), shipment/PO references, discovery date
▸What's on the freight — SKUs, quantities, value, and what they feed (customer orders, production, safety stock)
▸Timing — original ETA, current best ETA, and how the delay compares to buffer stock on hand
▸Actions so far — reroutes, expedites, allocations already in motion
▸Customer exposure — which customers are affected and any committed dates or penalty/SLA clauses If details are thin, build the report with figures marked `[to confirm]` and list exactly what data closes each gap. A fast 80% report beats a complete one after the containment window closes.
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Impact quantified through all three layers — orders and dollars, not just delayed units
✓Delay netted against available stock before declaring customer impact
✓Severity assigned from the table, and the response posture matches it
✓Containment actions each have an owner, status, and cost
✓Root cause names an internal exposure, not just the external event
✓Customer draft contains no blame, no unconfirmed promise dates, and a mitigation offer
✓Unknowns marked `[to confirm]` with the data source that closes them
⚠️ What it refuses to do
Do not report freight value as the impact — a $40k container feeding a $2M line-down is a $2M problem
Do not stop the root cause at "the carrier/port/customs failed" — the exposure that let it hurt you is the fixable part
Do not promise customers a recovery date you don't have — give a date for the date instead
Do not let expedite costs go untracked — containment spend belongs in the report, or the same lane stays fragile at premium prices
Do not merge containment and prevention lists — one has hour deadlines, the other needs owners after the fire is out
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y -p pm-claude-skills pm-claude-skills-mcpRelated skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="logistics-incident-report"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
Logistics Incident Report is one of 1326 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog