TLDR: check out noriskillsets.dev.

Our company ethos is “build the things that make us faster at building the things that make us faster.” This is a necessary part of any startup, of course. But we take this to extremes. When LLMs failed to adapt to larger codebases, we built the first versions of nori-skillsets to get to the point where agents were writing all of the code at our company. When Claude Code failed to build out critical features like built in notifications and SessionEnd output, we built on top of it to let us run >10 agents at once. And when our agent CLIs began to lag behind, we built our own CLI tool in rust so that we could keep pace with our own throughput. We don’t wait for the industry to catch up. We don’t have time for that. AI is moving too fast for that.

A few days ago, I complained that the industry and the ecosystem needs a trusted package manager

Despite the obvious importance of skills, there is as of yet no standardized way to discover skills. For example, if you search for ‘creating-skills/SKILL.md’, you will find 76 different versions of a skill for creating skills. To try and find good skills, people have taken to producing massive lists of dozens of otherwise-unrelated skills on github. It’s giving very Web 0.1. The problem, of course, is that you also can’t find those lists! There are 53 different repositories called ‘awesome claude skills’!
Most of these skills are bad. A huge huge chunk of them are written by AI without any guidance. These are possibly the worst, because AI tools do not yet know how to write good skills…
As far as I can tell, there is basically 0 understanding of what makes a good skill. So what proliferates in the market is slop, and search indices for that slop. It happens to me all the time. I will see a skill that I think is cool, try it out, and realize that it doesn’t work. Or that it actively makes my agent worse. And then I either scrap it, or spend the time rewriting the whole thing from scratch…There is a need for an AI npm or pypi, a package manager that is an ecosystem backbone, one that does a good job surfacing the best tools instead of simply indexing all of them without care for quality.

More succinctly, the ecosystem needs a place where developers can:

Quickly and easily get the latest configuration options and tooling for their agents;
Make it easy to onboard their teams to agentic coding best practices;

Avoid the slop on GitHub;
Not have to spend hours and hours becoming experts in these tools before being able to get value from them.

We heard this from our own customers over and over again. “My team won’t adopt coding agents because they had a terrible first impression and don’t have the time to learn the difference between a skill, a subagent, a slash command, and an agent.md.” I don’t blame those engineers! If I wasn’t already in AI, I wouldn’t touch this ecosystem with a ten foot pole.

Well, we build the things that make us faster. And a package manager that we can use to share configs within our team definitely makes us faster. We built an initial version of this thing a month ago and have been using it in house ever since.

After my post on Sunday, we realized no one was coming to save the wider ecosystem. So we’ll do it. We’re bringing the things that make us faster to the public so everyone can use them.

I’m very excited to announce noriskillsets.dev.

The goal of noriskillsets.dev is to provide a curated and off-the-shelf package manager for the AI ecosystem. You can:

Create skillsets (collections of skills)1 that have the tools and configs you need
Easily switch between skillsets
Source the best versions of skills and other tools, as vetted by the Nori team
Get internal/private registries to easily version control and share configs with your team.

Some people like to brag that they’ve indexed thousands of skills. Not us. Right now, we have ~33.

If you’re just getting started with agentic coding, noriskillsets.dev will help you become a master. If you’re trying to get your team to use coding agents, noriskillsets.dev will make your settings portable and save your engineers hours of configuration time. And if you’re trying to stay abreast of the fire hose, don’t worry — noriskillsets.dev will keep you up to date on the latest and greatest.

The ease and simplicity of NPM with the quality guarantees of the Apple App Store.

Try it out, let us know what you think. And if you have skills or configs that you want to share, or if there’s something out there that you know works that we’re not aware of, send it our way.

PS. Eng team of 3, 28 PRs landed in the last 24 hours. Our skillsets have us moving so fast.

See also:

Hacker News Announcement

usenori.ai mainpage

What is a Skillset

1

It’s crazy to me that the concept of a skillset isn’t more widespread. Skills work best in context. They need to be able to reference each other, reference subagents, be referenced by the CLAUDE.md, etc. etc. This is such an obvious and natural thing, and it’s been vital to our velocity.

12 Grams of Carbon

Fuck it, we’ll build our own AI package…