The important part is not the leaderboard. The important part is that skills can now be found, installed, and compared through a shared directory. Vercel's docs show npx skills add <owner/repo> as the install path and describe support across many agent tools.
That means a small open-source tool can show up where agents are looking, not just where humans search.
For a tool like AgentGuard, that is the right kind of distribution. A developer may not search for "AI agent budget limiter" until after the bill hurts. An agent working on a risky loop can be instructed to look for a budget-control skill before it ships the loop.
That is a better moment.
The packaging rule
Do not maintain three stories.
Keep one source. The package docs, SKILL.md, examples, and site copy should all say the same thing in different levels of detail.
The Python README explains the API. The skill explains agent behavior. The blog explains why the behavior matters. The product page gives the next step. The catalog is where all of them live.
That is enough.
For AgentGuard, the next step is still simple: install it, wrap the dangerous path, and prove the cap trips before production does.
Build it safely with AgentGuard: https://bmdpat.com/tools/agentguard
Originally published on bmdpat.com. I run a one-person AI agent company and write about what actually works.
Want these in your inbox? Subscribe to the newsletter - no spam, unsubscribe anytime.