updated skill file

delay-list-snooze-orders-skill/SKILL.md

@@ -74,26 +74,112 @@ Process in this exact order to ensure data is fresh for downstream decisions:
 * The Postermen
 * Intervlag
 * Vila Etiketten
-* VG Print BV
+* VG Print B.V.
-* Zalsman BV
+* Zalsman B.V.
 * Oakdene Services
 * I print 1925
 * Digiforce
 * Enson
 * Probo
-* Promino
+* Promio
 * Inpromo
 * Today's Media
 * Pressing
 * Drukkerij Van As
 * Oakdene Services
 
-**Action**: If you want to snooze an order call n8n-mcp snooze-order workflow.
+**Action**: If you want to snooze an order call traffic-mcp snooze-order workflow.
 with a body like this:
 {
   orderDetailId: %id_orderdetail%
 }
 
+**Action**: Sent information to traffic-mcp with call slack-feed-traffic-delay-list. Use the format below.
+## Slack Message Format for Snoozed Orders
+
+When posting snoozed order results to Slack, always use this exact format with Slack mrkdwn syntax.
+
+### 1. Header
+A bold line with the total count:
+```
+*Here are all {count} snoozed orders:*
+```
+
+### 2. Table
+Wrap the table in a Slack code block (triple backticks) so columns stay aligned:
+```
+```
+Order Detail ID | Supplier                    | Carrier            | Product
+5768484         | De Groot Drukkerij B.V.     | DPFINT-STANDARD    | foldedleafletsv2
+5785996         | Probo                       | UPS-UPS_STANDARD   | smallstickersownsize
+```
+```
+
+- Use `|` as column separator for readability
+- Include every order — never truncate or summarize with "and X more"
+- Column order is fixed: Order Detail ID → Supplier → Carrier → Product
+- The header count must match the actual number of rows
+
+### 3. Summary footer
+After the code block, add a summary line in italic:
+```
+_All had state "Your order has been packaged", target dispatch date of March 13, and valid tracking links._
+```
+
+If orders have different states or dispatch dates, group them:
+```
+_• {count} orders with state "{state_a}", target dispatch date of {date_a}_
+_• {count} orders with state "{state_b}", target dispatch date of {date_b}_
+_All had valid tracking links._
+```
+
+### Posting Rules & Slack Character Limit
+
+Slack has a ~4000 character limit per message. If the full table exceeds 25 rows, you **must** split it into multiple messages to prevent the code block formatting from breaking. Don't send the message as json.
+
+**Important — Slack message formatting:** Always send message text with **actual line breaks**, not `\n` escape characters. If you type `\n` literally in the input, the entire message will appear as one long line in Slack. Write the message across multiple lines in the input field itself
+
+**Splitting logic:**
+1. Calculate the number of parts needed: `ceil(total_rows / 25)`
+2. Each message must be a **self-contained code block** (with its own opening and closing triple backticks)
+3. **First message** starts with the bold header: `*Snoozed orders (part 1/{total_parts}):*`
+4. **Middle messages** use: `*Snoozed orders (part X/{total_parts}):*`
+5. **Last message** includes the italic summary footer after the code block
+6. If all orders fit in a single message (≤25 rows), use the standard header: `*Here are all {count} snoozed orders:*`
+
+**Example with 56 orders (3 parts):**
+
+Message 1:
+```
+*Snoozed orders (part 1/3):*
+``` ```
+Order Detail ID | Supplier                    | Carrier            | Product
+5768484         | De Groot Drukkerij B.V.     | DPFINT-STANDARD    | foldedleafletsv2
+...rows 1-25...
+``` ```
+```
+
+Message 2:
+```
+*Snoozed orders (part 2/3):*
+``` ```
+Order Detail ID | Supplier                    | Carrier            | Product
+...rows 26-50...
+``` ```
+```
+
+Message 3:
+```
+*Snoozed orders (part 3/3):*
+``` ```
+Order Detail ID | Supplier                    | Carrier            | Product
+...rows 51-56...
+``` ```
+_All had state "Your order has been packaged", target dispatch date of March 13, and valid tracking links._
+```
+
+Send each part as a separate call to `mcp__traffic-mcp__Call_slack-feed-traffic-delay-list_`.
+
 
 **Confidence:** If ALL criteria match exactly → auto-execute (99%+ confidence). If any field is ambiguous or missing → MANUAL\_REVIEW.
 
@@ -218,7 +304,7 @@ When the supplier is **The Postermen**, the carrier field may be any value when
 ```
 Operator: "Process today's delay list. No special notes."
 
-Step 1: Fetched delay list via API ‒ 347 delayed orders. 4 records missing data → MANUAL_REVIEW.
+Step 1: Fetched delay list via API → 347 delayed orders. 4 records missing data → MANUAL_REVIEW.
 Step 2: 89 orders match auto-snooze criteria → Snoozed 12h. Batch 1/1 (89). All succeeded
 
 SUMMARY: 343 processed | 16 manual review | 0 failures