Menu
Detects and classifies Duplicate Purchase Order (PO) exceptions in B2B order intake. Triggered on EDI_850_DUPLICATE_PO events.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Classifies a post-extraction email-channel sales-order envelope into one-click approve, standard review, low-confidence, or fatal-reject. Triggered on EMAIL_ORDER_ENTRY_REQUEST events.
Triaged a back-order / out-of-stock condition on an inbound order line and ranks resolution options — alternate DC, substitute SKU, split shipment, or reschedule. Triggered on BACK_ORDER_OOS events.
Classifies shipment delay severity (SD-DELAY-001 minor / SD-DELAY-002 severe) and ranks expedite / split-ship / reschedule options. Triggered on DELIVERY_DELAY events.
Classifies non-duplicate EDI 850 line mismatches (SKU, qty, UOM, ship-to) and selects the appropriate resolution path. Triggered on EDI_850_LINE_MISMATCH events whose metadata.mismatch_sub_type is not PRICE_MISMATCH.
Decides whether to round a PO line up to the Minimum Order Quantity, accept below MOQ, or escalate for a KNMT waiver. Triggered on MIN_ORDER_QTY events.
Classifies a PO whose total quantity exceeds the contract max and recommends a per-line trim plan that preserves pallet integrity where possible. Triggered on OVER_MAX_QTY events.
| name | duplicate-po |
| description | Detects and classifies Duplicate Purchase Order (PO) exceptions in B2B order intake. Triggered on EDI_850_DUPLICATE_PO events. |
| metadata | {"version":"1.1.0","author":"CPG Expert-Systems-Architect","required_tools":["mcp-sap-connector","mcp-pinecone-search"],"recipes":["DuplicatePORecipe.py"],"constrained_generation":["Guidance","Outlines"]} |
This skill is triggered when an inbound EDI 850 order is flagged as a potential
duplicate of an existing PO in the order management system. It classifies the
duplicate probability and routes to the correct recipe or escalation path.
Do not improvise scoring logic. All scoring and thresholds live in DuplicatePORecipe.py;
weight overrides are resolved by the tenant_config gateway per ADR-029.
EDI_850_DUPLICATE_PO).event.metadata.signal_scores.DUPLICATE_PO.DuplicatePORecipe.py — the only allowed recipe for this intent.oms.get_fulfillment_status, oms.get_matched_po_details, and
tenant_config.resolve_for_event (the latter supplies the per-event
weight map per ADR-029, with fail-closed-to-platform on contract
violation). Do not call any of these gateways directly.Use Guidance / Outlines for all machine-consumed outputs:
DUPLICATE_PO (the only valid value for this event type)DuplicatePORecipe.py (registered recipe, no other allowed)DuplicatePORecipe.pyFAIL_TO_HUMANBefore calling any recipe, check the Compliance Shadow. If the shadow returns RED, halt execution and explain the compliance breach. If the shadow returns YELLOW, route to MANUAL_REVIEW_REQUIRED.
Always include the Recipe Execution Log snippet for audit traceability.
The log must capture: composite_score, classification, recommended_action, signal_breakdown.
The tenant_config gateway response (per-layer contribution trace +
validation_status) lives on state.enrichment_context["tenant_config"]
and surfaces on the canonical envelope (ADR-028 G2 / A6).