update Markdown skills

skill-examples/board-invalid-context.md

@@ -0,0 +1,26 @@
+---
+id: board-invalid-context
+name: Board (invalid context)
+description: Negative test — a position-scoped source on a placement that supplies no position.
+pages:
+  - positions
+status: active
+ui:
+  type: card
+  placement: after-position-list-summary
+  title: Board
+  source: position.activity
+  periods:
+    - today
+    - last-7-days
+    - previous-month
+---
+
+# Board (invalid context)
+
+## Purpose
+
+Deliberately wrong, and kept so the refusal stays tested. `position.activity`
+needs one position to read; `after-position-list-summary` renders once above the
+grid with no position in context. Saving this must be refused with a message that
+names both halves of the mismatch.

skill-examples/board-page-level.md

@@ -0,0 +1,31 @@
+---
+id: board
+name: Board
+description: Helps Owliver understand, analyze, and act on the current task board.
+pages:
+  - positions
+status: active
+ui:
+  type: card
+  placement: after-position-list-summary
+  title: Board
+  source: candidates.activity
+  periods:
+    - today
+    - last-7-days
+    - previous-month
+---
+
+# Board
+
+## Purpose
+
+Helps Owliver understand the current task board by summarizing relevant work activity, identifying items that need attention, and explaining the current status of tasks shown on the board.
+
+## Capabilities
+
+- Summarize relevant activity from the current board.
+- Identify tasks or work items that need attention.
+- Explain the current status of tasks and work items.
+- Highlight recent activity and meaningful changes.
+- Help Owliver analyze board activity using the available board data.

skill-examples/board-position-card.md

@@ -0,0 +1,31 @@
+---
+id: board-position-card
+name: Board (per position)
+description: Control test — the same Board card, rendered inside every position card.
+pages:
+  - positions
+status: active
+ui:
+  type: card
+  placement: grid-card
+  title: Board
+  source: position.activity
+  periods:
+    - today
+    - last-7-days
+    - previous-month
+---
+
+# Board (per position)
+
+## Purpose
+
+The position-aware control for the page-level Board card. `grid-card` resolves to
+`after-position-card`, which renders inside each position card and supplies that
+position as context — so `position.activity` reads and the card is drawn once per
+role rather than once for the page.
+
+## Capabilities
+
+- Summarize activity for the position the card belongs to.
+- Show that activity across today, the last 7 days and the previous month.

skill-examples/board-ui-test.md

@@ -0,0 +1,40 @@
+---
+id: board-ui-test
+name: Board
+description: Renders the Board card once above the position list on the Positions page.
+pages:
+  - positions
+status: active
+ui:
+  type: card
+  placement: after-position-list-summary
+  title: Board
+  source: candidates.activity
+  periods:
+    - today
+    - last-7-days
+    - previous-month
+---
+
+# Board
+
+## Purpose
+
+The page half of the Board, and only that half. One card, above the position
+grid, reading activity across the workspace.
+
+`after-position-list-summary` renders once for the page and supplies no
+position — `surfaces.js` records that placement as providing nothing — so the
+card reads `candidates.activity`, which declares `context: null` and counts
+applications across the workspace over the periods named here.
+`position.activity` is refused at this placement by `unresolvableSections`, and
+correctly: it needs one position, and this placement has none to give.
+
+This definition declares no `owliver:` block, so it contributes no capability,
+no suggestion chip and no conversational answer. It is a page extension and
+nothing else.
+
+## Capabilities
+
+- Show workspace application activity above the position list.
+- Compare today, the last 7 days and the previous month in one card.

skill-examples/owliver-conversation-test.md

@@ -0,0 +1,63 @@
+---
+id: owliver-conversation-test
+name: Workspace Activity Assistant
+description: Answer questions about applications across the workspace and the roles still open.
+pages:
+  - positions
+status: active
+triggers:
+  - workspace applications
+  - applications across the workspace
+  - roles still open
+  - roles needing attention
+owliver:
+  enabled: true
+  # Every suggestion names the capability it asks for, so a chip and an answer
+  # are one-to-one rather than both falling through to the first declared
+  # capability.
+  suggestions:
+    - label: Summarize workspace applications
+      capability: summary
+    - label: List the roles still open
+      capability: list
+  capabilities:
+    - summary
+    - list
+  responses:
+    summary:
+      title: Workspace Applications
+      source: candidates.activity
+      periods:
+        - today
+        - last-7-days
+        - previous-month
+    list:
+      title: Roles Still Open
+      source: positions.demand
+      limit: 5
+---
+
+# Workspace Activity Assistant
+
+## Purpose
+
+The panel half, and only that half. No `ui:` block, so nothing is drawn on the
+Positions page and no card appears above or inside the grid.
+
+Each response names its own `source:` directly, which is what a definition
+without a `ui:` section must do — `normalizeSkillOwliver` inherits a source from
+the first `ui:` section only when one exists, and reports
+`owliver.responses.<capability>: a response needs a source, or a ui: section to
+read from` when neither is present.
+
+Both sources declare `context: null`, so neither answer asks which position is
+meant: `resolveEntity` returns immediately and no
+"This section needs a position to read" is possible. The shapes match what each
+source offers — `summary` is prose and is exempt from the shape check, and
+`list` is a shape `positions.demand` declares.
+
+## Capabilities
+
+- Summarize applications across the workspace over today, the last 7 days and
+  the previous month.
+- List the open positions and how many applicants each has.