materials-package
starsforks
How to install materials-package?
rlaope/oh-my-hermes/materials-package
$npx -y skills add rlaope/oh-my-hermes --skill materials-package[omh] Hermes Materials Package workflow: decks, PDFs, spreadsheets, documents, HWP, Markdown, and binary export handoffs.
SKILL.md
| 1 | # Materials Package |
| 2 | |
| 3 | This is a Hermes-native `materials-package` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user only needs a weekly/monthly report outline; use `report-package`. |
| 12 | - The user asks for recurring meeting minutes or scrum history; use `operating-rhythm`. |
| 13 | - The request is code documentation, README, or project wiki maintenance; use the docs/wiki workflow. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: materials-package 엑셀 매출 리포트를 PDF로 공유할 수 있게 준비해줘. |
| 20 | - Expected behavior: Create a material plan with xlsx/pdf target formats, source inputs, missing metrics, QA checks, and a generation handoff boundary. |
| 21 | - Why: The request is about material processing and binary export evidence, not just a text report outline. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: materials-package prove the PDF was sent to leadership. |
| 26 | - Expected behavior: Ask for observed delivery evidence or record the delivery as not_observed instead of claiming it happened. |
| 27 | - Why: A prepared material artifact cannot prove export, approval, or delivery. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - The material source, target format, audience, structure, and QA expectation are named. |
| 32 | - Binary export, rendering, formula recalculation, attachment, and delivery stay observed-only. |
| 33 | - The next action identifies whether the package is planned, generated, QA-ready, or blocked. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If a renderer or file tool is missing, keep the package prepared and expose the generation handoff. |
| 38 | - If render QA is unavailable, mark the artifact unverified and request the smallest visual/file check. |
| 39 | |
| 40 | ## OMH Context Rail |
| 41 | |
| 42 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 43 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 44 | - Current lane: **Materials and visual summaries** (`design-orchestration`, `design-quality-gate`, `frontend`, `accessibility-audit`, `visual-qa`, `content-operator`, `media-input-operator`, `materials-package`, `+3 more`) - web, accessibility, visual QA, files, and packages. |
| 45 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 46 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 47 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 48 | - Coverage: Every generated workflow skill carries this rail. |
| 49 | - Normal users talk to Hermes; OMH CLI is infra. |
| 50 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 51 | |
| 52 | ## Use When |
| 53 | |
| 54 | 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. |
| 55 | |
| 56 | 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 두 개 비교`, `PDF 표를 CSV`, `PDF 표 추출`, `분석 브리프`, `엑셀을 월간 보고서`, `pdf`, `pptx`, `keynote`, `keynote deck`, `docx`, `xlsx`, `csv report`, `spreadsheet`, `excel`, `hwp`, `korean hwp`, `proposal document`, `자료 패키지`, `자료 처리`, `자료 생성`, `문서 패키지`, `문서 생성`, `제안서 문서`, `엑셀`, `스프레드시트`, `피디에프`, `PDF`, `한글 문서`, `HWP`, `키노트`, `파일 export`, `파일 생성`, `렌더 QA`, `PDF랑 PPT`, `PPT랑 PDF`, `PDF와 PPT`, `PPT와 PDF`, `PDF랑 PPT로` |
| 57 | |
| 58 | ## Catalog Metadata |
| 59 | |
| 60 | Category: `materials` |
| 61 | Phase: `material-plan` |
| 62 | Hermes role: `operator` |
| 63 | Quality tier: `material-gated` |
| 64 | |
| 65 | Quality bar: |
| 66 | |
| 67 | - Name audience, source inputs, requested extraction/comparison task, target formats, outline sections, assumptions, missing inputs, and output owner. |
| 68 | - Attac |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
