Skip to content

rlaope/oh-my-hermes / .claude/agent-skills/omh-deliverable-package

omh-deliverable-package

Verified

[omh] Attachment and deliverable status tracking: track PPT, PDF…

Deliverable Package

This is an OMH deliverable-package workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

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.

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 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.

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

Use the current host's own tools and subagent/task mechanism when available; otherwise run the same lanes sequentially or name the unavailable capability. A prepared plan, handoff, checklist, or skill installation is not execution, review, CI, merge-readiness, or merge evidence. Record actual tool results, or not_observed / not_available, in the record; never invent dispatch or host accounting. Treat supplied context as advisory, not proof of hidden memory reads or writes. State scope, constraints, verification, and the stop condition before work. Reply in the user's own words and the host's own voice: the host's 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; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a real unresolved user decision or a useful briefing discussion remains, offer one specific, content-linked question. Completed work needs no question; omit unrelated non-action footers and generic offers to continue. Supporting paths are relative to this skill directory; sibling skill paths are relative to its parent. Resolve them from the host-provided skill base directory ({baseDir} on hosts that provide it), never a hardcoded install location. A named workflow not installed here is unavailable, not permission to emulate its host-specific capabilities. Verify through the real surface before done.

canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall