Quite a while ago I had tried creating a zip file with a filename .sublime-package and it didn't seem to work with ST2. I just saw your message @guillermooo, so I will try out your code.
I do think that having every little command in its own package is a good thing. What would be useful is some way through ST2 to discover and select packages to install/update. I'm relatively new to python programming, so I don't know what the current best practice is, but something like sublime_easy_install would be awesome.
I like the suggestions about the repo names for packages being CamelCase, however for discoverability I've added the work "sublime" to each repository/package name. This github organization should help some. I've also considered setting up a website for plugins. Perhaps it could pull metadata from the github organization and present it in a nice search-engine-friendly way.
To potentially further complicate the situation, I've also been spending a lot of time on a package I intend to sell for a small fee. Right now I think I'd like to have a little more friction between someone just downloading it on Github and not ever paying, but I would like to keep with the ST model and allow for an extended trial period. Perhaps this is something I'll just need to work out on my own.