You made a mistake adding those sprites into a family!
They may be added to a container, but not to a family!
These two features have completely different meaning, but many people confuse them..
You should add objects to a container when they should be logically linked together (when they all combined make one big complex object). PlayerBox+PlayerSkin+PlayerAttackAnimation+PlayerWearable+PlayerHealthBar=make one Player
All these sprites refer to one player, so you can add them to a container. This will make lots of things easier - picking, creating/deleting instances etc.
Also, containers make sense when you have many instances of these objects. For example you add 4x instances of PlayerBox to the layout, and the system will create PlayerSkin+PlayerAttackAnimation+PlayerWearable+PlayerHealthBar for each of the 4 players automatically.
If you only have one instance of each of these sprites, there is no point to add them to a container.
.
Families are different. You add objects that have similar features to a family. For example you can add all different monsters to one family Enemies. Or all different controls in your game into a family Buttons. This allows you to create universal events, for example: On Buttons tap -> Play "Click" sound