1. Choose the right page
Use Skid Proof for the public lane, Sentinal Labs for premium coverage and post-processing, and Lua Optimizer for read-only performance guidance.
2. Prepare the script
Start with cleaner source when possible. If the script looks rough, performance-heavy, or parser-hostile, use pre-scan first.
3. Run the main tool
Use the lane or preset that fits the job. Review the output and warnings before you spend more credits or open follow-up tools.
4. Open extra tools only when needed
XLR and XQR are optional workflow steps. Not every run should automatically move into that path.
The cleanest credit-saving habit is using the simpler page or the read-only scan first whenever there is a real question about script quality.