$npx -y skills add rlaope/oh-my-hermes --skill img-summary[omh] Hermes img-summary workflow: turn meetings, reports, PRs, issues, research, and releases into domain-aware image prompt cards.
| 1 | # Img Summary |
| 2 | |
| 3 | This is a Hermes-native `img-summary` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `img-summary` exists so Hermes can turn common communication work into provider-neutral image-card prompts while adapting format, domain mood, background, texture, lighting, camera, and poster grammar, and keeping generation, QA, and delivery as observed-only evidence. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user needs a deck, PDF, spreadsheet, HWP, Markdown package, or binary file export plan; use `materials-package`. |
| 12 | - The user wants a text-only report, leadership brief, or PPT-ready outline; use `report-package`. |
| 13 | - The user asks OMH to directly generate, inspect, upload, or post an image without a wrapper-supplied observed evidence path. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: img-summary make a PR summary card for reviewers. |
| 20 | - Expected behavior: Prepare visual_prompt_card/v1 with the PR review infographic format, copy mode, generation prompt, negative prompt, and not-evidence boundaries. |
| 21 | - Why: The request asks for an image-card communication artifact, not a PDF/deck package or hidden image generation. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: img-summary prove this generated card was posted to Slack. |
| 26 | - Expected behavior: Ask for visual_observation/v1 delivery evidence or report delivery as not_observed. |
| 27 | - Why: A prompt card cannot prove generated image, QA, or delivery evidence. |
| 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 prepare a source-specific visual or supplied-image edit prompt without claiming generation or transformation. |
| 55 | |
| 56 | Strong routing signals: `img-summary`, `img summary`, `visual prompt card`, `image card`, `image generation`, `image edit`, `edit this image`, `remove the background`, `background removal`, `이미지 편집`, `배경 제거`, `image generation features`, `image generation support`, `image tool support`, `image feature`, `image features`, `visual generation`, `visual generation support`, `visual card support`, `image summary card`, `summary image`, `summary card`, `explainer image`, `feature explainer image`, `feature explanation image`, `product explainer image`, `product explainer card`, `infographic`, `one-page infographic`, `workflow image`, `workflow card`, `shareable image`, `explain this as an image`, `make an image explaining`, `image explaining the cron feature`, `make an image explaining the cron feature`, `make a visual summary of this PR`, `visual summary`, `picture card`, `meeting notes picture card`, `vertical card`, `vertical summary image`, `vertical image card`, `meeting image`, `meeting summary image`, `conversation summary image`, `meeting notes image`, `pr card`, `pr summary card`, `pull request card`, `review card`, `issue card`, `bug triage card`, `feedback card`, `triage |