The Verified Badge Doesn't Predict Quality — and That's Fine
We put a green "verified" badge on 98% of the directory. That should tell you something about the badge, not the skills.
| Group | Skills | Average score |
|---|---|---|
| Verified | 577 | 8.53 |
| Unverified | 14 | 8.21 |
A 0.32-point gap — below our evaluator's own variance. The badge does not predict quality.
What it actually means
On this site, "verified" means one specific thing: the skill's package was inspected and its source repository was confirmed. It is a provenance check, not a quality judgment.
When 98% of entries carry it, the badge has stopped being a discriminator and become a baseline. That is the right design — provenance should be the default, not an achievement — but it is not what a reader sees. A green check reads as endorsement.
The 14 that don't have it
They are the exceptions: recently imported entries whose source could not be confirmed at import time, or whose package failed a structural check. Several are pending re-review. Their slightly lower average is not evidence that unverified skills are worse; it is evidence that the unverified set is small and selected by a technical condition.
Why this matters beyond our site
Every directory invents badges, and every badge starts as a signal and ends as decoration. The mechanism is the same each time:
- The badge is introduced for a real reason.
- Coverage expands until most entries have it.
- Readers keep reading it as a differentiator long after it stopped differentiating.
- If you are reading a directory: check what a badge is awarded for before you weight it. "Verified" often means "we have the file", not "we checked the work".
- If you are building one: reserve badges for properties that are actually rare. A badge on 98% of entries is a label, not a signal.
- Instead of the badge, read the rationale. Every skill page here carries the written reasoning behind its score. That is a slower read and a much better one.
The fix is to keep the badge meaningful by keeping it scarce, or to rename it so it says what it does. We did neither at the start, and the data is now pointing that out.