First, you should read this:
To summarise it for you, I will say that you have not completed all the steps of using a SlackBuild.
A SlackBuild package from Slackbuilds.org (the SBo
of the "sbotools" name) contains only the scripts to *build* a software, NOT the software itself.
To get the software you want to install, you should either go to its SlackBuilds.org page (in this case: https://slackbuilds.org/repository/1...search=sbotool
) and follow the URL under the Source Downloads:
section, or do this:
$ cat /home/chuck/sbotools/sbotools.info | grep DOWNLOAD
and download the result.
Verify that you downloaded what you think you downloaded by comparing its checksum:
$ md5sum /home/chuck/sbotools/sbotools-X.Y.tar.gz
Place this downloaded file in the same directory as the other files that are members of the SlackBuild package, and run the SlackBuild script.
$ chmod +x /home/chuck/sbotools/sbotools.SlackBuild
$ su -c '/home/chuck/sbotools/sbotools.SlackBuild'
Once that is finished, you will find a freshly built installable package in your /tmp folder. Install it with 'installpkg':
$ su -c 'installpkg /tmp/sbotools*SBo*t?z'
This is how SlackBuilds work.
Honestly, you might want to give yourself some time to learn that system in its purest form (the form I just described here) before you let yourself graduate to a tool that does it all for you. That's just my opinion, of course, but you earn more Slack
if you learn the technology before you learn the frontends.