MCP adds standard Agent Skills discovery and loading

The MCP addition sits on top of a connection layer that already standardized how agents reach tools, resources, and external systems. What was missing was a standard place to put the playbook: the reusable knowledge of how a workflow should be performed. Previously, that knowledge often lived separately in docs, repos, prompt files, or custom integrations, which meant it had to be maintained and versioned apart from the server that provided the capability.

Serving skills through MCP's Resources primitive changes that distribution model. Because SKILL.md, references, scripts, and examples are exposed as resources, an agent can first discover what skills exist, inspect their metadata, and then load only the one required for the current task. The article frames this as context window management: instead of loading every workflow instruction upfront, the agent pays only for what it uses, and reusable workflows travel with the server rather than with each client.

How much this matters in practice hinges on client behavior. On-demand loading only saves context if clients actually defer reading skills instead of prefetching them, and the body offers no adoption or rollout figures. For teams already running MCP servers, the practical question is whether their client of choice supports this discovery-and-load flow; if it does, workflow knowledge can be versioned and shipped alongside the tools themselves, and if it does not, the older split between capability and playbook is likely to persist.