It superficially reminds me of the old "Alexa Skills" thing (I'm not even sure if Alexa still has "Skills"). It might just be the name making that connection for me.
Claude Skills
21–30 of 443 posts
Re: Claude Skills
#22It superficially reminds me of the old "Alexa Skills" thing (I'm not even sure if Alexa still has "Skills"). It might just be the name making that connection for me.
Re: Claude Skills
#23Re: Claude Skills
#24Interesting. For Claude Code, this seems to have generous overlap with existing practice of having markdown "guides" listed for access in the CLAUDE.md. Maybe skills can simply make managing such guides more organized and declarative.
I have been using claude code to create some and organize them but they can have diminishing return.
Re: Claude Skills
#25Re: Claude Skills
#26Can someone explain the differences between this and Agents in Claude Code? Logically they seem similar. From my perspective it seems like Skills are more well-defined in their behavior and function?
Skills can merge together like lego.
Agents might be more separated.
Re: Claude Skills
#27Seems like a more organized way to do the equivalent of a folder full of md files + instructing the LLM to ls that folder and read the ones it needs
Re: Claude Skills
#28getting hard to keep up with skills, plugins, marketplaces, connectors, add-ons, yada yada
Re: Claude Skills
#29It superficially reminds me of the old "Alexa Skills" thing (I'm not even sure if Alexa still has "Skills"). It might just be the name making that connection for me.
This is where waiting for this stuff to stablize/standardize, and then writing a "skill" based on an actual RFC or standard protocol makes more sense, IMO. I've been burned too many times building vendor-locked chatbot extensions.
Re: Claude Skills
#30We used to call that a programming language. Here, they are presumably repeatable instructions how to generate stolen code or stolen procedures so users have to think even less or not at all.