Hmmm, if you have to be in charge of exporting the skeletons from Spine in that situation, it may be a good idea to use the default settings as much as possible except for the required settings for the spine-unity runtime such as changing the file extension of the atlas file to .atlas.txt and the binary format file extension to .skel.bytes. If you are using the default settings in Spine except for the file extensions, and have not changed any settings on the Unity side, you should basically be able to import your skeleton without any problems.
Also, it would be good to automate exporting your project files so that you can easily re-export your skeletons to modify the settings if you are asked to do it later. For example, you can see a script we use to export all the Spine example projects here:
https://github.com/EsotericSoftware/spine-runtimes/blob/4.1/examples/export/export.sh
Personally, I use Automator which is a standard macOS application to create automated export applications. If you need additional advice on automation, please do not hesitate to ask.
FYI, we will release a video introducing common import issues in the near future, and we hope that you will watch it, and it will be helpful to you on how to properly handle the issue if you receive a complaint that your skeleton is not importing or working properly.
