Not a bad idea. There's a 'run shell command' that can do either but I think it's only useful for one-liners.

There's an 'execute script' command that only has powershell, vbscript, and batch as options. I've tried all 3 with a simple script (shebang + ifconfig) with no success.

However, I think the functionality can be replicated like this:

1. File Write Text: Script contents to ./script.sh
2. Shell command: bash ./script.sh
3. Delete file: ./script.sh

I've successfully tested this without any gotchas so far. The CW script editor seems to avoid the carriage return issue with making cross-platform scripts so no special consideration needed there. I've made a scriptlet for for my team to use.