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 omh-design-quality-gate.
• The request is frontend implementation, layout, or design-system work; use omh-frontend.
• The request is WCAG, keyboard, or screen-reader conformance; use omh-accessibility-audit.
• The request is a rendered capture or a pixel verdict; use omh-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