One of the reasons for the delay was to show how to do nice skin packages Thats a nice goal and good purpose.
If you read the project description for the nice TR skin you can read:
"The downloadable package here contains the DNNRadMenu skin object, in addition to the skin and container packages. This package allows you to install all the items with a single zip file." (a few other descriptions is wrong by the way)
In my opinion this is not so good to include a common skinobject in the skin package.
Why?
If you already have this skinobject installed you get a warning that tell you that this package is already instaled and you have to repair/overwrite the skinobject to get the skin installed. As the package is done you now will overwrite maybe a newer version of the skinobject.
In my opinion a dependency of the skinobject is a better choice.
OK you have to install first the skinobject and then the skin but in the long run this will make the installation better.
If the skin object is skin specific the method in the TR package is good practice but in this live example it is not.