Claude skills is cool! I hear people saying that
@AnthropicAI focuses too much on side quests instead of building better cheaper faster models.
I don’t think so. They understood that creating the best coding model is useless if doesn’t have access to a high quality agent ecosystem and they’ve committed to building this ecosystem in the open.
I have several years of experience as senior software dev and I recently finished my MSc. in innovation management. This is my take from an interdisciplinary perspective.
If it wasn’t for Anthropic, CLI coding environments would not be what they are today. Codex, opencode, Gemini CLI etc are great (some more, some less) and they are essential to drive innovation, but we cannot appreciate enough what Anthropic has given to us.
They had the guts to invest when there was no reliable indication that CLI tools could be a serious market in a world where devs spend their days in IDEs. They still saw the potential and went for radical innovation.
Then they created standards like MCP in a way that separates their financial interests completely from the concept. It works perfectly well with any other model and coding tool and it made everyone better off. It’s also incredibly easy to use claude code with other coding models, further confirming their dedication to open innovation.
And they keep pushing. They look at people’s needs and they search for universal solutions.
Claude Skills may seem like a trivial solution but that is exactly the beauty of it. Devs at Anthropic learned from the trouble that comme with MCPs. They read the papers about context rot and recognized that developers need a more lightweight way to connect their coding agent with the tools that are already present on their system as fully configured CLI tools or to provide context for reoccurring complex tasks that don’t need external tools. Without polluting context.
MCPs have their right of existence. Remote MCPs are hilarious and define a unified structure that allows developers to give agents (remote) tool access across ecosystems. It’s a turning point and I think this ecosystem is only in its very beginning. When I look at well developed MCP servers like the
@linear MCP, I can only imagine the bright future this technology offers for agents.
But to be honest I see the future of MCPs mainly with task dedicated production agents. Less with general purpose coding agents. Professional developers usually have their tools at hand and can access them via cli commands. They also have an idea of how they want these tools to be utilized. There is no need for an additional abstraction layer defined by the scary and powerful term “server”. If a coding agent should access my Postgres dev DB, it should just use the pg cli tool and it knows how to do that without adding 20k tokens every time I use Claude Code.
Of course you could just add the instructions on how you want your cli tools to be used to
Claude.md in every project. But that leads to context pollution again and lacks the joy of reusability we devs love so much.
Agent skills are a simple solution that just add the necessary structure to already existing solutions to makes them reusable and extendable. In innovation science we know that invention != innovation and real innovation often requires looking at ideas others have invented. Then taking a step back to see how they can be adapted to allow for large scale integration makes them a real innovation.
This became a bit long, maybe I should better start blogging. Btw. I have no affiliation with Anthropic but I felt the need to highlight how their attitude of open innovation drives progress in one of the most exciting topics today. Open weight models would be nice though.. ;D
I you made it through this long ass post, I’d love to hear your opinions.
Claude Code Weekly Round Up
A big week for shipping!
Besides Haiku 4.5, we added support for Claude Skills, gave Claude a new tool for asking interactive questions, added an ‘Explore’ subagent, auto-background long running tasks and fixed several bugs.