agent build

skills/operational-risk.md

@@ -0,0 +1,94 @@
+---
+id: operational-risk
+name: Operational Risk
+description: Surface what is going wrong operationally across hiring and the roster.
+category: operations
+pages:
+  - control-center
+  - activity
+status: active
+version: 1
+triggers:
+  - operational risk
+  - operations risk
+  - what is going wrong
+  - backlog
+  - decisions owed
+owliver:
+  enabled: true
+  suggestions:
+    - label: What is going wrong operationally?
+      capability: list
+    - label: Summarize operational risk
+      capability: summary
+  capabilities:
+    - summary
+    - list
+    - table
+    - stats
+    - insight
+  responses:
+    summary:
+      title: Operational risk
+      source: operations.risk
+    list:
+      title: Operational risks
+      source: operations.risk
+    table:
+      title: Operational risks
+      source: operations.risk
+    stats:
+      title: Operational risk
+      source: operations.risk
+    insight:
+      title: Biggest operational risk
+      source: operations.risk
+---
+
+# Operational Risk
+
+## Purpose
+
+- Surface the operational problems that need somebody to act.
+- Draw them from every domain, because they feel like one problem to the person
+  who has to fix them.
+- Report nothing when the operation is running.
+
+## Capabilities
+
+- Detect strong candidates left awaiting a decision.
+- Detect an unscreened application backlog.
+- Detect open roles with no applicants.
+- Detect shifts going unworked.
+
+## Data
+
+Reads `operations.risk`, which joins `JobApplication`, `JobPosting` and
+`ShiftRecord`.
+
+## Analysis
+
+Four checks, each with a floor so ordinary operation does not trip them:
+
+1. **Decisions owed** — a candidate scoring 70 or above, screened or
+   shortlisted, and not moved on. Any such candidate counts.
+2. **Unscreened backlog** — three or more applications with no score.
+3. **Roles with no applicants** — any open role nobody has applied to.
+4. **Shifts unworked** — two or more absences or no-shows in the last 7 days.
+
+Findings are ordered most severe first. A finding is included only when it
+exists; an empty list means the operation is running, not that the check was
+skipped.
+
+## Output
+
+A count of open risks, then a row per risk naming what is wrong and the figures
+behind it.
+
+## Limitations
+
+- Thresholds are fixed rather than tuned to this workspace's volume.
+- "Decisions owed" assumes a screened, strong candidate should be progressed.
+  A candidate deliberately held is indistinguishable from one overlooked.
+- The shift check covers the last 7 days only; a longer pattern is Attendance
+  Analysis's question.