I'd really like to see how this does with nontrivial examples. I'm happy to be proven wrong, but I bet the bash one isn't that effective for real world sysadmin tasks, since most bash things also require knowledge of the commands in-between the actual bash "glue", and usually requires regexes and pipelines to get the exact answer you want. Pretty much every time I look up a bash command (probably from the same sources this model trains on) I have to tweak it to do what I need.

For example, here are some things I pulled from `.bash_history`, and what I think I was meaning to do.

    # Get the IP address of running lxc container ${CONTAINER_NAME}
    CONTAINER_NAME=some-container; lxc-ls -f | grep ${CONTAINER_NAME} | awk '{print $5}' | sed -z 's|-.*\s||g;'

    # Find the latest git tag version, excluding release candidates and development builds
    git describe --tags `git rev-list --tags --exclude=*-rc* --max-count=100` | grep -vP '(\-rc|dev)' | head -1

    # get the database name from parameters.yml
    grep 'database_name:' parameters.yml | sed 's|.*:||g; s|\s||g;'

I bet #3 would would be feasible, but I'd be extremely surprised if it could get close on the first two.

PowerShell has the advantage of a really consistent standard library, syntax, objects, and has the .NET type system behind it, so any answer is probably already in the format you want or requires minimal manipulation. I can see it working much better there, and that's also probably why the example video only shows PowerShell too. Granted, I am probably the opposite of the target audience.

All that being said, would you really trust running some random commands you don't understand enough to write, because some remote server told you to? It should tell you the commands first rather than just executing them.