Live data from Hacker News

Show HN: Agent Skills Leaderboard

skills.sh

41–47 of 47 posts

Re: Show HN: Agent Skills Leaderboard

#41

The install is very opaque. It's not clear where these skills are installed, how to upgrade them or remove them. Here's the `skills` package on NPM: https://www.npmjs.com/package/skills - it's MIT licensed but I can't find it on Github. `skills` looks to be a wrapper around `add-skill`: https://github.com/vercel-labs/add-skill From the docs, `add-skill` auto detects from 16 different potential paths to copy skills to…

Although it's not clear how to upgrade them (I doubt there is any version management built-in), the installer does specify where it will be installed (And lets you choose global/project level.

Re: Show HN: Agent Skills Leaderboard

#42

Earlier quoted context omitted.

;) 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

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.

I misunderstood your question, thought you were confused about a skill to enforce NPM usage by Claude to use NPM strictly as opposed to another package manager. Last time I post on HN past midnight.

Re: Show HN: Agent Skills Leaderboard

#43
post #16

Earlier quoted context omitted.

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

I can’t thank you enough for course correcting me here, this is exactly what I should have been doing. I did some reading and I clearly wasn’t using any of the features correctly or efficiently. My Claude.md was nearly 1,900 lines. It’s down to 150 lines now with Skills fully built out for the agents, and a hook to steer the ship. It’s all working perfectly now. Thank you again!

You are welcome. I have myself picked up this trick reading through Reditt and later polished that myself. No official guide is suggesting that

Re: Show HN: Agent Skills Leaderboard

#44
post #43

Earlier quoted context omitted.

I can’t thank you enough for course correcting me here, this is exactly what I should have been doing. I did some reading and I clearly wasn’t using any of the features correctly or efficiently. My Claude.md was nearly 1,900 lines. It’s down to 150 lines now with Skills fully built out for the agents, and a hook to steer the ship. It’s all working perfectly now. Thank you again!

You are welcome. I have myself picked up this trick reading through Reditt and later polished that myself. No official guide is suggesting that

Now that it’s set up it feels obvious, but I agree nowhere was this clear to me that this is how skills, hooks, and subagents were intended to be configured.

I was so much more productive today and used far less tokens. Thank you again!

Re: Show HN: Agent Skills Leaderboard

#45

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

Basically skills are /commands that can have attached scripts, that's about it.

If your "skill" doesn't come with scripts/executables, it's just a fancy slash command.

I've had success with code quality analysis skills that use PEP723 Python scripts with tree-sitter to actually analyse the code structure as an AST. The script output and switches are specifically optimised for LLM use, no extra fluff - just condensed content with the exact data needed.

Re: Show HN: Agent Skills Leaderboard

#46
At risk of piggybacking off someone elses post, my team just published noriskillsets.dev. It's maybe not as polished as this beautiful vercel site, but I think it solves a bigger problem: every skill in noriskillsets.dev is something that we've personally battle tested and evaluated as best in class for that particular task.

I love vercel, but I think the 'collect a bunch of random skills' approach just isn't it. You need versioning, linking between skills, an easy install client...basically a full package manager, which this is not.

If any of that is interesting, check out noriskillsets.dev. Would love to get feedback!

Re: Show HN: Agent Skills Leaderboard

#47
Cool! I built with https://enact.tools and can see several other competitors here.

I think this really has a future. Skills are going to be the way forward for portable ai tools. I think the skills standard needs to adapt to allow forward slashes so we can name things @vercel/somecategory/sometool. I've already brought it up in the agentskills GitHub.

posted last month: https://news.ycombinator.com/item?id=46435383

Post reply on HN