Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

omh-award-bar-score

[omh] Hermes award-bar score workflow: score a web surface against published design-award judging axes and name the binding constraint. Use when the user says: award-bar-score, award bar score, award winning, award-winning, award winning website, award-winning website, award winning design, award ready.

rlaope · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add rlaope/oh-my-hermes --skill omh-award-bar-score

About this skill


name: "omh-award-bar-score" description: "[omh] Hermes award-bar score workflow: score a web surface against published design-award judging axes and name the binding constraint. Use when the user says: award-bar-score, award bar score, award winning, award-winning, award winning website, award-winning website, award winning design, award ready." metadata: hermes: tags: [workflow, oh-my-hermes, materials] category: materials phase: award-bar-score role: operator quality_tier: design-orchestration-gated

Award Bar Score

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

Why This Exists

award-bar-score gives "make it award-winning" a measurable meaning: published axes, published weights, a published threshold, and the one axis holding the surface below it — instead of a taste argument nobody can settle.

Do Not Use When

  • The request is broad premium quality across decks, PDFs, or posters; use design-quality-gate.
  • The request is frontend implementation, layout, or design-system work; use frontend.
  • The request is WCAG, keyboard, or screen-reader conformance; use accessibility-audit.
  • The request is a rendered capture or a pixel verdict; use visual-qa.
  • The award is a business, sales, or team award with no judged web surface.

Examples

Good example:

  • Prompt: score our landing page against the css design awards bar and tell me what is holding it back
  • Expected behavior: Prepare award_bar_score/v1 with per-axis UI/UX/innovation scores from rendered evidence, the weighted total against the 8.0 threshold, the binding constraint, and the accessibility/performance tradeoff ledger.
  • Why: The request asks for a measured comparison against a published external bar, not a general polish pass.

Bad example:

  • Prompt: award-bar-score confirm this site will win website of the day
  • Expected behavior: Score the axes against the published model and refuse the outcome claim; a jury scores submissions and OMH does not.
  • Why: A rubric self-assessment cannot predict a jury result.

Completion Checklist

  • Each of UI, UX, and innovation carries its own score and the rendered evidence it was read from.
  • The weighted total is computed from the stated weights and compared against the published threshold.
  • The binding constraint names one axis and what moving it requires.
  • Any innovation move that costs accessibility or performance budget is recorded as a tradeoff the user chooses.
  • No award, jury, placement, or selection outcome is claimed.

Recovery Notes

  • If no rendered evidence exists, keep every axis not_observed and route the capture to visual-qa before scoring.
  • If the award body publishes no weights, score the axes separately and report the total as unweighted rather than inventing a ratio.

Use When

Use when a web surface must be judged against an external award bar: per-axis scores for UI, UX, and innovation, the weighted total against the published threshold, and the one axis holding the score down.

Strong routing signals: `award-bar-score`, `award bar score`, `award winning`, `award-winning`, `award winning website`, `award-winning website`, `award winning design`, `award ready`, `make it award winning`, `design award`, `design awards`, `css design awards`, `cssda`, `awwwards`, `site of the day`, `website of the day`, `wotd`, `score my site`, `어워드`, `디자인 어워드`, `어워드 수준`, `수상작 수준`, `수상 가능한 디자인`, `어워드 받을만한`, `올해의 사이트`

Catalog Metadata

Category: materials Phase: award-bar-score Quality tier: design-orchestration-gated Reasoning demand: standard

Quality bar:

  • Score each axis separately with named rendered evidence, then compute the weighted total; an overall impression is not a score and hides which axis is failing.
  • Reserve binding-constraint language for a total within about 0.3 of the threshold. Measured axis spread is roughly a twentieth of site spread, so further below the bar a weak axis is a symptom: report that the site needs a level change, never a one-axis fix.
  • Load references/award-judging-model.md for the published axes, weights, and thresholds, the measured per-axis score table, and the stack table that separates entry-fee craft (fluid type, real typography) from optional spend (WebGL).
  • Record what an innovation move costs on the accessibility and performance budgets before recommending it; half the sampled motion-heavy winners drop prefers-reduced-motion, and the two highest-scoring entries keep it, so never present the inaccessible path as the higher-scoring one.

Required inputs:

  • the target URL, route, or rendered capture being judged
  • the award model and its published axes, weights, and threshold
  • the surface's own accessibility and performance budgets
  • audience and primary user task

Expected outputs:

  • award_bar_score/v1
  • per-axis scores with named evidence for UI, UX, and innovation
  • the weighted total and its distance from the published threshold
  • the binding constraint: the axis whose gain moves the total most
  • tradeoff_ledger/v1 when an innovation move costs accessibility or performance budget
  • downstream route: frontend, accessibility-audit, visual-qa, or design-quality-gate

Artifact expectations:

  • award_bar_score/v1 with prepared_not_observed status
  • every axis score cites the rendered evidence it was read from, or stays not_observed
  • the weighted total is arithmetic over the stated weights, never an impression
  • no claim that a submission would win, place, or be selected

Safety rules:

  • A self-assessment against a published rubric is never an award, a jury outcome, or a prediction of one; juries score submissions, and OMH does not.
  • Never score an axis without rendered evidence; an unrendered page keeps every axis not_observed.
  • Quote axis weights and thresholds only from the award body's published rules, and name the body and the date they were read.
  • Accessibili
Read the complete source ↗