When the output slips twice in a row, you fix one thing. Not five. Test before, test after.
The output misses your standard twice in a row. Not once. Once can be the input. Twice is the skill.
Never rip the whole skill. Identify the single instruction or file that drifted. That is your target.
Capture the current "wrong" output. So you know what changed when you change it.
Edit the single instruction. Or add to the single knowledge file. Not three things at once.
Same input, new output. Did the change fix it? Did it break something else? You can only see this if you test the same way.
Date the change in the skill file. One-liner. Future you will thank current you when something else breaks in three weeks.
Read the whole skill before you touch anything. Run it once before you edit. Make one change at a time. Run it again with the same input. Commit each change separately so it can be rolled back.
Changing five things at once. Now you have no idea which fix worked, which broke something, or whether the next bug is new or old.
Continue with skill-creator. Step 7: iterate. The skill missed the output standard twice in a row. Help me find the single step or knowledge file that broke. 1. Capture the current "wrong" output for the same input. 2. Make one change — never more than one. 3. Re-run with the same input. 4. Compare. Did it fix? Did it break something else? 5. Stamp the version with today's date in SKILL.md.
Iteration is a discipline, not a vibe. Test before. One change. Test after. Stamp it. Skills that survive are skills that were edited carefully.