菜单
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.
用 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).
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.
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.
| name | oee-analysis |
| description | 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. |
| enabled | true |
Use this skill whenever Frank asks for an OEE trend, a chart, "what does the week look like?", or any "show me, don't tell me" view of production. This is the computation surface — it uses code_interpreter against the numbers returned by azure-iot. Do NOT do mental math on OEE values; always send the numbers through this skill.
iot_get_oee(plant_id="P-CLE", line="<line>", date_from="<7 days ago>", date_to="<today>").iot_list_downtime_events(plant_id="P-CLE", line="<line>", since="<7 days ago>") — used as tick marks on the chart.iot_get_telemetry("DEV-3001", since="<window>") — used as the secondary axis on the chart.code_interpreter with the analysis script — DO NOT retype any numbers./tmp/oee-trend-<plant_slug>-line-<N>-<date>.png — chart/tmp/oee-trend-<plant_slug>-line-<N>-<date>.csv — flat OEE for the briefThe full script is in scripts/oee_analysis.py in this skill's directory. Read it once with file_read, then invoke via code_interpreter — DO NOT inline the script body in your response.
The script signature:
python /app/use-cases/plant-floor-supervisor/skills/oee-analysis/scripts/oee_analysis.py \
--plant-id P-CLE \
--line "Line 3 — Precision" \
--date 2026-06-09 \
--oee-json '<JSON returned by iot_get_oee>' \
--downtime-json '<JSON returned by iot_list_downtime_events, optional>' \
--telemetry-json '<JSON returned by iot_get_telemetry, optional>' \
--out-dir /tmp
Outputs to stdout: a 1-line summary of trend direction and the file paths. Outputs to disk: the .png + .csv.
watch zone (target-5 to target), light yellowinvestigate zone (<target-5), light rediot_get_oee inline; don't build the chart for one row.