Apparently, everyone is writing agent skills these days. We have skills for code reviews, architecture analysis, testing, debugging, and just about everything else. Meanwhile, we're debating whether comments in source code are an anti-pattern, while writing thousands of lines of Markdown to tell agents how to write code. :) Don't get me wrong. Skills can be useful. But availability isn't execution, instructions aren't guarantees, and more configuration doesn't necessarily produce better outcomes. We had linters, compilers, scripts, and deterministic analysis tools long before we had agent skills. I wrote about the growing complexity of agent configurations, what independent research actually tells us, and why I eventually deleted all my skills and instruction files. We Had Linters Before We Had Skills menges.dev/writing/we-had-li…

While working on a new blog post, I did some refactoring of Enola itself today. With Opus 5.5 it was a weekend of work - yesterday and today, intermittently, when I was around the computer (more today considering the weather). As I am following up package metrics (beside other things) on every change, I noticed that numbers went a bit out of proportion, so today I dog fed Enola with Enola, while following the results in CI as the work was happening. And, interestingly, one of the commits was again cleaning up dead code - not necessarily not used, but one too many indirection that Enola discovered itself.