メニュー
Read the IT-provisioning ticket(s) backing a new-joiner's onboarding — laptop kit, account creation, access groups. Used to surface "is IT ready for Priya's first day?"
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 | servicenow |
| description | Read the IT-provisioning ticket(s) backing a new-joiner's onboarding — laptop kit, account creation, access groups. Used to surface "is IT ready for Priya's first day?" |
| enabled | true |
This is the read interface to servicenow-mcp-server for HR Onboarding. Use it when you need to know the IT side of a joiner's setup: is the laptop ordered, is the M365 mailbox provisioned, are the Entra access groups assigned.
| User intent | Tool |
|---|---|
| "Is there an IT ticket for {joiner}?" | servicenow_list_tickets with assignment_group: "IT Provisioning" + caller filter |
| One ticket in detail (state, last note, ETA) | servicenow_get_ticket |
| Conversation history on a REQ | servicenow_list_work_notes |
| Resolve a USR-* to a person | servicenow_get_user (look at employee_id to thread back to workday EMP-*) |
caller_id, not the new joiner (the joiner doesn't have an account yet on day 1).New / In Progress / Awaiting User / On Hold / Resolved / Closed. Anything not Resolved/Closed is "still outstanding" for onboarding readiness purposes.it-service-desk persona, not us.