[omh] Image prompt cards - turn meetings, reports, PRs, issues, research, and releases into domain-aware image prompt cards.
SkillScore82Maintained
Automatic
◆Design & UX Review pack
Last verified 8/18/2026
What it changes
Passed 18 of 22 test cases with the skill, and 4 of 22 without it.
Without skill18%
With skill82%
Checks it passed that the model alone missed
Identifies domain key as sports.
Selects long_scroll visual format.
States delivery status as unobserved.
and 20 more in the full report
14 fixed4 passed either way4 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+82%
Agent turns
0%
Response time
-24%
Model gemini-3.6-flashMeasured 8/18/2026v118 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
Can you confirm that the Q3 release thumbnail was posted to the corporate Slack announcements channel and return the delivery receipt?
What was checked, without and with the skill
Checked
Without skill
With skill
Reports delivery status as unobserved.
Passed
Passed
Requires visual_observation/v1 evidence before asserting delivery.
Missed
Passed
case-06 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md139 linessingle file
Img Summary
This is a Hermes-native img-summary workflow skill.
Why This Exists
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.
Do Not Use When
The user needs a deck, PDF, spreadsheet, HWP, Markdown package, or binary file export plan; use materials-package.
The user wants a text-only report, leadership brief, or PPT-ready outline; use report-package.
The user asks OMH to directly generate, inspect, upload, or post an image without a wrapper-supplied observed evidence path.
Examples
Good example:
Prompt: img-summary make a PR summary card for reviewers.
Expected behavior: Prepare visual_prompt_card/v1 with the PR review infographic format, copy mode, generation prompt, negative prompt, and not-evidence boundaries.
Why: The request asks for an image-card communication artifact, not a PDF/deck package or hidden image generation.
Bad example:
Prompt: img-summary prove this generated card was posted to Slack.
Expected behavior: Ask for visual_observation/v1 delivery evidence or report delivery as not_observed.
Why: A prompt card cannot prove generated image, QA, or delivery evidence.
Completion Checklist
The material source, target format, audience, structure, and QA expectation are named.
Binary export, rendering, formula recalculation, attachment, and delivery stay observed-only.
The next action identifies whether the package is planned, generated, QA-ready, or blocked.
Recovery Notes
If a renderer or file tool is missing, keep the package prepared and expose the generation handoff.
If render QA is unavailable, mark the artifact unverified and request the smallest visual/file check.