31–40 of 47 posts
Why do none of these “npm for Skills” document any way to do basic package management things like updates, version-pinning, or even uninstalls?
Why do none of these “npm for Skills” document any way to do basic package management things like updates, version-pinning, or even uninstalls?
;) 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
> but which package manager?
The one being linked to.
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
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.
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 in a repository (.claude/, .codex/, .Gemini/, etc).
`add-skill` also let's you install skills globally (~/). From the code, `skills` looks like it doesn't support global installs but under the hood it passes all args to add-skill, so you should be able to install skills globally or install multiple skills (even if the wrapper doesn't expect it).
Aside: although lots of agents have adopted SKILLS.md conventions, they're currently all using their own paths. There doesn't seem to be a consensus yet, like there is with AGENTS.md. There are even 3 generic paths: .agent/skills/, .agents/skills/ and just skills/
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
I have a feeling that codex still does not do it reliably - so I still have normal README files which it loads quite intelligently and it works better than the discovery via skills.
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
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!
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…
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
https://zzbbyy.substack.com/p/what-are-skills
In my experience it doesn’t work too well with codex, but I expect llm providers to train them on that use case and improve the situation soon.
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…
¹ https://github.com/hodgesmr/agent-fecfile?tab=readme-ov-file...
Nice.
The page should properly advertize that this is a corporate built/sponsored site so people can understand that it's totally biased.