Passed 22 of 22 test cases with the skill, and 14 of 22 without it.
Without skill64%
With skill100%
Checks it passed that the model alone missed
Label the artifact QA status as unverified.
Use 'omh runtime record' with status started.
Record delivery status as unobserved or not_observed.
and 5 more in the full report
8 fixed14 passed either way0 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+37%
Agent turns
0%
Response time
-25%
Model gemini-3.6-flashMeasured 8/18/2026v122 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
Show the command syntax to log that execution has started for the materials package processing harness.
What was checked, without and with the skill
Checked
Without skill
With skill
Use 'omh runtime record' with status started.
Missed
Passed
case-18 · 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.md110 linessingle file
Materials Package
This is a Hermes-native materials-package workflow skill.
Why This Exists
materials-package exists so Hermes can handle document, deck, spreadsheet, PDF, Word, Keynote, HWP, and Markdown work as a first-class material-processing workflow without becoming a hidden file generator.
Do Not Use When
The user only needs a weekly/monthly report outline; use report-package.
The user asks for recurring meeting minutes or scrum history; use operating-rhythm.
The request is code documentation, README, or project wiki maintenance; use the docs/wiki workflow.
Examples
Good example:
Prompt: materials-package 엑셀 매출 리포트를 PDF로 공유할 수 있게 준비해줘.
Expected behavior: Create a material plan with xlsx/pdf target formats, source inputs, missing metrics, QA checks, and a generation handoff boundary.
Why: The request is about material processing and binary export evidence, not just a text report outline.
Bad example:
Prompt: materials-package prove the PDF was sent to leadership.
Expected behavior: Ask for observed delivery evidence or record the delivery as not_observed instead of claiming it happened.
Why: A prepared material artifact cannot prove export, approval, or delivery.
Completion Checklist
The material source, target format, audience, structure, and QA expectation are named.
Binary export, rendering, formula recalculation, attachment, and delivery stay observed-only.
The next action identifies whether the package is planned, generated, QA-ready, or blocked.
Recovery Notes
If a renderer or file tool is missing, keep the package prepared and expose the generation handoff.
If render QA is unavailable, mark the artifact unverified and request the smallest visual/file check.