We made the score punish unsourced numbers

Skills on SupaSkills carry numbers — thresholds, rates, benchmarks. Until this week the SupaScore didn't care where those numbers came from. A skill that said "keep CPI above 0.90" scored the same whether that 0.90 was sourced or invented on the spot.

We ran our own catalog against three model families and found the invented ones everywhere. Confident numbers with nothing behind them. The score had been rewarding them, because more numbers looked like more substance.

Now unsourced numbers cost points. Every number a skill can't back pulls the score down.

Some skills dropped. The ones that leaned hardest on invented precision dropped the most, and a chunk of them now show a "being re-sourced" tag. They still work, they're still live — they sit in a queue to have every number checked against a source. Nothing got deleted.

A score that only goes up looks better on a landing page. This one went down. We'll take the honest number.

Next: we work through the queue, worst first. Re-sourcing a number means backing it with a source, or saying plainly it's a rule of thumb you calibrate yourself. It does not mean stripping numbers out — a skill with no numbers is useless.

How the score works: /methodology

— Max