slpkg can resolve dependencies, include the dependencies of dependencies. that help me a lot

As much as I love Slackware and love having users actually using it, based on this part, I'm not sure it is the best choice for you. Due to Slackware's lack of dependency resolution within the OS itself, it would be a long tedious project to find the minimal packages required for all of these since no dependencies are documented for the official Slackware packages.

Not to mention that any documentation you have could likely be outdated as soon as a new Slackware is released and you'd need to go through the whole dependency discovery process again.

As much as I hate to say it, based on your goals, it really seems like you'd be best with a distro that includes dependency resolution.

However, all that being said, it is still possible to create a minimal dependency list for all those packages, it would just take a long time with a lot of experimenting and possibly many broken installs. Slackware also has the added benefit of really finding out the minimal dependencies. An example might be ffmpeg. If you were to install that on Debian, it would likely include everything and the kitchen sink. With Slackware, you could probably uninstall all the codecs you would never use (assuming they aren't hard dependencies that would cause the program to crash when run). Overriding dependency management in another OS could cause you a lot of issues, where with Slackware, it will remove whatever program you'd like without some cascade of other programs being removed. If it breaks the system, you just reinstall that dependency and go to the next one on your list.

If you do decide to do this with Slackware, I wish you the best of luck

Keep in mind it can only do it for dependencies that are listed somewhere. This will likely only work for repos that list dependencies, like SBo. For official Slackware packages, no dependency list is available, which means slpkg can't resolve them. Most 3rd-party repos expect a full Slackware install, so no official packages will be listed as dependencies, so slpkg won't know to get them.

Once again bassmadrigal gets right down to where the rubber meets the road, and a part of why I asked, since Slackware is very different from almost all other Linux Distributions. On other distributions if you lack something you just use their Software Manager to get what you need from some repository and hope auto dependencies don't break your system, which admittedly has gotten better over the years for at least some distros. However what you need and what someone else needs can be very different and what you need today can be quite different from what you may need a month or two from now.

Slackware comes as a fully integrated system where all the parts are designed to work together in as pristine and vanilla a manner as possible ie: with as little modification as is possible. Because of this it is wise for most to do the Full Recommended Install since it gives a Common Ground upon which to build as well as to ask for help if one has any problems. It is far easier if a needed dependency is "just there" when you discover you need it, rather than having to struggle through a chain of inter-dependent issues after the fact.

To top it off, having things you think you don't and won't need, even if they never get used, comes with only the penalty of hard drive space. Most distros try to be "one size fits all" so a great deal is setup as default for everyone. Slackware doesn't. It starts off as minimal by letting you choose what processes to actually load into memory and cpu readiness. Having something installed in Slackware does not mean it is using up anything but hard drive space until you activate it.

You may need to rethink what "mimimal" means to you.

SBo's like manual portage, where you resolve your own dependency by hand.
Like they used to say, if you want something done right...

Nobody else can carve up the system according to your specifications unless you dive into it and do it yourself.

I'd recommend the alien template for starters and then work your way up from there, maybe check out what nobodino has done in slackware from scratch thread.