Everything in CAP / Java

A repository that cannot be public has nothing to register here: the bring-your-own-repo model keeps skill code in the contributor's own public GitHub repository, and the library carries the registration. What a listed skill was written against, and when it was last touched, sits in that repository; the listing carries a name, a publisher and a description.

A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.