the original version of our high autonomy skillset was a fork of obra's superpowers back in...October? November? of last year. Whenever it first came out.
I think basically all of the best skillsets implement SPACE, including superpowers, mattpocock skills, get shit done, etc. There are aesthetic reasons why you might prefer one over the other, but candidly I think any of them will get the job done and are strictly better than not using one of the SPACE skillsets.
(I haven't played with the latest version of superpowers. My hunch is that on average our skillsets have better compliance rates with the models because of some of the ways in which we write the skills themselves, but its a hunch)
standards are good though, we should make plugins for our skillsets so theyre easier for some folks
FWIW I work on AI enablement in my day job for both our build org and the broader company and we’ve found success with using marketplaces for distribution.
I also built a free tool that diffs a lot of agent configs to help me keep current on changes.
Here’s the main page, but you can checkout the marketplace and plugin entries if you’re interested!
Second, we share all of our sets of skills in a purpose built registry: https://noriskillsets.dev/ you can use any of our public skillsets from there. If you're on a team you can also sign up to get your own private registry. Makes organization much easier.
Finally, for local development, we use this CLI to manage skills (https://github.com/tilework-tech/nori-skillsets). This is a tool that lets you bundle skills into groups, and then switch between those groups. So for eg if I'm making a slide deck I'll use an admin skillset, and for coding I'll use a swe skillset, and for debugging I'll use a debugging skillset.
We do keep tinkering with our skillsets, but not very much. I don't get the need to adjust things for every model release, doesn't seem necessary for us in practice