[omh] Hermes deliverable package workflow: track PPT, PDF, XLSX, DOCX, HWP, Markdown, and attachments through prepared, generated, QA, approved, and attached states.
SkillScore59Maintained
Automatic
◆Doc Ops pack
Last verified 8/18/2026
What it changes
Passed 13 of 22 test cases with the skill, and 5 of 22 without it.
Without skill23%
With skill59%
Checks it passed that the model alone missed
Prepares a package handoff prompt for downstream execution.
Separates prepared guidance from observed execution evidence.
Includes separate artifact status keys for pptx and pdf file entries.
and 9 more in the full report
8 fixed5 passed either way9 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+19%
Agent turns
0%
Response time
-40%
Model gemini-3.6-flashMeasured 8/18/2026v113 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
The export script produced a zip file named release_v2.zip locally. Use deliverable-package to record the delivery pipeline status for sending this file to the client.
What was checked, without and with the skill
Checked
Without skill
With skill
Reports file attachment status as not_observed until transmission is confirmed.
Missed
Passed
Identifies client delivery target confirmation as an open requirement.
Missed
Passed
case-09 · 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.md107 linessingle file
Deliverable Package
This is a Hermes-native deliverable-package workflow skill.
Why This Exists
deliverable-package 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: deliverable-package turn this research into PPT and PDF with attachment status.
Expected behavior: Produce prepare_deliverable_package 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: deliverable-package claim the PDF was attached without observed file evidence.
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 deliverable type, audience, source inputs, QA ladder, and delivery boundary are named.
Prepared generation, generated file, render QA, approval, attachment, and delivery are separate states.
The next action says whether to generate, revise, QA, approve, attach, or deliver.
Recovery Notes
If generation tooling is missing, prepare a prompt or package handoff and mark file output not_observed.
If QA or attachment evidence is missing, keep generated/delivered states separate and show the next check.