Very handy indeed.... could be a nice feature  for 6.0 maybe?

About the name I don't really think its important what we call it at this point It actually works for both admin and edit like Sebastian says... lets call it an admin_edit view and everybody stays happy? :) 

It seems that the "edit" skin only applies when editing an individual module. I need an edit skin to apply when editing the page as a whole, and when I am on pages such as host or admin settings pages. There is a "Mode: View/Edit/Layout" setting at the top of the page. I need the edit skin to apply when in edit mode, and the view skin to apply when in view mode. What am I missing?

Beatriz, yes and no. Your answer was helpful, but my problem is not solved.

What I really need is a way to exclude all of the CSS for the ribbon menu on pages that do not have the ribbon menu (as well as other interface elements, but for the sake of simplicity, I'm just referring to one). It doesn't make sense to include all of the CSS for that stuff when it is not needed, and the rules in default.css are conflicting with the styles that I would like to use on the public-facing site. I understand how to use CSS Specificity and the Cascade, and I know the order of DNN's CSS (module>default>skin>skinfilename>container>containerfilename>portal>inline), so I can over-ride styles, but that adds hours to my development time as well as leaving me with inefficient and messy CSS, so I am trying to find a solution.