A procedure you re-type from memory is a procedure you'll eventually get wrong.
There were multi-step routines I ran constantly, and every time I re-described them in prose — a little differently, a little worse. The fix was a skill: a saved, named procedure you trigger by name instead of re-explaining. The reliability comes from it being written once and frozen.
I tested turning one of those routines into a skill file — the steps, the inputs, the output format, locked — invoked by a single slash command.
The saved procedure. Same steps, same order, every time, no re-typing and no drift.
Trusting myself to re-describe a ten-step routine identically on the fortieth try. I never did.
If you've explained it twice, save it. A named skill beats a good memory.