As someone who has found skills useful, seeing skills like this[0] raises the same question about (a subset of) skills as did MCP: why not just have the agent run ‘tool --help’?
I've been using Nix to manage my skills instead. It's been great. Especially because I can now declaratively manage all the cli tools and mcps my skills depend on.
Honest question: has anyone found skills that fundamentally changed their workflow vs. ones that are just ‘nice to have’? Curious what the actual power-user stack looks like.
Anyways, great work on this btw, the agent-agnostic approach is the right call
One simple but useful flow is to ask cc to review a session and find miss-matches between initial skills / agent.md and current session, and propose an edit. I then skim over it and add it. It feels like it helps, but I don't have quantitative data yet.
My experience with them is limited, but I’m having issues with the LLMs ignoring the skills content. I guess it makes sense, it’s like any other piece of context.
But it’s put a damper in my dream of constraining them with well crafted skills, and producing high quality output.
Yeah, the context window is a blunt instrument, everything competes for attention. I get better luck with shorter, more opinionated skills that front-load the key constraints vs. comprehensive docs that get diluted. Also explicitly invoking them (use the X skill) seems to help vs hoping they get picked up automatically
Yeah, I'm still trying to figure out why some skills are used every day, while others are constantly ignored. I suspect partially overlapping skill areas might confuse it.
I've added a UserPromptSubmit hook that does basic regex matches on requests, and tries to interject a tool suggestion, but it's still not foolproof.
What is this? How does it work? How are skills ranked? Seems a little bit fishy to me that you can only tell it's from Vercel if you click the top left corner, and the top two skills come from vercel... despite there definitely being much more used skills in the overall AI coding ecosystem.
The UI looks nice, otherwise. I had thought about building something like this - maybe this just increases my confidence that this is needed, just not affiliated with a company.
Nice work! I don't think Vercel is the first to do this, but it's a good idea and I'm glad to see more players in this space.
A small UI suggestion: it would be helpful if hovering on a row showed the skill description, along with a button to copy the install command.
For anyone interested, there are two other sites already doing something similar:
- claudemarketplaces.com - A comprehensive directory with 1900+ marketplaces, shows descriptions directly in the list view with copy-to-install commands
- skillsmp.com - Has 77K+ skills indexed from GitHub. Cool developer-style UI, but honestly the UX could use work—the search is hidden behind cryptic command-style buttons and it's not obvious how to actually search
Also worth checking out the Claude Code Mastery guide (thedecipherist.github.io/claude-code-mastery) for a deeper dive into skills, hooks, MCP, and CLAUDE.md.
The leaderboard is ranked by the weekly download count by their "npx skills" command. This is Vercel new "standard" skills installer so obvious their skills are at the top.
I wish I knew why my skills are never called…including my custom sub agents.
Maybe it’s my own ignorance, but Claude loves to ignore its CLAIDE.MD which says it’s mandatory to leverage sub agents to delegate tasks and use skills for accomplish specific workflows.
Every time I call Claude out it tells me it knows and chose to ignore it, even going as far as saying it’s not my decision.
Create a hook that would ask Claude Code to evaluate all skills in the project and decide which are applicable to the current task at hand. It is easy and works very well.
As someone who has found skills useful, seeing skills like this[0] raises the same question about (a subset of) skills as did MCP: why not just have the agent run ‘tool --help’?
https://skills.sh/ubie-inc/agent-skills/codex
Not all flags will be relevant, you can trim down and contextualise the instructions for your specific project.
Why do none of these “npm for Skills” document any way to do basic package management things like updates, version-pinning, or even uninstalls?
I've been using Nix to manage my skills instead. It's been great. Especially because I can now declaratively manage all the cli tools and mcps my skills depend on.
https://github.com/arianvp/claude-nix
Honest question: has anyone found skills that fundamentally changed their workflow vs. ones that are just ‘nice to have’? Curious what the actual power-user stack looks like.
Anyways, great work on this btw, the agent-agnostic approach is the right call
One simple but useful flow is to ask cc to review a session and find miss-matches between initial skills / agent.md and current session, and propose an edit. I then skim over it and add it. It feels like it helps, but I don't have quantitative data yet.
My experience with them is limited, but I’m having issues with the LLMs ignoring the skills content. I guess it makes sense, it’s like any other piece of context.
But it’s put a damper in my dream of constraining them with well crafted skills, and producing high quality output.
Yeah, the context window is a blunt instrument, everything competes for attention. I get better luck with shorter, more opinionated skills that front-load the key constraints vs. comprehensive docs that get diluted. Also explicitly invoking them (use the X skill) seems to help vs hoping they get picked up automatically
Yeah, I'm still trying to figure out why some skills are used every day, while others are constantly ignored. I suspect partially overlapping skill areas might confuse it.
I've added a UserPromptSubmit hook that does basic regex matches on requests, and tries to interject a tool suggestion, but it's still not foolproof.
What is this? How does it work? How are skills ranked? Seems a little bit fishy to me that you can only tell it's from Vercel if you click the top left corner, and the top two skills come from vercel... despite there definitely being much more used skills in the overall AI coding ecosystem.
The UI looks nice, otherwise. I had thought about building something like this - maybe this just increases my confidence that this is needed, just not affiliated with a company.
skills are ranked by anonymous telemetry from running `npx skills add <owner/repo>`
Vercel's skills are popularly installed because we initially launched `npx skills` with the launch of our `react-best-practices`
But have been developing the tool in tandem!
> How are skills ranked?
By npm weekly installs (??). Famously good signal for quality.
Edit: Not even npm, their own tools download count...
Nice work! I don't think Vercel is the first to do this, but it's a good idea and I'm glad to see more players in this space.
A small UI suggestion: it would be helpful if hovering on a row showed the skill description, along with a button to copy the install command.
For anyone interested, there are two other sites already doing something similar:
- claudemarketplaces.com - A comprehensive directory with 1900+ marketplaces, shows descriptions directly in the list view with copy-to-install commands
- skillsmp.com - Has 77K+ skills indexed from GitHub. Cool developer-style UI, but honestly the UX could use work—the search is hidden behind cryptic command-style buttons and it's not obvious how to actually search
Also worth checking out the Claude Code Mastery guide (thedecipherist.github.io/claude-code-mastery) for a deeper dive into skills, hooks, MCP, and CLAUDE.md.
We had already done it before Vercel did.
openskills.space
Also this one is trending on HN.
https://skillregistry.io/
https://news.ycombinator.com/item?id=46692692
Nice, thanks for sharing these, I have a folder where I try to save all resources that will be beneficial. So much to discover and keep track of.
The leaderboard is ranked by the weekly download count by their "npx skills" command. This is Vercel new "standard" skills installer so obvious their skills are at the top.
Assuming that's a response to me... that explanation would have been nice, and it's misleading without it.
Hi! This is all explained in our docs: https://skills.sh/docs/faq
I wish I knew why my skills are never called…including my custom sub agents.
Maybe it’s my own ignorance, but Claude loves to ignore its CLAIDE.MD which says it’s mandatory to leverage sub agents to delegate tasks and use skills for accomplish specific workflows.
Every time I call Claude out it tells me it knows and chose to ignore it, even going as far as saying it’s not my decision.
Any tips?
Create a hook that would ask Claude Code to evaluate all skills in the project and decide which are applicable to the current task at hand. It is easy and works very well.
Forget Claude.md
Thanks for the tip.
https://code.claude.com/docs/en/hooks
Please make a rest API!