メニュー
Read the M365 surface for a ServiceNow caller — presence (Available / Busy / OOO), the OOO auto-reply text (key for triage when the caller is unreachable), recent mail / calendar context. Used to know whether to chase the caller or their cover.
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 | m365-graph |
| description | Read the M365 surface for a ServiceNow caller — presence (Available / Busy / OOO), the OOO auto-reply text (key for triage when the caller is unreachable), recent mail / calendar context. Used to know whether to chase the caller or their cover. |
| enabled | true |
This is the read interface to m365-graph-mcp-server. Use it to enrich triage when you need to know whether a caller is actually reachable right now, what their OOO message says, or whether they've already emailed about the issue.
| User intent | Tool |
|---|---|
| Is the caller currently OOO / what's their auto-reply? | m365_get_user_presence |
Resolve EMP-* ↔ email ↔ display name | m365_get_user |
| Has the caller emailed about this issue? | m365_search_messages with mailbox={EMP-*} + a query word from the ticket |
| What's on the caller's calendar today (for VIP / exec) | m365_list_events |
When triaging a P1/P2 or VIP ticket:
m365_get_user_presence(EMP-*) →
Available / Busy → chase directlyOutOfOffice / Offline with ooo.enabled: true → read the OOO message. If it names a cover, chase the cover instead and add a public note on the ticket.m365_search_messages(mailbox=EMP-*, query=<keyword>).m365_draft_message, m365_send_message, m365_create_event are H-I-T-L write tools. This use-case does not own them (they belong to use-cases that send mail or book meetings). Don't call them from here — if the user wants to email the caller, propose it as a next step and hand off.
EMP-* id and email.