菜单
Convention for writing downloadable files to /tmp so the user can pick them up
用 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 | file-sharing |
| description | Convention for writing downloadable files to /tmp so the user can pick them up |
| enabled | true |
When you produce a file the user needs to download — a PDF brief, a CSV export, a chart — write it to /tmp/<descriptive-name>.<ext> and reference the path in your response.
The backend exposes /tmp paths to the frontend as downloadable artifacts. The user clicks the path to open / save.
/tmp/account-brief-<account-slug>.pdf — single-account briefing PDFs/tmp/pipeline-<owner>-<period>.csv — pipeline exports/tmp/<name>.png — chartsUse lowercase, hyphens, no spaces, no special characters.
After writing the file, mention it in your response on its own line as a markdown link:
📄 [/tmp/account-brief-acme-corp.pdf](/tmp/account-brief-acme-corp.pdf)
/tmp/ — not ~/, not relative paths.