News for hackers. Stuff that matters.
Re:Agent Skills by iainmerrick on Tuesday February 03, 2026 @01:55PM (#46875487)
To clarify, the bit where I think the bitter lesson applies is trying to standardize the directory names, the permitted headings and paragraph lengths, etc. It's pointless bikeshedding.

Making your docs nice and modular, and having a high-level overview that tells you where to find more detailed info on specific topics, is definitely a good idea. We already know that when we're writing docs for human readers. The LLMs are already trained on a big corpus written by and for humans. There's no compelling reason why we need to do anything radically different to help them out. To the contrary, it's better not to do anything radically different, so that new LLM-assisted code and docs can be accessible to humans too.

Well-written docs already play nicely with LLM context.

Re:Agent Skills by ashdksnndck on Tuesday February 03, 2026 @08:05PM (#46879969)
Is your view that this doesn’t work based on conjecture or direct experience? It’s my understanding Anthropic and OpenAI have optimized their products to use skills more efficiently and it seems obviously true when I add skills to my repo (even when the info I put there is already in existing documentation).
Re:Agent Skills by iainmerrick on Wednesday February 04, 2026 @03:03AM (#46882891)
Hmm, that’s a good question! I think a bit of both.

In terms of experience, I’ve noticed that agents don’t always use skills the way you want; and I’ve noticed that they’re pretty good at browsing existing code and docs and figuring things out for themselves.

Is this an example of “the bitter lesson”? That’s conjecture, but I think pretty well-founded.

It could well be that specific formats for skills work better because the agents are trained on those specific formats. But if so, I think it’s just a local maximum.

Re:Agent Skills by ashdksnndck on Wednesday February 04, 2026 @02:22PM (#46890379)
I had a kind of visceral distaste for all of this rules, skills etc stuff when I first heard about it for similar reasons. This generalized text model can speak base64 encoded Klingon but a readme.md isn’t good enough? However given the reality of limited context windows, current models can’t consider everything in a big repo all at once and keep coherent. Attaching some metadata to the information that tells the model when and how to consider it (and assisting the models with tooling written in code to provide the context at the right time) seems to make a big difference in practice.
Re:Agent Skills by xyzzy123 on Wednesday February 04, 2026 @12:06AM (#46881697)
I've never felt that generic, share-able skills were much of a useful thing. The model already knows the generic things!

On the other hand, the specific details of how to do things in YOUR software, in YOUR environment (especially if it's quirky) - that does beat asking the model to work it out from first principles each time.

I still prefer to rely on convention where possible - i.e, what's even better than writing a skill for say, "how to manage users in our ABC application, first call API a..." is to follow some widely established convention that means the obvious first thing the model would naturally try "just works".