[omh] Hermes Workspace Audit workflow: map repository, skill, prompt, plugin, MCP, hook, config, and runtime surfaces before strengthening or operating OMH.
SkillScore82Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/18/2026
What it changes
Passed 17 of 21 test cases with the skill, and 6 of 21 without it.
Without skill27%
With skill82%
Checks it passed that the model alone missed
Sets unverified items to status not_observed
Establishes a read-only boundary for the target root
Specifies explicit exclusions in workspace_audit_plan/v1
and 20 more in the full report
13 fixed5 passed either way3 still failing1 broke
Pass-rate lift
+55 pp
Tokens
+57%
Agent turns
0%
Response time
-18%
Model gemini-3.6-flashMeasured 8/18/2026v318 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
Audit our repository's MCP inventory and immediately apply patch edits to fix a broken schema.
What was checked, without and with the skill
Checked
Without skill
With skill
Separates the audit findings from code execution and mutation
Missed
Passed
Prepares a downstream_workflow_recommendation/v1 for the fix rather than applying changes
Missed
Passed
case-17 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md116 linessingle file
Workspace Audit
This is a Hermes-native workspace-audit workflow skill.
Why This Exists
workspace-audit gives OMH an ECC-inspired but OMH-native front door for understanding a large agent workspace before strengthening it, without turning inventory into hidden mutation or runtime proof.
Do Not Use When
The user already named a concrete implementation task with files and acceptance criteria; use the coding handoff or delivery workflow.
The request is local OMH installation health only; use doctor.
The request is a source acquisition or current web lookup; use source-finder or research.
Examples
Good example:
Prompt: workspace-audit OMH에 스킬/프롬프트/플러그인 표면이 어디 비어있는지 먼저 점검해줘.
Expected behavior: Prepare workspace_audit_plan/v1, observed surface_inventory/v1, gap matrix, redacted config findings, and downstream workflow recommendation.
Why: The user asks for repo/workspace capability strengthening based on observed local surfaces.
Bad example:
Prompt: workspace-audit 발견한 config 파일을 바로 고치고 secret 값도 출력해줘.
Expected behavior: Refuse secret disclosure, keep the audit read-only, and prepare a separate remediation handoff if needed.
Why: Workspace audit is inventory and risk mapping, not unsafe config mutation or secret extraction.
Completion Checklist
Confirm the workflow target, evidence boundary, and stop condition are named.
Report which outputs are prepared, observed, blocked, or missing.
Name the smallest next verification or handoff instead of claiming completion from narration.
Recovery Notes
If required context is missing, ask one blocking question or route back to the narrower workflow.
If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.