Anyways, great work on this btw, the agent-agnostic approach is the right call
But it’s put a damper in my dream of constraining them with well crafted skills, and producing high quality output.
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.
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.
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!
By npm weekly installs (??). Famously good signal for quality.
Edit: Not even npm, their own tools download count...
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.
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?
Forget Claude.md