$ ~/registry/skill/microsoft-agency-plugins-ff-oce-skills-ff-oce-dashboard

SKILL

ff-oce-dashboard

Name: ff-oce-dashboard
Author: microsoft

Generate an OCE shift dashboard summarizing incidents, pipelines, and errors.

Stars

★ 4,934

Source

GitHub

Updated

2026-07-14

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 4.9k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "ff-oce-dashboard" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/FluidFramework/main/.agency/plugins/ff-oce/skills/ff-oce-dashboard/SKILL.md
2. Save it as ~/.claude/skills/ff-oce-dashboard/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Generate shift overview

Prompt

Generate the current OCE shift status dashboard and give me a non-specific overall overview.

Expected

A shift status dashboard summarizing current incidents, pipeline status, errors, and overall system health.

See what's going on now

Prompt

What's going on with OCE right now? Show me the dashboard.

Expected

A shift-oriented overview dashboard that helps quickly understand current system activity and anomalies.

Open status dashboard

Prompt

Show the OCE status dashboard, focusing on incidents, pipelines, and errors.

Expected

A status dashboard focused on key operational indicators so on-call staff can quickly assess priorities.

// docs

OCE Shift Status Dashboard

Gathers data from multiple MCP servers in parallel and presents a consolidated shift status dashboard. Best-effort — partial results are always shown.

Procedure

Step 0: Confirm with the user

Before gathering any data, use the ask_user tool:

Question: "Would you like me to generate a shift status dashboard? This will query IcM, ADO, Kusto, Teams, and WorkIQ and may trigger auth prompts. Make sure you're connected to VPN first — it's required for Kusto and other internal services."

Choices: "Yes", "Yes, and write it to a file", "No"

If No: respond "No problem — what can I help you with?" and stop.
If Yes: proceed to Step 1. Present the dashboard in the console.
If Yes, and write it to a file: proceed to Step 1. Write the dashboard to oce-dashboard-<YYYYMMDD-HHmmss>.md in the current working directory instead of printing it to the console. Just confirm the filename when done.

Step 1: Launch 6 background agents in parallel

Use the task tool with mode: "background" for each. Instruct each agent to always terminate — either return its results or respond with "FAILED: <reason>" if the tool call errors or auth fails. Agents must never hang or retry indefinitely.

CRITICAL: Background agents do not inherit the agent prompt context. Each sub-agent prompt must be self-contained with all IDs, parameters, and tool-call details it needs. Use the templates below — do not construct prompts from memory.

Agent 1 — IcM Incidents

Call icm-search_incidents_by_owning_team_id for each team: 98481 (FF Hot), 149377 (Fluid Framework Client), 98313 (Azure Fluid Relay Client). Only include Active and Mitigated incidents — exclude Resolved. Report ID, Sev, Title, Status, Team, Created date.

Agent 2 — ADO Pipeline Health

Call ado-pipelines_get_builds for each pipeline definition (12 = Build, 56 = E2E, 63 = Stress) with project: "internal", branchName: "refs/heads/main", statusFilter: "Completed", top: 3, queryOrder: "FinishTimeDescending". Result codes: 2 = ✅, 4 = ⚠️, 8 = ❌. Report build ID, result, finish time, and overall trend.

Agent 3 — Loop-FF Integration Pipeline

Call ado-office-pipelines_get_builds with project: "OC", definitions: [29163], top: 5, queryOrder: "FinishTimeDescending". Important: Use the ado-office MCP server tools (NOT the default ado tools) — this pipeline is in the office ADO org, not fluidframework. Result codes: 2 = ✅, 4 = ⚠️, 8 = ❌. Report build ID, result, finish time, branch, and build number. Flag any failures — a failing integration pipeline means the next FF bump to Loop will break.

Agent 4 — Kusto Error Rates

Do not load the ff-oce-kusto skill. Call kusto-kusto_query with cluster_uri: "https://kusto.aria.microsoft.com", database: "6a8929bcfc6d44e9b13fee392ada9cf0", and this query:

Office_Fluid_FluidRuntime_Error
| where Event_Time > ago(1h)
| summarize ErrorCount = count() by AppName = tostring(App_Name)
| order by ErrorCount desc
| take 15

If it fails, retry with a simple summarize ErrorCount = count() fallback (no by clause). Report as a table: Partner, Error Count.

Agent 5 — Teams Pipeline Alerts

Call teams-ListChannelMessages with teamId 9ce27575-2f82-4689-abdb-bcff07e8063b, channelId 19:[email protected], top 50, and expand: "replies" to fetch threaded replies inline. The expand parameter is required — without it, replies will be null and acknowledgment status cannot be determined. Filter for messages from Azure DevOps (check from.displayName contains "Azure DevOps") in the last 2 weeks. Classify each as Acknowledged (has a text reply or ✅/☑️/👍/👀 reaction), Resolved (reply confirming fix), or Unacknowledged (no replies, no meaningful reactions). Report: Date, Description, Status, Action Needed.