GitHub Copilot Skillsets Guide
GitHub Copilot Skillsets Guide
GitHub Copilot uses two adjacent extensibility ideas that are easy to mix up: Agent Skills and skillsets. They are related, but they solve different layers of the problem.
Agent Skills vs skillsets
Use Agent Skills when you want reusable workflows, instructions, and operating procedures packaged around SKILL.md.
Use skillsets when you are extending Copilot through a GitHub App and exposing callable endpoints, schemas, and tool-like functionality.
In short:
- Agent Skills package process
- skillsets package callable capability
Why this distinction matters
Searches for “GitHub Copilot skills” often blur these two concepts. That can lead teams to overbuild an extension when a documented workflow would have been enough, or to write a skill when the real need is an API-backed capability.
The cleanest way to decide is to ask whether the problem is primarily about behavior or access.
When to use each
Use a skill when:
- the workflow is repeatable
- the runtime already has the necessary access
- you want portable instructions
Use a skillset when:
- Copilot needs to call an external service
- you need schema-driven parameters and endpoints
- the capability should live in a GitHub App