Harness Session Inventory
This is a Hermes-native harness-session-inventory workflow skill.
Why This Exists
harness-session-inventory exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration.
Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
Examples
Good example:
- Prompt: harness-session-inventory compare Codex, Claude Code, Hermes, MCP configs, and worktrees for drift before we dispatch agents.
- Expected behavior: Produce
prepare_harness_session_inventory with required context, wrapper actions, and not-evidence boundaries.
- Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.
Bad example:
- Prompt: harness-session-inventory claim every MCP host loaded and every agent session is healthy from config files alone.
- Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
- Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.
Completion Checklist
- The inventory scope names the harnesses, sessions, MCP hosts, connector configs, and worktrees being compared.
- Prepared, observed, missing, stale, and drifted entries are separated before any health or progress claim.
- The next action says whether to load a host, verify a connector, inspect a worktree, dispatch an executor, or stay blocked.
Recovery Notes
- If config sources are unavailable, report only the discovered surfaces and mark the missing hosts not_observed.
- If cleanup, host load, connector execution, or session progress is requested, route to the owning workflow instead of folding it into inventory.
Workflow Lane
- Current lane: Automation and status (
achievements, workspace-audit, production-audit, automation-blueprint, github-event-ops, github-issue-intake, buzz, agent-board, +35 more) - schedules, status, health, and ops review.
- If intent belongs to another lane, hand back to
oh-my-hermes or name the adjacent workflow.
- Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use when operators need a cross-harness/session/MCP/worktree inventory and drift summary before claiming any host loaded, connector ran, or agent session progressed.
Strong routing signals: `harness-session-inventory`, `harness session inventory`, `session inventory`, `session adapter`, `session adapters`, `harness sessions`, `mcp inventory`, `mcp config inventory`, `mcp drift`, `harness drift`, `connector drift`, `worktree inventory`, `worktree lifecycle`, `operator inventory`, `control pane inventory`, `codex session inventory`, `claude code session inventory`, `find previous coding session`, `recover coding session`, `previous codex coding session`, `coding session recall`, `세션 인벤토리`, `지난 코딩 세션`, `코딩 세션 복구`, `세션 기억 복구`, `하네스 세션`, `하네스 드리프트`, `MCP 인벤토리`, `MCP 설정 드리프트`, `워크트리 인벤토리`, `커넥터 드리프트`
Catalog Metadata
Category: observability
Phase: harness-session-inventory
Hermes role: tracker
Quality tier: workflow-surface-gated
Reasoning demand: standard
Quality bar:
- Name the user-facing workflow objective, required context, next action, and stop condition.
- Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.
- Expose missing tools, credentials, targets, or observations as user-visible gaps.
Handoff policy:
Keep this as Hermes-facing orchestration guidance first. Prepare executor, connector, gateway, or host-runtime handoff only when the user accepts that next step and observed evidence can be recorded.
Required inputs:
- user request
- target context
- delivery or status expectation
- known missing evidence
Expected outputs:
- harness_session_inventory/v1 card or guidance
- harness_session_adapter_matrix/v1
- mcp_inventory_drift_report/v1
- worktree_lifecycle_snapshot/v1
- session_progress_slots/v1
- next action
- prepared-vs-observed boundary
Artifact expectations:
- harness_session_inventory/v1 metadata-only runtime or wrapper card when recorded
- harness_session_adapter_matrix/v1 with observed, prepared, missing, and stale adapters
- mcp_inventory_drift_report/v1 with secret-redacted config/source drift only
- worktree_lifecycle_snapshot/v1 with merge-conflict and cleanup candidates when observed
Safety rules:
- A harness session inventory is not host load, MCP tool-call, connector availability, executor dispatch, worktree cleanup, merge-conflict resolution, or session progress evidence.
- Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.
Runtime Evidence
Preferred harness for this skill: harness-session-inventory.
omh runtime record --skill harness-session-inventory --harness harness-session-inventory --status started
Record observed delegation results; otherwise return not_available or not_observed.
Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
Preserve workflow intent and stop conditions; verify before claiming completion.
Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
1---
2name: "omh-harness-session-inventory"
3description: "[omh] Hermes harness session inventory workflow: normalize Codex, Claude Code, Hermes, OpenCode, Cursor, MCP host, worktree, and wrapper session metadata into one drift-aware inventory. Use when the user says: harness-session-inventory, harness session inventory, session inventory, session adapter, session adapters, harness sessions, mcp inventory, mcp config inventory."
4metadata:
5 source: https://skillmd.com/skills/gabrielmoreira/omh-harness-session-inventory
6 hermes:
7 tags: [workflow, oh-my-hermes, observability]
8 category: observability
9 phase: harness-session-inventory
10 role: tracker
11 quality_tier: workflow-surface-gated
12---
13
14# Harness Session Inventory
15
16This is a Hermes-native `harness-session-inventory` workflow skill.
17
18## Why This Exists
19
20`harness-session-inventory` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration.
21
22## Do Not Use When
23
24- The request is already handled by a narrower explicit skill with stronger evidence.
25- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
26- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
27
28## Examples
29
30Good example:
31
32- Prompt: harness-session-inventory compare Codex, Claude Code, Hermes, MCP configs, and worktrees for drift before we dispatch agents.
33- Expected behavior: Produce `prepare_harness_session_inventory` with required context, wrapper actions, and not-evidence boundaries.
34- Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.
35
36Bad example:
37
38- Prompt: harness-session-inventory claim every MCP host loaded and every agent session is healthy from config files alone.
39- Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
40- Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.
41
42## Completion Checklist
43
44- The inventory scope names the harnesses, sessions, MCP hosts, connector configs, and worktrees being compared.
45- Prepared, observed, missing, stale, and drifted entries are separated before any health or progress claim.
46- The next action says whether to load a host, verify a connector, inspect a worktree, dispatch an executor, or stay blocked.
47
48## Recovery Notes
49
50- If config sources are unavailable, report only the discovered surfaces and mark the missing hosts not_observed.
51- If cleanup, host load, connector execution, or session progress is requested, route to the owning workflow instead of folding it into inventory.
52
53## Workflow Lane
54
55- Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `github-issue-intake`, `buzz`, `agent-board`, `+35 more`) - schedules, status, health, and ops review.
56- If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
57- Shared product, routing, compatibility, and evidence rules: `omh-routing/references/skill-common-rail.md`.
58
59## Use When
60
61Use when operators need a cross-harness/session/MCP/worktree inventory and drift summary before claiming any host loaded, connector ran, or agent session progressed.
62
63 Strong routing signals: `harness-session-inventory`, `harness session inventory`, `session inventory`, `session adapter`, `session adapters`, `harness sessions`, `mcp inventory`, `mcp config inventory`, `mcp drift`, `harness drift`, `connector drift`, `worktree inventory`, `worktree lifecycle`, `operator inventory`, `control pane inventory`, `codex session inventory`, `claude code session inventory`, `find previous coding session`, `recover coding session`, `previous codex coding session`, `coding session recall`, `세션 인벤토리`, `지난 코딩 세션`, `코딩 세션 복구`, `세션 기억 복구`, `하네스 세션`, `하네스 드리프트`, `MCP 인벤토리`, `MCP 설정 드리프트`, `워크트리 인벤토리`, `커넥터 드리프트`
64
65## Catalog Metadata
66
67Category: `observability`
68Phase: `harness-session-inventory`
69Hermes role: `tracker`
70Quality tier: `workflow-surface-gated`
71Reasoning demand: `standard`
72
73Quality bar:
74
75- Name the user-facing workflow objective, required context, next action, and stop condition.
76- Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.
77- Expose missing tools, credentials, targets, or observations as user-visible gaps.
78
79Handoff policy:
80
81Keep this as Hermes-facing orchestration guidance first. Prepare executor, connector, gateway, or host-runtime handoff only when the user accepts that next step and observed evidence can be recorded.
82
83Required inputs:
84
85- user request
86- target context
87- delivery or status expectation
88- known missing evidence
89
90Expected outputs:
91
92- harness_session_inventory/v1 card or guidance
93- harness_session_adapter_matrix/v1
94- mcp_inventory_drift_report/v1
95- worktree_lifecycle_snapshot/v1
96- session_progress_slots/v1
97- next action
98- prepared-vs-observed boundary
99
100Artifact expectations:
101
102- harness_session_inventory/v1 metadata-only runtime or wrapper card when recorded
103- harness_session_adapter_matrix/v1 with observed, prepared, missing, and stale adapters
104- mcp_inventory_drift_report/v1 with secret-redacted config/source drift only
105- worktree_lifecycle_snapshot/v1 with merge-conflict and cleanup candidates when observed
106
107Safety rules:
108
109- A harness session inventory is not host load, MCP tool-call, connector availability, executor dispatch, worktree cleanup, merge-conflict resolution, or session progress evidence.
110- Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.
111
112## Runtime Evidence
113
114Preferred harness for this skill: `harness-session-inventory`.
115
116```sh
117omh runtime record --skill harness-session-inventory --harness harness-session-inventory --status started
118```
119
120Record observed delegation results; otherwise return `not_available` or `not_observed`.
121Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
122- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
123Preserve workflow intent and stop conditions; verify before claiming completion.
124
125Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
126
127Shared product, compatibility, topology, memory, harness, and execution rules: `omh-routing/references/skill-common-rail.md`. Load it when applicable; otherwise name an unavailable capability.