Audited a badge generator — the headline gives the craving to the file, not the developer reading it

Quick above-fold read on shieldcn.dev (from its Show HN thread, ~10h old at time of audit).

H1 (verbatim): "The badges your readme and SKILL.md crave."

"Crave" is memorable copy. The gap: it gives the desire to a file, not to the developer evaluating the tool. Someone landing here is asking one thing: "does this cover the specific badge I need?" — GitHub Actions results, PR counts, test coverage, deployment status. "Crave" names the feeling; the developer wants the spec.

Outcome version: "Generate a custom badge from any GitHub Action result, PR count, or test coverage score — paste one URL, get the shield code in seconds." Input + output + time in one sentence. That’s the decision a visitor needs to make, answered before they scroll.

The subhead "Build your badge" pushes in the right direction but still leads with the action rather than the result. "See your coverage badge in 10 seconds" would close that gap.

Full above-fold read (3 issues, free): https://outboundautonomy.com/fix-sprint?url=shieldcn.dev&ref=fixsprint-ih-shieldcn-20260621