メニュー
Read Workday HCM data for a ServiceNow caller — resolve `employee_id` to a human (display name, manager, department, location, status). Used to enrich VIP triage and to know if the caller is currently on leave.
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 | workday |
| description | Read Workday HCM data for a ServiceNow caller — resolve `employee_id` to a human (display name, manager, department, location, status). Used to enrich VIP triage and to know if the caller is currently on leave. |
| enabled | true |
This is the read interface to workday-mcp-server. Use it whenever you need to attach a human face + reporting line to a ServiceNow caller's employee_id. Don't call it speculatively — only when a triage or escalation actually needs the org context.
| User intent | Tool |
|---|---|
Resolve an EMP-* id to a person | workday_get_employee |
| Search by name | workday_search_employees_by_name |
| "Who's the caller's manager?" | workday_get_employee → read manager_id → workday_get_employee again |
| Verify the caller is currently active (not on leave / terminated) | workday_get_employee → check status |
| Direct reports of a manager (rare for IT desk) | workday_list_employees with manager_id= |
users.json carries employee_id (USR-1001 → EMP-1001).workday_get_employee(EMP-*) returns the org context.On Leave, hand off to m365-graph m365_get_user_presence to read the OOO message and find out who's covering.Jamal Carter (USR-2102, EMP-2102).status: "On Leave" prominently — it changes triage (the caller may not respond, you may need to chase the coverer).