Publish a per-version release report for `eval/token_ceiling_formula.py` every time `FORMULA_VERSION` bumps — the exact configuration (formula, signal weights, calibration constants), a ranked gap list for the next contributor, and what's settled and not worth re-relitigating. Why this is its own skill rather than folding into `model-right-sizer-research-report`: every claim must interweave WHY it matters, in the same breath as WHAT changed — it stays decision-support only if a reader can tell, without a second file, what breaks (wasted spend, false alarms, undetected overruns, a re-biased fleet of budgets) if a number or gap is wrong. Never a new-finding surface — synthesizes only from committed results files. Also the tool for BACKFILLING a report for a past version that shipped before this skill existed. Use when someone says "write the release report for this version", "version the token ceiling formula", "backfill a release report for v0.x", or after any `FORMULA_VERSION` bump.
68
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Scanned
f539a8b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.