It will be interesting to see how this is structured. I was already doing something similar with Claude Projects & Instructions, MCP, and Obsidian. I'm hoping that Skills can cascade (from general to specific) and/or be combined between projects.
Claude Skills
161–170 of 443 posts
Re: Claude Skills
#162I 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.
Hopefully there’s a similar “don’t make me think” mantra that comes to AI product design.
I like the trend where the agent decides what models, tooling and thought process to use. That seems to me far more powerful than asking users to create solutions for each discreet problem space.
Re: Claude Skills
#163So sort of like MCP prompt templates except not prompt templates?
Re: Claude Skills
#164Sub agents, mcp, skills - wonder how are they supposed to interact with each other? Feels like fair bit of overlap here. It's ok to proceed in a direction where you are upgrading the spec and enabling claude wth additional capabilities. But one can pretty much use any of these approaches and end up with the same capability for an agent. Right now feels like a ux upgrade from mcp where you need a json but instead can…
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?
Yeah how is this different from MCP prompts?
Re: Claude Skills
#165Re: Claude Skills
#166AGI nowhere near
Re: Claude Skills
#167Could be helpful. I often edit scientific papers and grant applications. Orienting Claude on the frontend of each project works but an “Editing Skill” set could be more general and make interactions with Claude more clued in to goals instead of starting stateless.
Re: Claude Skills
#168I 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.
Except in reality it's ALL marketing terms for 2 things: additional prompt sections, and APIs.
Re: Claude Skills
#169I 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.
[deleted]
Re: Claude Skills
#170One sharp contrast though I see between OpenAI and Anthropic is the product extensions are built around their flagship products.
OpenAI ships extensions for ChatGPT - that feed more to plug into the consumer experience. Anthropic ships extensions (made for builders) into ClaudeCode - feel more DX.