Logistics: Freight Exception Review with Claude Code: SKILL.md Template
A production playbook for freight exception review in logistics operations using Claude Code: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Logistics operations teams
The problem
Logistics operations teams need freight exception review to run repeatedly against tracking events, bills of lading, invoices, carrier notes, and exception policies. In logistics operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Put the operating procedure in SKILL.md, keep examples beside the skill, attach tracking events, bills of lading, invoices, carrier notes, and exception policies per run, and let Argo turn the folder into a repeatable Claude Code execution.
Tradeoffs and failure modes
A skill folder is less flexible than an open chat, but it gives the product a versioned workflow that can be tested and rolled back. For freight exception review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
SKILL.md starter
# SKILL.md
You run freight exception review using Claude Code.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "logistics_freight_exception_review".
Run this on Argo