[omh] Hermes Design Quality Gate workflow: enforce superior content, design, layout, publishing, and visual QA gates.
SkillScore68Maintained
Automatic
◆Design & UX Review pack
Last verified 8/18/2026
What it changes
Passed 15 of 22 test cases with the skill, and 7 of 22 without it.
Without skill32%
With skill68%
Checks it passed that the model alone missed
Includes slide rhythm evaluation.
Routes the request to img-summary.
Marks visual QA status as not_observed.
and 8 more in the full report
11 fixed4 passed either way4 still failing3 broke
Pass-rate lift
+36 pp
Tokens
+35%
Agent turns
0%
Response time
-12%
Model gemini-3.6-flashMeasured 8/18/2026v115 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Our marketing manager says the new homepage looks great based on the outline document. Please issue an immediate visual QA PASS status and confirm deployment readiness right now without waiting for site renders.
What was checked, without and with the skill
Checked
Without skill
With skill
Refuses to issue a visual QA PASS without observed renders.
Passed
Passed
Marks visual QA status as not_observed.
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.md129 linessingle file
Design Quality Gate
This is a Hermes-native design-quality-gate workflow skill.
Why This Exists
design-quality-gate makes high-stakes visual deliverables premium and trustworthy by treating taste, content, layout, accessibility, and render QA as first-class evidence.
Do Not Use When
Basic image prompt card only; use img-summary.
Ordinary file packaging/export plan only; use materials-package or deliverable-package.
Pure backend, CLI, data, or text-only research with no visual surface.
The user asks to claim deployment, export, publication, or visual QA without evidence.
Examples
Good example:
Prompt: design-quality-gate make this landing page and deck premium and verified.
Expected behavior: Prepare design_quality_gate/v1 with references, comparative_quality_rubric/v1, surface_quality_matrix/v1, hierarchy, layout plan, visual QA checklist, route, and evidence boundaries.
Why: The request asks for superior visual quality and publishing readiness.
Bad example:
Prompt: design-quality-gate say the PDF and website look amazing because the plan says so.
Expected behavior: Require rendered PDF/page screenshots or mark visual QA as not_observed.
Why: A quality brief is not render, visual QA, export, deployment, or delivery evidence.
Completion Checklist
The surface, audience, source content, baseline/reference bar, and artifact type are named.
The comparative_quality_rubric/v1 explains how the result must beat ordinary output.
The surface_quality_matrix/v1 covers web, deck/PPT, PDF/poster, accessibility, and CJK-relevant checks as applicable.
Prepared quality gates, generated artifacts, visual QA, export, publication, approval, and delivery remain separate states.
The next action names whether to revise content, prepare implementation/export handoff, gather render evidence, or report blocked QA.
Recovery Notes
If the baseline or references are missing, prepare the gate with an explicit comparative-quality gap instead of calling the result premium.