@cloud0132 The main question is: Why do you want to do that, what problem do you want to solve?
If you really want to separately load some of your skeleton's animations, you could export the main skeleton once without the additional animations and just your base animations (to e.g. name.skel.bytes), and then export the identical skeleton with just the additional animations (to e.g. name-anims.skel.bytes). Then at runtime you could load the additional animations skeleton file on demand, and then append the additional skeleton's SkeletonData.Animations to your main SkeletonData.Animations.
In general, be sure to export your skeleton as binary (.skel.bytes file) instead of .json, as this brings the largest benefits in regards to file size and load time .
