Show HN: Agent Skills Leaderboard
83 points by andrewqu 11 hours ago | 30 comments
  • straydusk 9 hours ago |
    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.

    • embedding-shape 9 hours ago |
      > How are skills ranked?

      By npm weekly installs (??). Famously good signal for quality.

      Edit: Not even npm, their own tools download count...

    • andrewqu 9 hours ago |
      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!

  • toledocavani 9 hours ago |
    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.
    • straydusk 9 hours ago |
      Assuming that's a response to me... that explanation would have been nice, and it's misleading without it.
  • laborcontract 9 hours ago |
    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

    • solumunus 2 hours ago |
      Not all flags will be relevant, you can trim down and contextualise the instructions for your specific project.
  • Johnny_Bonk 9 hours ago |
    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.

    • simple10 8 hours ago |
      Also this one is trending on HN.

      https://skillregistry.io/

      https://news.ycombinator.com/item?id=46692692

      • Johnny_Bonk 8 hours ago |
        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.
    • onurkanbkrc 2 hours ago |
      We had already done it before Vercel did.

      openskills.space

    • mrdonbrown an hour ago |
      If you want to share skills (and other tools) with teams at scale, consider sx - https://github.com/sleuth-io/sx

      [yup, my project :)]

  • amadeuswoo 9 hours ago |
    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

    • rudedogg 6 hours ago |
      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.

      • amadeuswoo 4 hours ago |
        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
        • SOLAR_FIELDS an hour ago |
          Yes, unfortunately the most reliable way is to inject them into the user prompt at a fresh session. My guess is that biasing towards checking for the tools availability too much affects performance, which might explain why it is quite rarer that I see it just choose to use a skill without previous prompting.
      • KingMob 4 hours ago |
        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.

    • NitpickLawyer 2 hours ago |
      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.
    • flwi an hour ago |
      Define "fundamental", but I added skills to run complicated evaluation procedures for my ML research. This way I can open 5 CC instances, let them run and iterate on research without intervention. After that, I can do the final review.
    • esperent an hour ago |
      > power-user stack

      Try installing the Claude Superpowers skills - you can install them one by one from here, but it's easier to install the superpowers plugin. Try using it for a couple of sessions and see how it works for you.

      For a full test, try starting with the brainstorming one which then guides you from brainstorming though planning, development etc.

      I've been using it for a few days and I would say it's enhanced my workflows at least.

  • arianvanp 8 hours ago |
    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

  • testfrequency 8 hours ago |
    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?

    • chewz 8 hours ago |
      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

  • thomasfromcdnjs 8 hours ago |
    Please make a rest API!
  • m-hodges 2 hours ago |
    Why do none of these “npm for Skills” document any way to do basic package management things like updates, version-pinning, or even uninstalls?
    • giancarlostoro an hour ago |
      ;) because you can ask Claude to do all of those things, but which package manager? there's a dozen ways to install packages, will Claude pick the right one you wanted? Your skill will guarantee consistency
      • m-hodges an hour ago |
        I don’t understand this reply at all. If I use this skills.sh tool to install the Foo Skill for one or more agent harness, how do I update Foo later?

        > but which package manager?

        The one being linked to.

  • joshribakoff an hour ago |
    This is a really good implementation, but I don’t lean too heavily into skills especially not other people‘s. If I’m doing design who’s to say I want instructions in there in the first place like “pick an extreme“ (instructions in the design skill featured on the homepage)
500 Internal Server Error

500 Internal Server Error