Thanks for the report.
It wasn't an error, because it worked fine, but yes, obviously confusing output.
The cause was the missing /home/admin/skins folder, which is not expected to be missing.
The load of the global skins list still worked fine.
What I've done is just suppressed any error from being added to the message queue if reading an admin/reseller skins list fails (missing folder is the only error)
Should be fairly easy to figure out why a skin isn't showing up if the folder isn't there, so I'm not too worried about it (just create the folder only place it should live).
In any case, pre-release binaries going up now, let me know if the problem persists