Member-only story
Every team building agents in 2026 eventually hits the same fork in the road. The agent almost does what you want. It has the tools, it has the data, and it still botches the job in a way that feels avoidable. So you face a choice: hand it another tool, or teach it to use the tools it already has. That choice is now a concrete architectural decision, because the industry has shipped two different open standards that answer it in opposite ways — the Model Context Protocol (MCP) and Agent Skills.
Getting the distinction wrong is expensive. Teams keep building MCP servers to solve problems a text file would have solved, and keep stuffing procedural instructions into brittle system prompts when a Skill would have carried them. Here is how to tell which one a given problem actually needs.
What an Agent Skill actually is #
An Agent Skill is a folder. At minimum it contains a single file, SKILL.md
, whose YAML frontmatter declares a name
and a description
. The body holds instructions — workflows, steps, conventions — and the folder can also bundle reference files and executable scripts. According to Anthropic's Agent Skills documentation, the format is deliberately close to an onboarding guide you'd write for a new teammate: what to do, when, and where to look for the details.
The mechanically important part is how a Skill loads. Skills use progressive disclosure: the agent pulls information in stages instead of…