Ask HN: I still don't understand why AI agents need "skills"
"Well-organized markdown docs" are exactly what skills are.
More specifically, they are well-organized markdown docs that explain how to do some particular thing.
After that, I think "skill" is just a good name. It sounds more "AI" than a "spell" or "incantation", which would sound magical and esoteric.
Nothing of the sort happens here though...
So you are not missing anything. What you think is exactly what it is. Just some prefix for preloading the LLM context with..
https://news.ycombinator.com/item?id=48132477
Don't underestimate the value of "Skill builder" skills too. Great UX
They're presented as a list of titles and descriptions to the LLM and it can pick which ones seem relevant and load them.
Markdown docs the LLM needs to make a tool call to read the files and potentially multiple tool calls to discover data if there's a hierarchy. Additionally, it now has to decide if it should read the entire file or cherry pick parts of it.
Skills organize that in an atomic and composable way.
I think ChatGPT and Claude skills will also package arbitrary artifacts like scripts as well. Not sure if that's standard or not
Context, similar to your computer's memory, is limited.
Additionally, the more things the AI has in context, the worse it performs.
Skills helps you to quickly add more context for doing things, without polluting your context window.
I think you need to learn about AI, there isn't anything hype there. It's just an easier way of giving more context to the AI.
This can be helpful, for example, if you have an internal API that does XYZ, and you want the AI to know that API, you can save that API, its endpoints and authenticaiton methods to a skill, and invoke it when you want your harness (CC, Codex) to know about the existance of that API, to make requests, make tests etc.