logistics-incident-report
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.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill logistics-incident-report --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 Ask for these if not provided: - **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
- What This Skill Produces
- Required Inputs
- Impact & Severity Framework
- Output Format
- Logistics Incident Report: [event] — [reference]
- Quality Checks
- Anti-Patterns
What does the logistics-incident-report skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill logistics-incident-report --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.