The agent development landscape shifted sharply in late 2025. Model Context Protocol dominated conversations through most of the year, becoming the de facto standard for building AI agents. Companies hired for MCP expertise. Conferences centered on it. Development roadmaps aligned with it.
Then AI Skills arrived, and the consensus fractured. Engineers rebelled against the new approach, signaling that the market had moved past protocol-focused development. The backlash revealed a deeper truth: builders had optimized for the wrong thing.
The industry spent months perfecting how agents communicate with tools and systems. MCP became the language of choice. Teams invested heavily in standardizing these connections. But protocol mastery proved hollow. What users actually cared about was agent experience.
This pivot matters because it exposes a common developer trap. Technical elegance and standardization feel productive. Adopting a protocol gives teams clear direction and measurable progress. But protocols are infrastructure, not products. They enable good experiences. They do not create them.
The real work happens elsewhere. How does the agent handle ambiguity in user requests? Does it ask clarifying questions or make assumptions? How does it recover from errors? Can it explain its reasoning? Does it gracefully defer to human judgment when uncertain? These questions define whether an agent feels useful or frustrating.
Building good agent experiences requires different skills than implementing protocols. It demands research into how people actually interact with autonomous systems. It needs rapid iteration based on user feedback. It requires design thinking, not just engineering discipline.
The lesson for 2026 is clear: protocol competence is table stakes, not differentiation. Teams that win will be those that treat MCP or whatever infrastructure emerges as solved problems. They will invest the hard work into understanding their users and crafting interactions that feel natural and trustworthy.
The agents that matter will not be the ones with the cleanest protocol implementations. They will
