Although skins and containers are created, packaged, and deployed independently, it is very likely that you will create a skin and container combination which is intended to work together. Of course this can be accomplished by uploading both the skin and the container and then applying them to your portal user interface. To simplify this operation and provide a higher degree of granularity, a concept known as Pane Level skinning is also available.

Solution:

Pane level skinning can only be configured at design-time when the skin designer constructs the skin. It involves the use of some custom attributes which can be included in the markup for the pane. The ContainerType, ContainerName, and ContainerSrc attributes are used to identify a specific container to be used with all modules injected into the pane. In order for this to work correctly, the container must exist in the location specified otherwise the default container will be displayed.

In Skin.html or skin.ascx you can add attributes like shown below

ContainerType:
Container Type "G" = Host Container (i.e. stored in portals/_default)
Container Type "L" = Portal Container (i.e stored in portals/{portal ID})

ContainerName:
DNN creates a subfolder for each container because you can have multiple containers in that folder. For example, you could have a container called "MyContainer" and within it you could have "Standard.ascx", "Red.ascx", "Blue.ascx", "Green.ascx" etc.

ContainrSrc:
Container Source file which you may want to apply form your container folder.

Or

If your using [CONTENTPANE] Tockens for panes in skin.html

use this XML for Skin in your skin.xml