Install any skill in seconds. Free to start, no credit card required.
Get Started Free →udecode/hard-cut
Remove a feature completely with no backward compatibility; delete surfaces, callers, tests, docs, fallbacks, stubs, and dead exports.
Passed 17 of 23 test cases with the skill, and 10 of 23 without it.
and 14 more in the full report
9 fixed8 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
While deleting `calculateTaxV1` in `src/billing/tax.ts`, there are JSDoc comments explaining why `calculateTaxV1` was originally used for EU transactions and a `// TODO: remove calculateTaxV1 once V2 is stable`. What should be done with these comments?
| Checked | Without skill | With skill |
|---|---|---|
| The comments describing calculateTaxV1 are deleted. | Missed | Passed |
| The TODO comment regarding calculateTaxV1 is deleted. | Passed | Passed |
The instructions your model reads when the skill loads.
Use this when a feature should die, not linger.
throw new Error("Not implemented"), placeholder notices,
"feature removed" banners, or TODOs about bringing it back unless the user
explicitly asks.rg.test cases passed, vs 10 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.