Skip to content

rlaope/oh-my-hermes / skills/omh-deliverable-package

omh-deliverable-package

Verified

[omh] Attachment and deliverable status tracking: track PPT, PDF, XLSX, DOCX, HWP, Markdown, and attachments through prepared, generated, QA, approved, attached, archived, and published states. Use when the user says: deliverable-package, deliverable mode, file attachment, attach file, attachment status, file delivery, file deliverable status, generated file.

Deliverable Package

This is a Hermes-native deliverable-package workflow skill.

Why This Exists

deliverable-package exists because a requested file moves through prepared, generated, QA-checked, approved, and attached states that no single tool reports together: it tracks each file through them and reports a state only from that state's own evidence, never from an earlier one's.

Do Not Use When

  • Planning a deck, PDF, workbook, or document from source inputs before any file exists (its outline, target formats, and QA ladder); use omh-materials-package.
  • A text-only report, executive brief, or slide outline with no file to produce; use omh-report-package.

Examples

Good example:

  • Prompt: deliverable-package the deck and PDF are generated; check they were rendered, get my approval of v2, and tell me whether the PDF was attached to the thread.
  • 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 tell the client the PDF is attached.
  • 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 rendered images do not match slide_count or remain uninspected, retain the observed slide_count, mark render_screenshot unresolved, and hand back the exact file and outstanding image checks.
  • If the person's approval names no final file, retain each generated version's read-back, mark approval unresolved, and hand back the stable id and version choices without selecting by modification time.
  • If a publication URL resolves to a different content hash, retain the approved file and any archive evidence already read back, mark publication unresolved, and hand back the URL and expected sha256 for destination read-back.

Workflow Lane

  • Current lane: Materials and visual summaries - web, accessibility, visual QA, files, and packages.
  • If intent belongs to another lane, hand back to omh-routing or name the adjacent workflow.
  • Shared product, routing, compatibility, and evidence rules: skill_view(name='omh-routing', file_path='references/skill-common-rail.md').

When to Use

Use when Hermes should prepare, request generation, QA, and report attachment status for user-visible file deliverables.

Strong routing signals: `deliverable-package`, `deliverable mode`, `file attachment`, `attach file`, `attachment status`, `file delivery`, `file deliverable status`, `generated file`, `첨부`, `첨부 상태`, `전달 상태`

Catalog Metadata

Category: deliverables Phase: package-status Hermes role: operator Quality tier: workflow-surface-gated Reasoning demand: standard

Quality bar:

  • Name the user-facing workflow objective, required context, next action, and stop condition.
  • Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.
  • Expose missing tools, credentials, targets, or observations as user-visible gaps.
  • On Hermes, a rung taken from a bundled document skill is observed only from that skill's result for that exact file, judged by its field, not its exit code: "rendered": false or "recalculated": false exits 0 yet leaves that rung not observed, blocked on the missing tools it names; other observed evidence for a rung still counts.
  • On Hermes, the bundled document skills give these rungs when available (powerpoint, xlsx, docx; microsoft-office from v0.22.6; same scripts): PowerPoint gives slide_count (pptx_read.py --outline) and render_screenshot (pptx_render.py into a fresh directory, its image count matching slide_count, since it lists every image already in that directory); pdf gives page_count (pdf_read.py --meta) and render_preview (pdf_page_image.py); Excel gives sheet_schema (xlsx_read.py --sheets) and formula_recalculation (xlsx_recalc.py --out <copy>, since without --out it replaces the input and rungs or approvals already recorded were for other bytes, then the cached results read back with xlsx_read.py --formulas, where an error value or a formula with no cached value is a finding); Word gives section_structure and required_clause_check (docx_read.py --structure and --text) but no page_count or appearance until a converted PDF is rendered, and docx_validate.py checks package health, never rendering. Images that exist are not a render pass until each one has been inspected, and a producer's "ok": true is never the QA verdict.
  • A file is generated only from the producer's read-back of the written file, approved only from the person's answer, and attached only from the destination's own read-back, never from a reply that names the file.
  • archived only after the archive entry records the content sha256, the version, a poster frame or thumbnail for media, and a catalog row read back from the archive.
  • published only from the destination's own read-back - a URL resolving to the same content hash - never from an upload command's exit code.
  • Never pick the final file by modification time: the person's approval names it.
  • One work keeps one stable id, and each revision is a new version under it - never a new id and never an overwrite.

Handoff policy:

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.

Required inputs:

  • user request
  • target context
  • delivery or status expectation
  • known missing evidence

Expected outputs:

  • deliverable-package/v1 card or guidance
  • next action
  • prepared-vs-observed boundary

Artifact expectations:

  • deliverable-package/v1 metadata-only runtime or wrapper card when recorded

Safety rules:

  • A deliverable package card is not binary generation, render QA, formula recalculation, approval, upload, attachment, or delivery evidence.
  • Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.

Runtime Evidence

Preferred harness for this skill: deliverable-package.

omh runtime record --skill deliverable-package --harness deliverable-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. Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only. When the requested output is delivered, put any open points inside the result and end with no question or offer; only when the person asked to choose or decide and that choice is still theirs, end with one specific question about it, not a list, a generic offer, or a footer; the shared rail's Reply Language And Host Voice and Turn Ending sections hold the full rule.

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: skill_view(name='omh-routing', file_path='references/skill-common-rail.md'). Load it when applicable; otherwise name an unavailable capability.

finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall