メニュー
Handle work order operations — viewing, listing, creating, and updating work orders. Use when the technician asks about work orders, assignments, scheduling, job status, or needs to create or update a WO.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/microsoft-foundry/build-2026-demos --skill work-order-managementコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | work-order-management |
| description | Handle work order operations — viewing, listing, creating, and updating work orders. Use when the technician asks about work orders, assignments, scheduling, job status, or needs to create or update a WO. |
Use this skill for any work order operation — viewing, listing, creating, or updating.
All work order capabilities live in the Foundry Toolbox under the work_orders MCP server, so the actual tool names are prefixed work_orders___.
| Capability | Prefixed tool name |
|---|---|
| List / filter work orders | work_orders___list_work_orders_work_orders_get |
| Get a specific work order | work_orders___get_work_order_work_orders__work_order_id__get |
| Create a work order | work_orders___create_work_order_work_orders_post |
| Update a work order | work_orders___update_work_order_work_orders__work_order_id__patch |
If the work-order tools aren't already visible in your tool list, call tool_search once with limit: 10 and a short query like "work order". Examples:
tool_search({"query": "work order", "limit": 10})tool_search({"query": "create work order", "limit": 10}) for create flowsThe returned tools stay callable for the rest of the turn — do not search again.
| Request Type | Tool (prefixed name) | Key Parameters |
|---|---|---|
| View a specific WO | work_orders___get_work_order_* | work_order_id (e.g. WO-007) |
| List / filter WOs | work_orders___list_work_orders_* | status, priority, assigned_technician |
| Create a new WO | work_orders___create_work_order_* | title, description, priority, technician, location, due_date |
| Update an existing WO | work_orders___update_work_order_* | work_order_id + fields to change |
Invoke each tool via call_tool with {"name": "<prefixed_name>", "arguments": {...}}.
Always use filters when listing. If the technician asks "what are my open work orders?",
filter by status=open rather than listing all and filtering yourself.
For a single work order:
## WO-007 — Fiber Splice Repair
| Field | Value |
|-------|-------|
| **Status** | 🟡 In Progress |
| **Priority** | 🔴 Critical |
| **Technician** | Mike Chen |
| **Location** | 456 Industrial Pkwy, Building C |
| **Due Date** | 2025-06-15 |
| **Parts Needed** | FIB-012 (×2), FIB-045 (×1) |
**Description:** Repair damaged fiber splice in distribution panel, Building C, 3rd floor.
For multiple work orders, use a summary table:
| WO ID | Title | Status | Priority | Technician | Due Date |
|---|---|---|---|---|---|
| WO-003 | Cable Install | 🟢 Open | 🟡 Medium | Sarah Kim | 2025-06-10 |
| WO-007 | Splice Repair | 🟡 In Progress | 🔴 Critical | Mike Chen | 2025-06-15 |
Always include the label text after the icon — never show a bare colored circle.
Status:
Priority:
When status and priority appear on the same line (e.g., in a header), use labels to disambiguate:
🟡 In Progress | 🟡 Medium Priority — not 🟡 | 🟡
On create: Confirm with the technician before submitting if any required field is missing. Required: title, description, priority, assigned_technician, location, due_date.
On update: After a successful update, echo back exactly what changed:
✅ **WO-007 updated:**
- Status: In Progress → **Completed**
- Updated at: 2025-06-15T14:30:00Z
If a work order has parts_needed, mention them by part ID so the technician can follow up
with an inventory check. Offer: "Want me to check stock on these parts?"