11–20 of 47 posts
Anyways, great work on this btw, the agent-agnostic approach is the right call
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+ marke…
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?
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+ marke…
Also this one is trending on HN. https://skillregistry.io/ https://news.ycombinator.com/item?id=46692692
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?
Forget Claude.md
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
But it’s put a damper in my dream of constraining them with well crafted skills, and producing high quality output.
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
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.
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
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.
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.