--- title: "Copilot Skills" id: "70647" type: "page" slug: "copilot-skills" published_at: "2026-11-12T20:20:42+00:00" modified_at: "2026-11-12T20:20:42+00:00" url: "https://www.uscloud.com/microsoft-support-glossary/copilot-skills/" markdown_url: "https://www.uscloud.com/microsoft-support-glossary/copilot-skills.md" --- Overview: - [What are Copilot Skills?](#what-are-copilot-skills) - [First, identify which “skills” you mean](#first-identify-which-skills-you-mean) - [The parts of a useful skill](#the-parts-of-a-useful-skill) - [Skills, instructions, tools, and plugins are not interchangeable](#skills-instructions-tools-and-plugins-are-not-interchangeable) - [A workplace example: a recurring leadership briefing](#a-workplace-example-a-recurring-leadership-briefing) - [Trust, permissions, and maintenance](#trust-permissions-and-maintenance) - [Questions teams commonly ask](#questions-teams-commonly-ask) - [Treat a skill as a maintained playbook](#treat-a-skill-as-a-maintained-playbook) - ## What are Copilot Skills? In this article, **Copilot Skills** means the built-in and custom capabilities used by Microsoft Copilot Cowork. A skill gives Cowork focused instructions for a type of work. Cowork can select relevant skills during a task, and users can create their own for repeatable workflows. A skill is not a separate employee, application, or license category. It is a way to package specialized instructions and, where applicable, supporting resources so they can be reused. A skill can guide how Cowork approaches work, but it does not by itself grant access to files, email, or other services. ## First, identify which “skills” you mean Microsoft uses “skills” in more than one context. The label may refer to reusable capabilities for Copilot Cowork, agent skills in Copilot Studio, or employees’ professional skills in Microsoft 365 profiles. These are different things. The Cowork meaning is specifically about guiding an AI workflow. It is not the same as general “Copilot skills,” meaning a person’s ability to use AI, and it is not an employee competency profile. When planning, searching, or discussing administration, naming the product context avoids confusion. ## The parts of a useful skill A custom Cowork skill needs a clear name, a description that signals when to use it, and instructions for how to perform the task. Some skills can also include supporting files. The description matters: it helps Cowork distinguish this skill from other capabilities and decide when it is relevant. A useful skill typically answers four questions: - **Purpose:** What recurring task does it support? - **Trigger:** What kind of request should cause Cowork to use it? - **Method:** What steps, checks, or structure should it follow? - **Limits:** What should it avoid doing, or ask the user to confirm? For example, “Help with communications” is too broad to guide consistent behavior. “Prepare a weekly project update from the user’s accessible project messages and documents, separating confirmed progress from unresolved questions” sets a more focused expectation. ## Skills, instructions, tools, and plugins are not interchangeable | Component | Primary role | Example | | --- | --- | --- | | Custom instructions | Set preferences that apply broadly to a user’s work | Prefer concise meeting summaries | | Skill | Guide a specific type of task | Create a weekly project update in a consistent format | | Tool or connector | Provide a way to retrieve information or take an action | Access a connected service | | Plugin | Package extensions, which may include skills or connections | Add a specialized capability to Cowork | A skill can describe a process, but it is not automatically a connection to an external system or permission to take an action. A plugin may bundle more than instructions. The distinction matters when evaluating what a capability can access, what it can do, and who needs to review it. Copilot Chat and Microsoft 365 Copilot are also distinct experiences. Copilot Chat is conversational support for questions and tasks; its available context depends on the experience and account. Microsoft 365 Copilot is designed to work more closely with Microsoft 365 apps and eligible work data, subject to permissions and organizational settings. Cowork uses skills as part of a more task-oriented experience. Access and capabilities can vary by license, account, configuration, and service update. ## A workplace example: a recurring leadership briefing Imagine an operations manager who prepares a weekly briefing from project updates, meeting notes, and email. A custom skill could direct Cowork to organize the briefing by project, distinguish completed work from planned work, and flag unanswered questions. The manager should test it with a few representative weeks before relying on it. If the skill routinely treats tentative plans as confirmed commitments, its instructions need a clearer distinction between evidence and inference. The manager should also verify the draft against the underlying work material before distributing it. The skill can make the process more repeatable, but the manager remains accountable for the briefing. ## Trust, permissions, and maintenance A skill influences how an AI system interprets and responds to a request. Treat its instructions and any included files as content that deserves review, particularly if the skill is shared or obtained from someone else. In practice, teams should: - Review a skill before uploading or sharing it. - Limit sharing to people who need the capability. - Check whether instructions are still accurate when the process changes. - Test whether the skill activates for the intended requests and stays out of unrelated ones. - Confirm that Cowork’s access to information aligns with the user’s permissions and organizational controls. Availability, sharing options, administration, and licensing can vary. A skill should not be assumed to bypass existing permissions, and organizations should verify how skills and any associated plugins are governed in their environment. ## Questions teams commonly ask **Does a skill run every time Cowork is used?** Not necessarily. Skills are intended to apply when a request matches their purpose. A vague description can make that selection less reliable. **Can a skill give Cowork access to data?** A skill’s instructions do not themselves grant access. Cowork’s access depends on the user’s permissions and the connected capabilities available in the environment. **Is a skill the same as an agent?** No. A skill guides a focused type of work. An agent is a broader AI-based component or experience that can use instructions, knowledge, tools, and other capabilities. **Can employees share custom skills?** Sharing options depend on the Cowork environment and organization settings. Before distributing a skill, review its instructions, included materials, intended audience, and maintenance owner. **Does creating a skill require a separate purchase?** Do not assume a universal licensing or pricing rule. Access to Cowork, particular capabilities, and plugins may depend on the account, subscription, configuration, or provider terms. **How should a team evaluate a skill?** Test it with realistic requests, including edge cases. Check whether it activates when intended, follows the process, respects its limits, and produces work that a person can verify. ## Treat a skill as a maintained playbook A Copilot Skill is most valuable when it captures a repeatable task with clear boundaries, not when it tries to encode an entire department’s work in one set of instructions. Its usefulness depends on how well it identifies the task, how carefully it is tested, and whether someone keeps it current. That makes ownership and review part of the skill itself, not an afterthought.