Interesting. 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.
Claude Skills
11–20 of 443 posts
Re: Claude Skills
#12The idea is interesting and something I shall consider for our platform as well.
Re: Claude Skills
#13Re: Claude Skills
#14"Equipping agents for the real world with Agent Skills" https://www.anthropic.com/engineering/equipping-agents-for-t...
Re: Claude Skills
#15You get the best of both worlds if you can select tokens by problem rather than by folder.
The key question is how effective this will be with tool calling.
Re: Claude Skills
#16Re: Claude Skills
#17Specifically, it looks like skills are a different structure than mcp, but overlap in what they provide? Skills seem to be just markdown file & then scripts (instead of prompts & tool calls defined in MCP?).
Question I have is why would I use one over the other?
Re: Claude Skills
#18getting hard to keep up with skills, plugins, marketplaces, connectors, add-ons, yada yada
Of course this is why the model providers keep shipping new ones; without them their product is a commodity.
Re: Claude Skills
#19Re: Claude Skills
#20http://github.com/ryancnelson/deli-gator I’d love any feedback