deliverable-package
starsforks
How to install deliverable-package?
rlaope/oh-my-hermes/deliverable-package
$npx -y skills add rlaope/oh-my-hermes --skill deliverable-package[omh] Hermes deliverable package workflow: track PPT, PDF, XLSX, DOCX, HWP, Markdown, and attachments through prepared, generated, QA, approved, and attached states.
SKILL.md
| 1 | # Deliverable Package |
| 2 | |
| 3 | This is a Hermes-native `deliverable-package` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is already handled by a narrower explicit skill with stronger evidence. |
| 12 | - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. |
| 13 | - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: deliverable-package turn this research into PPT and PDF with attachment status. |
| 20 | - Expected behavior: Produce `prepare_deliverable_package` with required context, wrapper actions, and not-evidence boundaries. |
| 21 | - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: deliverable-package claim the PDF was attached without observed file evidence. |
| 26 | - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. |
| 27 | - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - The deliverable type, audience, source inputs, QA ladder, and delivery boundary are named. |
| 32 | - Prepared generation, generated file, render QA, approval, attachment, and delivery are separate states. |
| 33 | - The next action says whether to generate, revise, QA, approve, attach, or deliver. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If generation tooling is missing, prepare a prompt or package handoff and mark file output not_observed. |
| 38 | - If QA or attachment evidence is missing, keep generated/delivered states separate and show the next 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 prepare, request generation, QA, and report attachment status for user-visible file deliverables. |
| 55 | |
| 56 | Strong routing signals: `deliverable-package`, `deliverable mode`, `file attachment`, `attach file`, `attachment status`, `file delivery`, `file deliverable status`, `generated file`, `자료`, `첨부`, `첨부 상태`, `전달 상태` |
| 57 | |
| 58 | ## Catalog Metadata |
| 59 | |
| 60 | Category: `deliverables` |
| 61 | Phase: `package-status` |
| 62 | Hermes role: `operator` |
| 63 | Quality tier: `workflow-surface-gated` |
| 64 | |
| 65 | Quality bar: |
| 66 | |
| 67 | - Name the user-facing workflow objective, required context, next action, and stop condition. |
| 68 | - Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence. |
| 69 | - Expose missing tools, credentials, targets, or observations as user-visible gaps. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | Keep this as Hermes-facing orchestration guidance first. Prepare executor, connector, gateway, or host-runtime handoff only when the user accepts that next step and observed evidence can be recorded. |
| 74 | |
| 75 | Required inputs: |
| 76 | |
| 77 | - user request |
| 78 | - target context |
| 79 | - delivery or status expectation |
| 80 | - known missing evidence |
| 81 | |
| 82 | Expected outputs: |
| 83 | |
| 84 | - deliverable-package/v1 card or guidance |
| 85 | - next action |
| 86 | - prepared-vs-observed boundary |
| 87 | |
| 88 | Artifact expectations: |
| 89 | |
| 90 | - deliverable-package/v1 metadata-only runtime or wrapper card when recorded |
| 91 | |
| 92 | Safety rules: |
| 93 | |
| 94 | - A deliverable package car |
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
