First, a lot of people in thread are saying you don't need skills. This is pretty wrong. There is a lot of alpha in using any set of skills that implements SPACE (search, plan, assert, code, evaluate). See: https://open.substack.com/pub/theahura/p/agentics-using-meta...
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
I'm building something similar with `Agents`[0] (think of it as a package manager for AGENTS.md snippets). I'm getting good results by including detailed instructions for certain tasks in the repo, and providing hints in AGENTS.md about when to use them. It's basically a simpler version of Skills—but it feels like AGENTS.md adherence is higher than Skill adherence.
for the most part skills are so portable that fiddling with moving them around is not that hard. The really hard thing is the 'is this skill worth the bits that its written with'. I'd say 99.99% of skills out there are so bad, you're actually worse off for installing them
standards are good though, we should make plugins for our skillsets so theyre easier for some folks
Definitely. Especially since those standards are fairly aligned across lots of tools. The other cool thing is a lot of desktop clients like Claude Cowork and ChatGPT Desktop also speak plugins, so hooking up marketplaces help with further distribution outside of technical teams.
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!
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)
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