Have you ever had this kind of problem :
You have got a page design with quite obscure menus from a web designer that you have to implement on a DNN system. You end up creating menu inside skin (without using any dynamic menus) and loose a lot of the base functionality of a CMS. On the other hand as the site administrators need menus to access Admin and Host -sections of the site, a some sort of menu has to be placed somewhere - I usually put it into some subpage as a module that has only access by site administrators.
Problem is that as good as the default SolPartMenu and others available at the moment are, they can't do everything. This problem bothers me every now and then and my solution would be that since with new profile provider each profile has an GUID -string, would it be possible to enable in skin.xml a permissions -section under each skinobject -section so that you could define roles that have access to view some skinobjects in some skins and vice versa. With this one could get a fixed menu visible with the option to show inside the same skin a dynamic menu with admin and host menus in case user has identified itself as an administrator.
This could work in other skinobjects than menu as well. If you want to enable search, logo, banners etc. depending on who is accessing your site, you could do this on skin level (i.e. subscribe to some role to see some banners and other roles see other banners or don't see banners at all).
So, visibility setting based on user's role in skin would be first step and maybe next one would be defining the content itself depending on user's role - like, show different kind of logo/menu/etc based on page accessing user role would be great.
Limitless possibilities :D