I fear the conceptual churn we're going to endure in the coming years will rival frontend dev. Across ChatGPT and Claude we now have tools, functions, skills, agents, subagents, commands, and apps, and there's a metastasizing complex of vibe frameworks feeding on this mess.
i’m letting the smarter folks figure all this out and just picking the tools i like every now and then. i like just using claude code with vscode and still doing some things manually
Claude Skills
211–220 of 443 posts
Re: Claude Skills
#212I fear the conceptual churn we're going to endure in the coming years will rival frontend dev. Across ChatGPT and Claude we now have tools, functions, skills, agents, subagents, commands, and apps, and there's a metastasizing complex of vibe frameworks feeding on this mess.
Re: Claude Skills
#213Earlier quoted context omitted.
I commented here already about deli-gator ( https://github.com/ryancnelson/deli-gator ) , but your summary nailed what I didn’t mention here before: Context. I’d been re-teaching Claude to craft Rest-api calls with curl every morning for months before i realized that skills would let me delegate that to cheaper models, re-using cached-token-queries, and save my context window for my actual problem-space CONTEXT.
>I’d been re-teaching Claude to craft Rest-api calls with curl every morning for months what the fuck, there is absolutely no way this was cheaper or more productive than just learning to use curl and writing curl calls yourself. Curl isn't even hard! And if you learn to use it, you get WAY better at working with HTTP! You're kneecapping yourself to expend more effort than it would take to just write the calls, helpi…
Re: Claude Skills
#214Earlier quoted context omitted.
I know I'm replying to a shitpost. But I had a realisation, and I'm probably not the only one. If you can manage to keep structuring slightly intelligent tools so that they compound, seems like AGI is achievable. That's why the thing everyone is after right now is new ways to make those slight intelligences keep compounding. Just like repeated multiplication of 1.001 grows indefinitely.
But how often can you repeat the multiplication when the repetitions are unsustainable?
But starting earlier this year, I've started to see glimpses of what seems like intelligence (to me) in the tools, so who knows.
Re: Claude Skills
#215AGI nowhere near
I know I'm replying to a shitpost. But I had a realisation, and I'm probably not the only one. If you can manage to keep structuring slightly intelligent tools so that they compound, seems like AGI is achievable. That's why the thing everyone is after right now is new ways to make those slight intelligences keep compounding. Just like repeated multiplication of 1.001 grows indefinitely.
Re: Claude Skills
#216It's pretty neat that they're adding these things. In my projects, I have a `bin/claude` subdirectory where I ask it to put scripts etc. that it builds. In the claude.md I then note that it should look there for tools. It does a pretty good job of this. To be honest, the thing I most need are context-management helpers like "start a claude with this set of MCPs, then that set, and so on". Instead right now I have sep…
Isn’t that sub agents?
Re: Claude Skills
#217Re: Claude Skills
#218Earlier quoted context omitted.
Claude Skills just seem to be the same as MCP prompts: https://modelcontextprotocol.io/specification/2025-06-18/ser... I don't really see why they had to create a different concept. Maybe makes sense "marketing-wise" for their chat UI, but in Claude Code? Especially when CLAUDE.md is a thing?
I see this as a lower overhead replacement for MCP. Rather than managing a bunch of MCP's, use the directory structure to your advantage, leverage the OS's capability to execute
Re: Claude Skills
#219Earlier quoted context omitted.
You'll need to expand on what you mean, I'm afraid.
I think, from my experience, what they mean is tool use is as good as your model capability to stick to a given answer template/grammar. For example if it does tool calling using a JSON format it needs to stick to that format, not hallucinate extra fields and use the existing fields properly. This has worked for a few years and LLMs are getting better and better but the more tools you have, the more parameters your f…