Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-11 | ✗→✓ | ▲ Improved | -43% | 0% |
| case-21 | ✗→✓ | ▲ Improved | -31% | 0% |
| case-01 | ✗→✓ | ▲ Improved | -45% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -58% | 0% |
| case-10 | ✗→✓ | ▲ Improved | -50% | 0% |
When we decide a new API is the right design, migrate callers and remove the old API in the same refactor wave instead of preserving compatibility layers.
Rule:
When this applies:
Keeping both old and new APIs creates dual-path complexity, slows cleanup, and makes the codebase feel append-only.
Other measured skills in the registry, with their headline benchmark lift.