First it was MCPs, now its skills.

I had it nailed. My agent setup was perfect — a dozen MCP servers wired in, everything humming. I felt smug for roughly a fortnight. Then Skills landed and quietly reframed half of what I'd built. The coding-agent world moves fast enough to give you whiplash.

The treadmill

This is the third or fourth time I've declared my setup "done". Each time, a new abstraction arrives, the community pivots overnight, and the thing I spent a weekend perfecting is suddenly the old way of doing it. MCP was the must-have. Now the conversation is all Skills. Next month it'll be something with a different three-letter acronym.

MCPs versus Skills, briefly

They're not really competitors, which is half the confusion. MCP is a protocol — a standard way to plug tools and data sources into an agent via servers. Skills are packaged instructions plus scripts that an agent loads on demand when a task calls for them. One is about connecting capabilities; the other is about packaging know-how. They overlap enough to make you question your old setup and differ enough that you can't just swap one for the other.

Chasing the meta is a trap

If you rebuild your entire workflow every time a new abstraction trends, you'll never actually ship anything — you'll just have the most fashionable toolbox on a project that never moves. The tooling is a means. It is astonishingly easy to forget that when there's a shiny new thing to configure.

What actually lasts

Underneath the churn, the fundamentals don't move much: clear instructions, disciplined context, version-controlled configuration, and actually knowing the domain you're working in. Get those right and you can adopt MCP, Skills, or whatever comes next as a thin layer on top, rather than a foundation you keep ripping up. So I'll learn Skills, fold in the genuinely useful bits, and ignore the rest. Next month, when it's something else, I'll do the same again.