Use it when the script looks rough
If the source already looks like it may have hot paths, repeated work, or cleanup issues, a read-only audit is often the smarter first move.
Use the optimizer or read-only audit first when the script looks heavy, messy, or likely to waste credits in a heavier lane. This page stays workflow-focused and does not reveal product internals.
If the source already looks like it may have hot paths, repeated work, or cleanup issues, a read-only audit is often the smarter first move.
Optimization guidance helps users avoid pushing a weak input into a heavier path too early.
Sometimes the goal is not stronger protection first. Sometimes the goal is to understand whether the script itself needs attention.
If the script is already straightforward and ready, users may not need a separate audit step before normal product usage.