Comment by SamuelAdams
20 hours ago
Skills are kind of a new thing starting around January 2026, but the spec was established about 12 months ago.
https://news.ycombinator.com/item?id=46871173
Anyways the most layman way I’ve seen it explained is this: skills help save token usage for the right context. Not every request needs all instructions all the time - running tests is different than reviewing a PR, so why should the context window have instructions for both on every request?
So now you split instructions into “skill” files, which are basically opinionated markdown files. And you invoke those with something like /grill-me in the prompt depending on what you’re doing.
There are some steps to have the agent automatically know what to invoke for you but in my experience this automation is hit or miss.
It is also challenging to keep track of a growing library of skills and keeping those up to date.
So YMMV regarding skills. I typically keep things in a single markdown file even if the context window gets a bit bloated.
Yeah, I get that. I have created dozens of skills, but they are usually to accomplish very specific tasks. Some of them have accompanying scripts, etc.
My point is that this sounds more like a general AGENTS.md use case, similar to defining tone of voice, output format, etc.
It just seems skills is the only way to distribute certain "behavior" as of today. But not everything is a skill IMHO, and not this is not one of them.
On the other hand, maybe we're seeing an evolution of what skills are becoming.