Below is a quick summary of what you have to consider to pass them successfully
Technique (/10)
This relates to what type of loops you have used where, how you found that certain object on the floor, how you detected that door, how you made sure your script was fail safe. It also refers to issues such as whether you should have used DTMs / DDTMs / bitmaps there or not, how you have found an ore/tree/etc., and if you could have done this any better
Individuality (/10)
This refers to whether your scripting style is your own or not. The more individual your script is, the better it is for you, because this means you really understand what all of the different procedures / functions / types / methods should be used for. it means you are relying less on other people, and are developing your own style.
Use of SRL (/10)
This relates to how well you have used the SRL include. Are you creating custom functions that are already in SRL, or are you using the existing ones in the include. Also, are you using them correctly? There is no point in creating something which is already in the include. Basically this shows how well you have looked through the include before resorting to making it yourself, and it shows your understanding of the include as well.
Efficiency (/10)
The more efficient the script is, the better it is. Why constantly write out procedures when you can use a simple repeat instead? Are you using "end else" when needed? Do you have duplicate functions? Are you freeing DTMs / bitmaps after finishing with them? The more efficient your script is, the better it will run, and the easier errors will be to fix when they arise. No more than 300 lines.
Meeting Requirements (/10)
How did the script run when we tested it? Did it do what it was asked for? Any problems? As simple as that.
Credit: The Great 'StarBlaster100'