one more screenshot showing the custom report in Skylien

found the solution :) just had to first export the custom report once to generate the .skyr file

Im collaborating with Stoyan on this issue and I found a fix for it. If I export the report (the custom made one it couldn't find) as a .skyr file, and then use the --report-add="path//to/skyr/file.skyr" together with the --report-conflict-resolution=overwrite in the command line, then it will use the custom report. Is this intended? dont mind the screenshot report being called skytest, its the same issue

Also: After running with the --report-add and conflict commands, i do not need to use these again, so it is as if the report template wasnt added properly through the GUI

The report definitions that Skyline knows about are saved in a "user.config" file somewhere under the AppData folder in the user's home directory.
The exact path to that user.config file depends on the executable that the process was started with.
When you use "SkylineRunner.exe", then "Skyline.exe" runs in its own process so it ends up using the same "user.config" file as when you run Skyline normally.
When you use "SkylineCmd.exe", there is only one process, so the "user.config" file that Skyline uses ends up having a different path than when you run Skyline in those other ways.
If you want to see what path that user.config file is in, you can run with the "--ui" command line argument:
SkylineCmd.exe --ui
This will bring up the Skyline user interface, and you can go the "Miscellaneous" tab at "Tools > Options" and see the full path to "user.config" file.

-- Nick

Thanks Nick