This skin is my first time ever using js so please point out anything that's wrong.
-pigeonlips
You may find strong opinions about JavaScript

As I understand it, JavaScript didn't get much time for design and polish before it got shipped and this shows. There are many oddities / warts in the language and sadly often trying to do things in a way that seems to make sense can backfire -- particularly if one has expectations about the language coming from a C / C++ (or similar) background.
If you intend to continue with the language, I highly recommend checking out some of Douglas Crockford's material early on, perhaps starting with:
Crockford on JavaScriptEven if one doesn't agree with some or much of what he says, I've found his material well worth the time.
He suggests an approach to the language based on being quite selective in what to use in the language and staying away from certain bits (e.g. he suggests not using == or != and instead using === and !==). I have found this helps tremendously for JavaScript (and even AHK) but it isn't necessarily the easiest thing to figure out or get used to.
To help in this process, there is a tool Crockford developed and maintains called jslint (and now at least one fork called jshint). I used jslint while doing JavaScript (via FScript) plugin development for FARR and found it to be really helpful. Haven't set it up for Qatapult yet, but based on working with the OpenWith plugin, getting the feeling it may be a good idea.
After writing the above, I remembered that there is now this thing called CoffeeScript. It compiles to JavaScript and although it has its problems, seems a far nicer language to be writing in. It's pretty easy to get it set up once one has Node.js installed. May be I'll see how practical it would be to use for Qatapult-related things.
Any interest?