If you check our Process for reviewing classic confinement snaps, the access to arbitrary files on the system isn’t typically a justification for classic. Strictly confined snaps can access users’ files with the home and the removable-media interfaces. personal-files and system-files may be used as well if needed. I have inspected skpr declaration and I see you have not plugged any interface yet. You can use snappy-debug to get suggestions/understand missing interfaces and denials. If you run into problems, post the snappy-debug output here along with your questions and we are happy to help.
I hope plugging some of the suggested interfaces support your platform use cases. This way you can keep your snap strict and enjoy all the benefits of a stable runtime environment. Please remember classic snaps are not installable on Ubuntu Core devices and also run in the global mount namespace, which means great care must be taken for the snap to work reliably across distributions.
This thread now appears to be requesting auto-connect of personal-files for skpr - can the title please be updated accordingly?
Also @kimpepper for consistency, could you please rename the personal-files instance to dot-skpr?
Finally, +1 from me for auto-connect of the dot-skpr personal-files instance providing read access to $HOME/.skpr for skpr from me - this is one of the primary purposes of the personal-files interface.