To clarify what blumisb said about trigger names being case-sensitive: Trigger names are apparently case-sensitive. Putting an uppercase V on "Vigorous", as you seem to have done in almost every case, will prevent those lines from triggering.
Also, I got one of the "vige" lines when I shouldn't have. Upon checking, you have them marked as:
{"check":{"held":"true"}}
The in-game parser apparently doesn't even recognize this, but it does recognize:
{"held":"true"}
... Which is the format used in other lines that do seem to work properly, so there you go.
As for my own actual specialty, the writing is very well done in general, but I'm noticing a lot of doubled spaces. I've actually run into this before, it seems to stem from the action tags and the game automatically inserting a space if there isn't one immediately before the tag even if there's already one after the tag, so you'll want to plan around that. I also noticed a few other isolated errors, and it's just now occurring to me that I should've made a list instead of just correcting them as I spotted them. Oops. Though one I wasn't sure what to do with was the fact that the "imagine me as whoever you want" line seems to... well, I'm not even sure what happened at the end of it, it just sort of gets lost.
The forcefuloffer chain is suitably hardcore, but it seems... Well, I'm not sure how to explain it, but parts of it don't seem to mesh with certain other parameters. You may actually be able to work it out with a small branch or even just a few substitutions, I haven't really sat down and tried anything on for size yet. Hell, that might be a good idea anyway to add variety, and it could easily play off the variables you already have in place. I've actually been having a few ideas on that front, if you're interested.