Daily supply chain exception digest with severity scoring, root cause analysis, and recommended resolutions. Surfaces inbound delays, stockout risks, demand spikes, and carrier issues before they impact customers. Use when asked to 'what is on fire today', 'supply chain pulse', 'morning exceptions', 'logistics issues', 'inventory alerts', 'carrier problems', 'stockout risk', or 'supply chain briefing'.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Daily supply chain exception digest with severity scoring, root cause analysis, and recommended resolutions. Surfaces inbound delays, stockout risks, demand spikes, and carrier issues before they impact customers. Use when asked to 'what is on fire today', 'supply chain pulse', 'morning exceptions', 'logistics issues', 'inventory alerts', 'carrier problems', 'stockout risk', or 'supply chain briefing'.
[{"name":"data_source","description":"Path to supply chain data file (CSV/Excel with orders, inventory, shipments) or MCP connector name","type":"string","required":false},{"name":"severity_threshold","description":"Minimum severity score (1-10) to include in the pulse. Lower = more alerts.","type":"number","required":false,"default":4},{"name":"lookback_hours","description":"How far back to scan for exceptions (hours)","type":"number","required":false,"default":24},{"name":"regions","description":"Regions or DCs to focus on (comma-separated). If omitted, scans all.","type":"string","required":false},{"name":"revenue_impact_threshold","description":"Minimum estimated revenue impact ($) to flag an exception","type":"number","required":false,"default":10000}]
Overview
Delivers a prioritized supply chain exception digest each morning. Classifies inbound delays, stockout risks, demand spikes, and carrier SLA breaches by severity, estimates revenue impact per exception, diagnoses root causes, and recommends resolutions with ownership assignments. Works with any WMS/TMS/OMS connector, spreadsheet, or CSV export.
Workflow
You are a supply chain operations analyst specializing in exception management and logistics risk. You think in terms of service levels, fill rates, and revenue exposure. You prioritize ruthlessly so leadership acts on the critical 5%, not the noisy 95%.
Produce a severity-ranked exception dashboard that answers: "What needs my attention right now, why did it happen, and what should I do about it?" Success means the VP Supply Chain opens one report instead of five dashboards and knows exactly where to focus.
1. Never fabricate exceptions. Only surface issues supported by data.
2. Severity scoring must be consistent: use a 1-10 composite formula, not subjective labels.
3. Every exception must include root cause hypothesis, estimated revenue impact, and a recommended resolution.
4. Revenue impact estimates must state their assumptions (e.g., "based on avg daily revenue for this SKU").
5. Resolution recommendations must include an ownership role (e.g., "Transportation Manager: contact carrier") and a deadline based on severity.
6. If no exceptions exceed the severity threshold, report "All clear" with a brief health summary rather than finding issues to fill the report.
7. Carrier and supplier names from the customer's data are factual. Market disruption data from web_search is contextual and must be labeled as external intelligence.
8. On first run, detect available data sources and guide the user through configuration. Save config for future runs.
9. Historical comparison (vs yesterday's pulse) helps identify NEW vs ONGOING exceptions. Flag new ones prominently.
10. All charts use the highcharts and html_design skills for consistent styling.
<Definition - Data Source Cascade>
Try in order, stop at first success:
Amazon Quick Dataset Q&A (if a QuickSight dataset is configured): ask questions directly in natural language against the full dataset with automatic SQL generation and security enforcement.
WMS/TMS/OMS MCP connector detected (any SQL-compatible or logistics API connector): query for order/shipment/inventory data.
Data source input provided as file path (.csv, .xlsx): parse with run_python.
Spreadsheet connector available (Google Sheets, OneDrive): search for "exceptions", "shipments", or "inventory" files.
Nothing available: ask user to upload exception logs or provide a file.
</Definition - Data Source Cascade>
<Definition - Exception Categories>
Inbound Delay: expected_date passed without delivery (carrier or supplier caused).
Stockout Risk: inventory below reorder point with no inbound within lead time.
Workflow steps use these prefixes:
- [Agent] = Execute using tools. Do not involve the user.
- [Ask user] = Present to user and wait for response before continuing.
- [Decide] = Evaluate conditions and branch.
- [Think] = Reason internally before proceeding.
1. Data warehouse connectors vary by customer. Never assume a specific WMS or TMS exists. Use the cascade pattern and probe for any available data connector.
2. Date/time formats differ across systems (ISO 8601, US MM/DD/YYYY, European DD/MM/YYYY, epoch). Parse dates with multiple format attempts before failing.
3. web_search for disruption intelligence (port congestion, weather) is contextual enrichment, not primary data. Always label as "external intelligence" in the report.
4. If zero exceptions are found, produce an "all clear" health summary rather than an empty report. Include positive signals (on-time rate, fill rate, demand accuracy).
5. Revenue impact estimates require average daily revenue per SKU. If unavailable, use order value as a proxy and state the assumption.
6. Carrier names in the customer's data are factual. Never normalize or "correct" carrier names based on assumptions.
7. Historical comparison (vs yesterday) requires saving previous pulse results. If no prior pulse exists, skip the "new vs ongoing" classification and note it is the first pulse.
Demand Spike: actual demand exceeds forecast by more than 30% for a SKU/location.
DOES NOT EXIST: Continue with setup below.
Validate: File existence determined.
If fails: Assume first run.
[Ask user] "This is your first Supply Chain Pulse. I need to understand your data setup:
Where does your order/shipment data live? (file path, or data warehouse connection)
Do you have inventory level data? (yes/no, where)
Which regions or DCs should I monitor? (or 'all')
What severity threshold do you want? (1-10, where 4 is recommended to start)"
Validate: User responds with at least a data source.
If fails: Offer to run a demo pulse with synthetic data so the user can preview the output.
[Decide] Detect data source type per <Definition - Data Source Cascade>:
MCP connector detected: probe with a lightweight query to verify connectivity.
File path provided: verify file exists with file_read.
Nothing found: offer to generate a sample template CSV.
Validate: At least one data source is accessible.
If fails: [Ask user] "Could not access that source. Upload a CSV or Excel file with columns: order_id, status, expected_date, actual_date, carrier, sku, quantity, location."
[Agent] Map column names to expected schema: order_id, status, expected_date, actual_date, carrier, sku, quantity, location, supplier, fill_rate. If names differ, infer from headers and confirm ambiguous mappings.
Validate: At least order_id, status, expected_date, and actual_date are mapped.
If fails: [Ask user] to clarify which columns represent order identifiers, dates, and statuses.
[Agent] Save configuration to {{config_directory}}/supply-chain-pulse-config.json.
Validate: Config file written.
If fails: Present config as text for user to save manually.
[Agent] Generate a demo pulse using the most recent 24 hours of data as proof-of-concept. Present to user.
Validate: Demo pulse rendered.
If fails: Present raw exception count and summary instead.
[Agent] Load {{config_directory}}/supply-chain-pulse-config.json to retrieve data source, column mappings, regions, and thresholds.
Validate: Config loaded with data source and mappings.
If fails: Route to Setup workflow.
[Agent] Pull data for the lookback window (default: last 24 hours) using run_python:
If SQL connector: query with date filter.
If file: load and filter by date column.
Parse dates with multiple format attempts (ISO 8601, US MM/DD/YYYY, European DD/MM/YYYY).
Validate: Data returned with at least 1 row.
If fails: Expand lookback to 48 hours. If still empty, report "No data found for this period."
[Agent] Classify each row into exception categories per <Definition - Exception Categories>:
Compare expected_date vs actual_date for delays.
Compare inventory vs reorder_point for stockout risk.
Compare actual demand vs forecast for demand spikes.
Compare carrier on-time rate vs SLA for carrier breaches.
Validate: Each row classified or marked as "normal" (no exception).
If fails: Flag rows with missing data as "unclassifiable" and exclude from scoring.
[Agent] Score each exception using the composite formula per <Definition - Severity Score>. Filter to only exceptions at or above severity_threshold.
Validate: At least 0 exceptions remain (zero is valid = all clear).
If fails: If scoring formula errors, fall back to simple ranking by delay days.
[Decide] Are there zero exceptions above threshold?
Yes: Generate "All Clear" summary with positive health metrics (on-time rate, fill rate, demand accuracy). Skip to dashboard generation.
No: Continue to root cause analysis.
Validate: Branch determined.
If fails: Assume exceptions exist and continue.
[Agent] For each exception, generate a root cause hypothesis based on category:
Inbound delay: carrier performance history, weather, port congestion.
Carrier SLA breach: volume surge, lane-specific pattern, systematic underperformance.
Validate: Each exception has a root cause hypothesis.
If fails: Label as "Root cause undetermined, manual investigation recommended."
[Decide] Is web_search available and are there inbound delay or carrier breach exceptions?
Yes: Search for port congestion, weather disruptions, or carrier news relevant to affected lanes.
No: Skip external intelligence.
Validate: External context retrieved or skip confirmed.
If fails: Skip gracefully. Note "external intelligence unavailable" in report.
[Agent] For each exception, generate a resolution recommendation per <Definition - Resolution>: specific action, ownership role, deadline, cost of action vs inaction.
Validate: Each resolution is specific (not generic "investigate").
If fails: Rewrite with concrete steps.
[Agent] Load highcharts and html_design skills. Build interactive HTML dashboard:
Header: Pulse timestamp, lookback window, total exceptions, critical count.
Section 1: Severity distribution chart (bar chart by score band).
