Usually TKLBAM downloads the profile you ask for (e.g., --force-profile=core) from the Hub.
However in --solo mode, it isn't connecting to the Hub so it can't download a prebuilt profile with a matching name. You have to either use the "empty" profile or create your own custom profile:
tklbam-internal create-profile --help
What is a backup profile?
A backup profile is used to calculate the list of system changes that need to
be backed up (e.g., new files and packages). It typically describes the
installation state of the system and includes 3 files:
* dirindex.conf: list of filesystem paths to scan for changes
* dirindex: index of timestamps, ownership and permissions for dirindex.conf paths
* packages: list of currently installed packages.
snip...
Read the documentation for details and experiment a bit until you understand how it works.
You can get a good starting point for your custom profile's configuration from the profile source on GitHub. I suggest customizing the 'core' profile configuration.
Note, regarding your question some of the profile configurations for GitHub are empty because they don't need to make any changes relative to 'Core'. There's an inheritance model.
--solo doesn't work with profile names
However in --solo mode, it isn't connecting to the Hub so it can't download a prebuilt profile with a matching name. You have to either use the "empty" profile or create your own custom profile:
Read the documentation for details and experiment a bit until you understand how it works.You can get a good starting point for your custom profile's configuration from the profile source on GitHub. I suggest customizing the 'core' profile configuration.
Note, regarding your question some of the profile configurations for GitHub are empty because they don't need to make any changes relative to 'Core'. There's an inheritance model.