All you really need are the function definitions, which give you no insight into the mechanics of how a given skill works, in order to write code for CF. As an example, below is a quick reverse engineer of what the code for "jab" looks like on CF. If I had the real function definitions, I could make something that was valid CF code, without ever having access to the rest of the code. Depending on implementation, that's probably just a copy of merc.h, which usually includes (most) of the function defs and some constants.

I can't put the code directly in, apparently, so you'll have to view the attached file...

http://forums.carrionfields.com/dc/user_files/120.txt

Attachment #1, (txt file)