← All IntelClip / AI AgentsSkill distribution is still an unsolved problem
From Combine Skills and MCP to Close the Context Gap — Pedro Rodrigues, Supabase · ≈16:31
Honest postmortem on the skills ecosystem gap: no standard registry exists, Vercel's skills package and model-specific plugins compete, and Supabase's workaround is packaging skills inside each repo as .claude/.cursor plugins.
What’s in it
- Honest postmortem on the skills ecosystem gap: no standard registry exists, Vercel's skills package and model-specific plugins compete, and Supabase's workaround is packaging skills inside each repo as .claude/.cursor plugins.
Clip transcript
do you have some package manager? That's That's an amazing That's an amazing question because uh currently one of the downsides or the I would say the the constraints of using skills is their distribution distribution system, right? Uh we're still finding the there's still some players trying to reclaim uh the either the registry or the way to distribute it. So, Vercel came up with the skills package. Uh we're seeing plugins, right, that you can bundle with MCP servers and other things. Uh but they are model specific. So, this is to distribute in general, skills in general. It's already a a problem for itself that we haven't solved it yet. Um Internally, we have uh we are packaging the skills on the the repos themselves. So, if you want to uh create a plugin, you just uh create a dot Claude uh plugin or a dot cursor plugin or whatever in that repo, right? Uh and then it's available or or it's discoverable uh if the if the the repo it's it's open sourced or you have access to it, uh you can use the skills package to to fetch it. So, yeah, this and this is how I've seen the other uh companies distributing the skills like a repo, a skill, trying to package the the skills
Comments
Sign in to comment.
Loading comments…