This is a dumb one, but I told it to refer to PowerShell as "StupidShell" and told it not to write it as "StupidShell (Powershell)" but just as "StupidShell". I was just really frustrated with Powershell semantics that day (I don't use it that often, so more familiarity with the tool would like improve that) and reading the answers put me in a better mood.
I made a custom GPT that was explicitly told to include snark, sarcasm, and dark humor in all of my IT related responses or code comments, it makes my day every time.
Sure thing!
I often use it to add code comments to my powershell scripts after I've written them, sprinkling in quotes from some of my favorite movies from the 80s like Spaceballs, Princess Bride, Airplane, etc...
"User '$username' found. Preparing to eject them from the AD universe."
"Failed to import Active Directory module. Inconceivable!"
"Failed to delete user '$username'. I am serious, and don't call me Shirley."
Other times I will ask it questions related to scripting commandlets and it often responds in a tone that is more fun to read at least.
"Firstly, ensure you're connected to the mystical realm of Exchange Online. If you're scratching your head wondering how, refer back to the ancient scrolls on how to establish a connection. It involves Get-Credential, New-PSSession, and a bit of patience."
Not either of them but I use Power-hell in my daily job to automate a lot of active directory related things, I can also confirm it can piss you off and has quite a few 'isms or gotchas. The way some things handle single and double quotes can drive you literally insane.
