{"id":81968,"plugin_id":"plugin_asdk_app_6adb8b000cbc8191a5b0646bbba32e50","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-05T01:19:48.401Z","digest":"260547ce19aee0cc3f09ebc4d94f7a1401aa787e5340acd01ab16766428ed8bf","against":null,"payload":{"description":"Turn order lines from a CSV, a spreadsheet export or a list into an X12 850 purchase order. Use when a buyer, or a supplier testing a trading partner connection, has order lines and needs them as EDI, asks how to send a purchase order by EDI, or wants a sample 850 built from their own data.","included_files":[],"name":"spreadsheet-to-850","skill_md_contents":"---\nname: spreadsheet-to-850\ndescription: Turn order lines from a CSV, a spreadsheet export or a list into an X12 850 purchase order. Use when a buyer, or a supplier testing a trading partner connection, has order lines and needs them as EDI, asks how to send a purchase order by EDI, or wants a sample 850 built from their own data.\n---\n\nUse this workflow when the user has order lines and needs an 850. The user's own instructions take priority over these steps.\n\n## Steps\n\n1. Call `generate_x12_850_from_rows` with the lines: `csv_text` for a pasted or attached CSV with a header row, or `rows` for a list you have read from the conversation. Each line needs a PO number, a quantity, and a vendor item number or a UPC/EAN/GTIN.\n2. Rows that share a PO number become one 850. Tell the user how many purchase orders and lines were built, and list any rows the tool skipped with the reason it gave.\n3. Give the user the 850 text from the result. Say that it uses version 004010 and that partner-specific segments (such as REF department numbers) are not added, so they should check it against the partner's implementation guide.\n4. If a GTIN was rejected for its check digit, offer to check the column with `check_gs1_identifiers` (the gs1-barcode-check skill).\n\n## Routing\n\n- A supplier answering a purchase order they received (855, 856, 810): follow the purchase-order-response skill instead. This skill builds purchase orders only.\n\n## Rules\n\n- Never invent a PO number, quantity, price or item number. Ask the user for anything missing.\n- The output is validated by the tool. Do not edit it by hand; if the user wants a change, change the rows and call the tool again.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}