Finding
Visual work is weak when image generation, screenshot review, diagram QA, and vision analysis are treated as occasional tricks instead of a defined quality gate for visual artifacts.
Current
A real Hermes installation may use image tools when a user explicitly asks for a picture, screenshot interpretation, or visual check. The operational gap appears when visual outputs are produced or reviewed without a repeatable standard: diagrams can be plausible but unclear, screenshots can hide important UI states, and generated images can miss brand, accessibility, layout, or factual constraints. Tool mastery here means knowing when vision/image tools should be part of the workflow, not just knowing that they exist.
Suggested
- Add a visual QA gate for any public-facing visual artifact. Exact change: add a “Visual artifact QA” section to the content or dashboard runbook requiring image/vision review before publishing diagrams, screenshots, landing-page visuals, generated images, and workflow illustrations.
- Create a reusable image prompt and review pattern. Exact change: add a skill named
visual-artifact-qaor update the existing content-production skill with a checklist covering goal, audience, constraints, image prompt, generated output review, accessibility check, and final approval criteria. - Add screenshot evidence to UI and workflow verification. Exact change: update the relevant test or verification habit so dashboard, browser, and visual workflow changes include one screenshot review step: verify that the image shows the intended state, contains no sensitive data, and supports the written recommendation.
Impact
This improves the quality of visual artifacts without turning every task into design work. Vision tools catch mistakes that text-only review misses: unreadable diagrams, misleading screenshots, broken layout states, missing labels, or accidental exposure of private information. It also makes generated images more operationally useful because prompts and review criteria become part of the system, not an improvised side activity.
Effort
Small — the main work is adding one runbook gate, one reusable visual QA skill or checklist, and one screenshot verification habit for visual workflows.
Public page note
Safe public content includes the visual QA principle, generic examples of when to use image generation or vision review, and the maturity benefit of treating visuals as verifiable artifacts. Internal-only content includes actual private screenshots, user data visible in images, raw UI captures from authenticated systems, unpublished brand assets, credentials, logs, environment values, and any image that exposes operational details.