Live data from Hacker News

Claude Skills

anthropic.com

321–330 of 443 posts

Re: Claude Skills

#321
post #138

Earlier quoted context omitted.

what makes it more likely that claude would read these .md files then?

Skills is hopefully put through a deterministic process that is guaranteed to occur, instead of a non-deterministic one that can only ever be guaranteed to happen most of the time (the way it is now).

It is literally just injecting context into the prompt.

Re: Claude Skills

#322
post #27

Earlier quoted context omitted.

If so it would be most welcome since LLMs doesn't always consistently follow the folder full of MD files to the same depth and consistency.

what makes it more likely that claude would read these .md files then?

It includes both the file names and a configurable description string. That’s where you put the TLDR of when to use each skill.

Re: Claude Skills

#323
post #142

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.

As usual, stick with the basic 20% which give 80% of the value.

Re: Claude Skills

#324
I like where this it's heading. In coming months, I'm expecting claude to learn skills automatically based on my inputs overtime.

Having able to start off with a base skill level is nice tho as humans can't just load into memory like this

Re: Claude Skills

#325
post #306

Earlier quoted context omitted.

This is just a formalization of an existing pattern many people were already using. Putting a list of short blurbs pointing Claude Code at a set of extra, longer sets of CLAUDE.md style information was being used to prevent auto loading that context until it was needed. Instead of assuming this is just change for the sake of change, it’s actually a nice way to support a usage pattern that many of us found works well…

If by "works well already" you mean "inconsistent prompt hacks that you have to constantly reinforce" then sure. CLAUDE.md holds about as much weight has the "Classroom Rules" craft posters hanging in most kindergarten classrooms.

Then you have misplaced your complaints. It sounds like you just don’t like the general instruction following patterns of Claude. Which is fine, but that is nothing specific to this Skills feature

Re: Claude Skills

#326
post #142

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.

Just wait until I can pull in just the concepts I want with "GPT Package Manager." I can simply call `gptpm add skills` and the LLM package manager will add the Skills package to my GPT. What could go wrong?

That's already the case with https://docs.claude.com/en/docs/claude-code/plugins

Re: Claude Skills

#328
post #225

Just published this about skills: "Claude Skills are awesome, maybe a bigger deal than MCP" https://simonwillison.net/2025/Oct/16/claude-skills/

Finally a good replacement for MCP. MCP was a horrible idea executed even worse and they hide the complexity under a dangerous "just paste this one liner into your mcpServers config!" together with wasting tens of thousands of tokens.

Re: Claude Skills

#329

I’m kind of in stitches over this. Claude’s “skills” are dependent upon developers writing competent documentation and keeping it up to date…which most seemingly can’t even do for actual code they write, nevermind a brute-force black box like an LLM. For those few who do write competent documentation and have well-organized file systems and the risk tolerance to allow LLMs to run roughshod over data, sure, there’s so…

Just went to the comments searching for a comment like yours and I'm surprised it seems to be the only one calling this out. My take on this is also that "Skills" is just detailed documentation, which like you correctly point out, basically never exist for any project. Maybe LLM skills will be the thing that finally makes us all write detailed documentation but I kind of doubt it.

I think part of the reason developers are resistant to writing docs is because the perceived value is very low.

This perceived value would be much higher if the docs were to tangibly become part of a productive tool chain

Re: Claude Skills

#330
post #142

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.

You forgot mcp-everything! Yes, it's a mess, and there will be a lot of churn, you're not wrong, but there are foundational concepts underneath it all that you can learn and then it's easy to fit insert-new-feature into your mental model. (Or you can just ignore the new features, and roll your own tools. Some people here do that with a lot of success.) The foundational mental model to get the hang of is really just:…

You have a great way of demystifying things. Thanks for the insights here!

Do you think a non-programmer could realistically build a full app using vibe coding?

What fundamentals would you say are essential to understand first?

For context, I’m in finance, but about 8 years ago I built a full app with Angular/Ionic (live on Play Store, under review on Apple Store at that time) after doing a Coursera specialization. That was my first startup attempt, I haven’t coded since.

My current idea is to combine ChatGPT prompts with Lovable to get something built, then fine-tune and iterate using Roo Code (VS plugin).

I’d love to try again with vibe coding. Any resources or directions you’d recommend?

Post reply on HN