Omh Materials Package

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.

Workflow Lane

• Current lane: Materials and visual summaries (design-orchestration, apple-design, design-quality-gate, award-bar-score, frontend, accessibility-audit, visual-qa, content-operator, +6 more) - web, accessibility, visual QA, files, and packages.
• 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 Hermes should turn source inputs into a material plan for decks, PDFs, Word/documents, spreadsheets, HWP, Markdown, office-file summaries, comparisons, table extraction plans, or binary export handoff without claiming file generation.

Strong routing signals: `materials-package`, `material package`, `materials package`, `document package`, `deck file`, `binary export`, `file export`, `render qa`, `layout qa`, `ppt and pdf`, `pdf and ppt`, `ppt/pdf`, `pdf/ppt`, `spreadsheet to pdf`, `excel to pdf`, `monthly report pdf`, `attached spreadsheet`, `word document`, `word doc`, `document action items`, `compare pdfs`, `pdf differences`, `extract tables from pdf`, `pdf to csv`, `spreadsheet analysis brief`, `clean analysis brief`, `pdf`, `pptx`, `keynote`, `keynote deck`, `docx`, `xlsx`, `csv report`, `spreadsheet`, `excel`, `hwp`, `korean hwp`, `proposal document`, `PDF`, `HWP`, `첨부한 엑셀`, `첨부한 워드`, `워드 문서`, `PDF 두 개 비교`, `PDF 표를 CSV`, `PDF 표 추출`, `분석 브리프`, `엑셀을 월간 보고서`, `자료 패키지`, `자료 처리`, `자료 생성`, `문서 패키지`, `문서 생성`, `제안서 문서`, `엑셀`, `스프레드시트`, `피디에프`, `한글 문서`, `키노트`, `파일 export`, `파일 생성`, `렌더 QA`, `PDF랑 PPT`, `PPT랑 PDF`, `PDF와 PPT`, `PPT와 PDF`, `PDF랑 PPT로`

Catalog Metadata

Category: materials Phase: material-plan Hermes role: operator Quality tier: material-gated Reasoning demand: standard

Quality bar:

• Name audience, source inputs, requested extraction/comparison task, target formats, outline sections, assumptions, missing inputs, and output owner.
• Attach format-specific QA expectations before preparing a binary-generation handoff.
• Record binary export, render QA, formula checks, approvals, and delivery only from observed evidence.

Handoff policy:

Keep source organization, outline planning, target-format selection, QA ladder, and missing-input review in Hermes; prepare an executor-neutral document-generation handoff only when a binary file is needed.

Required inputs:

• audience or recipient
• source inputs
• target format(s)
• deadline or delivery context
• missing data or assumptions

Expected outputs:

• material_artifact/v1 plan
• format-specific QA ladder
• executor-neutral generation handoff when needed
• observed export boundary

Artifact expectations:

• material_artifact/v1 under .omh/materials when a wrapper or CLI records it

Safety rules:

• Do not claim PPTX, PDF, Keynote, DOCX, XLSX, HWP, or upload output without observed file evidence.
• Do not claim render QA, formula recalculation, approval, or delivery from a prepared material plan.
• Keep source facts, assumptions, missing inputs, and generated output evidence separate.

Runtime Evidence

Preferred harness for this skill: materials-package.

omh runtime record --skill materials-package --harness materials-package --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.