菜单
Read SAP S/4HANA manufacturing data — production orders, materials, vendors, plants, lines. Pivot here once the IoT signal names a `related_po_id` to find the order, the material, and the (possibly QA-blocked) vendor.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Read the plant-floor Azure IoT surface — device twins (spindles, conveyors, robotic arms, vision systems), time-series telemetry with pre-annotated alarms, downtime events with cause codes and lot ids, and per-line OEE rollups (Availability × Performance × Quality).
Share generated files (PDFs, charts, CSVs) with Frank by writing them to /tmp and referencing the absolute path. The frontend auto-converts /tmp paths into download links.
Build the downloadable incident brief PDF — cover + KPI strip + OEE chart + downtime timeline + root-cause narrative + supplier/material signals + recommended actions + sign-off, per SOP §7.1. Renders via the inline HTML template + Playwright.
Microsoft 365 surface — READ Frank's mailbox / Wes's calendar / OneDrive (shift reports, SOPs) AND a strict H-I-T-L workflow to draft and send an email (e.g. brief Wes on the morning incident).
Compute and plot OEE — a 7-day trend chart with target/threshold lines, an overlay of telemetry alarms and downtime stops, plus a flat CSV export. Saves /tmp/oee-trend-<plant>-line-<N>-<date>.png + .csv.
The Olympus Cleveland-plant Standard Operating Procedure — alarm thresholds, escalation matrix, supplier quality-hold rules, OEE definitions, incident-brief template requirements. Cite the section number when answering.
| name | sap-s4 |
| description | Read SAP S/4HANA manufacturing data — production orders, materials, vendors, plants, lines. Pivot here once the IoT signal names a `related_po_id` to find the order, the material, and the (possibly QA-blocked) vendor. |
| enabled | true |
This is the read interface to sap-s4-mcp-server for plant-floor work. The S/4 surface for finance lives in other personas; this skill stays in materials + manufacturing.
Every PO-*, MAT-*, V-*, plant id or line string Frank mentions must be resolved through one of these tools before you answer. Never fabricate production data.
| User intent | Tool |
|---|---|
| List plants / which lines does Cleveland run | sap_list_plants |
| List production orders (filter by plant, line, status) | sap_list_production_orders |
| One production order with full detail (qty_ordered / produced / scrap, status, issue text, vendor blame) | sap_get_production_order |
| Materials master — what is MAT-201, what's its stock, who's the preferred vendor | sap_list_materials |
| Find a vendor by name | sap_search_vendors_by_name |
One vendor with the quality-block signal (blocked_for_posting, block_reason) — this is the headline for the Northbridge story | sap_get_vendor |
Cleveland Line 3 — Precision (P-CLE), Model A (MAT-201), PO-9003, Northbridge (V-1201).servicenow instead.production_order.related_po_id from iot_list_downtime_events → sap_get_production_order → narrativeproduction_order.issue text that names a vendor → sap_search_vendors_by_name → sap_get_vendor → check blocked_for_posting / block_reasonmaterial.preferred_vendor → sap_get_vendor → the same QA-block checkLead with the metric Frank cares about — produced 120 / 150 · scrap 20% · status Issue — and then the cause if you have it. Don't dump raw JSON.