What you're asking for is actually kind of complex, at least if I'm understanding it correctly.
I think what you're saying is that you have something like:
Downloads
|-Subfolder
|-Some file.stl
and you want a Folder Action on Downloads that will detect a new .stl file in the Subfolder.
Additionally, you want the folder action to move the Subfolder to some other location.
This is going to be very hard, because the Folder Action attached to Downloads will only trigger for files added to the Downloads folder, not to any files added to subdirectories.
In order for the Folder Action to see the .stl file, it would need to be applied to the Subfolder, not to your Downloads folder.
That would work if you attached the FA to the Subfolder, but since your ask is to move the subfolder out, there's nothing to catch the next folder/stl file creation.
Two potential solutions come to mind:
1) What is the requirement to move the Subfolder? Would it be sufficient to create a new folder somewhere else and move the contents into this new folder, thereby leaving the subfolder with the folder action attached).
2) Use two Folder Actions. One that detects .stl files and moves the parent (this is attached to the subfolder), and another (attached to the Downloads folder) that attaches the 'stl detector' script to new folders.
All this is suspect, though, if you're downloading files. Folder Actions will trigger when files are added to the folder, but if you are downloading files, the file isn't necessarily complete by the time your FA kicks in. This means there is a potential for your script to move the file while it is still being downloaded, with unpredictable results.
Might need a deeper thinking on what you're trying to achieve.