หมายเหตุ
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลอง ลงชื่อเข้าใช้หรือเปลี่ยนไดเรกทอรีได้
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลองเปลี่ยนไดเรกทอรีได้
A skill provides reusable instructions or a workflow that teaches an agent or supported Microsoft experience how to perform a specific job. A skill is represented by a directory with a required SKILL.md file and can include supporting resources or scripts.
A plugin can bring together a skill with other supported capabilities, such as agents, Copilot connectors, or MCP-based tools. The plugin is the unit of extensibility; the skill remains a distinct reusable capability.
Important
Skill availability, sharing, automatic use, and host support vary by Microsoft experience. Current documentation primarily covers adding skills to agents. Follow the guidance for the authoring experience and target host instead of assuming that every skill can be packaged or distributed independently.
Decide whether you need a skill
Choose a skill when:
- The solution requires repeatable instructions or a workflow for a specific job.
- The expertise should be reusable across supported agents or experiences.
- The work can be expressed through instructions and supporting resources.
- The skill can call approved tools or scripts when the target experience supports them.
A skill might not be the right component when:
- The requirement is the complete conversational experience. Consider a declarative agent.
- The requirement is primarily access to external data. Consider a connector.
- The requirement is to expose remotely hosted tools or resources. Consider an MCP server.
Decide whether to build or reuse
Before you build a skill:
- Search for an approved skill that already performs the job.
- Determine whether an existing skill can be reused as-is or configured for the scenario.
- Confirm that the skill format and its resources are supported by the target authoring tool and Microsoft experience.
- Review the instructions and supporting files for data, security, responsible AI, and maintenance requirements.
- Identify any gaps that require a new or extended skill.
If you reuse a skill, confirm who owns its content, versioning, testing, support, and distribution.
Record skill dependencies
As you decide whether to build or reuse a skill, note:
- The job, inputs, expected output, and success criteria.
- The agent or supported Microsoft experience that uses the skill.
- Required knowledge, connectors, MCP-based tools, scripts, or other resources.
- Authentication, permissions, data, and execution requirements.
- Format, version, sharing, and host constraints.
- Owner, support contact, and test requirements.
After you decide to build or reuse a skill, choose development tools.