Skill: the workflow layer
A skill describes how the agent should complete a repeatable task: instructions, sequencing, constraints, examples, and checks. It can exist even when no external integration is required.
These concepts solve different parts of an agent system. A skill defines how to perform a task, a plugin packages access to an external capability, and MCP is a protocol for exposing tools and context in a standardized way.
Last reviewed: 2026-09-18
A skill describes how the agent should complete a repeatable task: instructions, sequencing, constraints, examples, and checks. It can exist even when no external integration is required.
A plugin bundles access to an external product or workflow so the agent can read data or take permitted actions without every user manually rebuilding the integration.
Model Context Protocol standardizes how an AI client can discover and use tools, resources, and prompts exposed by an MCP server. It is infrastructure, not the task workflow itself.
One workflow can use all three: a skill defines the steps, a plugin handles a product-specific experience, and an MCP server can expose the underlying tools or context through a standard interface.
No. A skill primarily describes reusable task behavior, while a plugin provides packaged access to an external capability or workflow. They can be used together.
Not necessarily. MCP standardizes tool and context access, while a plugin can package product-specific authentication, permissions, UI, and workflows around one or more capabilities.
Yes. A skill can tell the agent when and how to call tools that are exposed through MCP, then define how to validate and format the result.
Explore next