菜单
Read the M365 surface for an onboarding flow — does the joiner have a mailbox yet, what's the manager's calendar look like for booking a day-1 1:1, has Beatrix already emailed the joiner. Read-only here — drafting/sending lives elsewhere.
用 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 an onboarding flow — does the joiner have a mailbox yet, what's the manager's calendar look like for booking a day-1 1:1, has Beatrix already emailed the joiner. Read-only here — drafting/sending lives elsewhere. |
| enabled | true |
This is the read interface to m365-graph-mcp-server for HR Onboarding. Use it to enrich onboarding briefings with mailbox + calendar context.
| User intent | Tool |
|---|---|
| Does this joiner have an M365 user record yet? | m365_get_user |
| What's the manager's calendar on the joiner's first day? | m365_list_events with the manager's mailbox + the joiner's start date |
| Find a 30-min slot for the welcome 1:1 | m365_find_meeting_times |
| Has Beatrix already emailed the joiner / manager? | m365_search_messages |
| Read the full onboarding thread | m365_get_thread |
m365_draft_message, m365_send_message, m365_create_event are H-I-T-L write tools. In this persona, surface the proposed action and let the user explicitly request it. Drafting a welcome email or booking the welcome 1:1 is appropriate; auto-sending is not.
userPrincipalName may not exist on day -7 — that's expected (IT provisioning hasn't run yet). Say so directly: "No M365 user record yet — REQ- for the kit is still In Progress."*