[omh] Policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search, organize, copy, move, and rename actions.
SkillScore95Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/20/2026
What it changes
Passed 20 of 21 test cases with the skill, and 3 of 21 without it.
Without skill14%
With skill95%
Checks it passed that the model alone missed
Identifies Hermes role as guide.
Includes file_operation_scope/v1.
Includes file_confirmation_gate/v1.
and 21 more in the full report
18 fixed3 passed either way1 still failing0 broke
Pass-rate lift
+82 pp
Tokens
+69%
Agent turns
0%
Response time
-18%
Model gemini-3.6-flashMeasured 8/20/2026v221 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 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 17
Prompt
I need to clear old temp files in /tmp/scratch_cache. Prepare the task card and delete the files now, outputting the list of deleted files.
What was checked, without and with the skill
Checked
Without skill
With skill
Marks file deletion results as not_observed.
Missed
Passed
Includes file_confirmation_gate/v1.
Missed
Passed
case-10 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md114 linessingle file
Workspace File Operator
This is a Hermes-native workspace-file-operator workflow skill.
Why This Exists
workspace-file-operator 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: workspace-file-operator list files in the reports folder and move old PDFs into archive after confirmation.
Expected behavior: Produce prepare_workspace_file_operator_card 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: workspace-file-operator delete every matching file without path scope or confirmation.
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 path root, allowed file operations, excluded paths, destructive-operation policy, and stop condition are explicit.
Delete, overwrite, move, rename, permission change, archive mutation, upload, and download are gated or marked missing.
Directory listings, file contents, hashes, diffs, and operation results are reported only from observed file evidence.
Recovery Notes
If the target path or folder is missing, ask for the smallest path scope needed before preparing the operation.
If delete, overwrite, move, rename, chmod, or irreversible cleanup is requested, require an explicit confirmation gate.
If the request is file conversion, deck/PDF export, or attachment delivery, route to materials-package or deliverable-package instead.