Copilot Studio skills: share across Cowork and SharePoint

Key insights

• Skills can be shared with specific people in the organization or with a security group.
• Recipients can add a shared skill to an agent through Browse skills in preview.
• The demonstrated skill also appeared in Copilot Cowork and Copilot in SharePoint.
• Deleting the shared skill removed it from Cowork and SharePoint after a delay.
• An agent that had already added the skill kept its copy after the original was deleted.
• After editing a shared skill, share it again to make the latest version available.

Copilot Studio lets makers share a skill with selected people or a security group, making it available for reuse in agents and, in the demonstrated setup, Copilot Cowork and Copilot in SharePoint. This matters to makers who want to distribute a repeatable task without asking each colleague to build the same skill from scratch. Daniel Anderson [MVP] demonstrates sharing a contract-redlining skill and checking how it behaves across these experiences.

What's new

The demonstrated sharing flow is in preview. A skill added to an agent can be shared with other people in the organization, who can find it in a skills catalog and add it to their own agent. In the example, the maker packages a contract-redlining skill and shares it with a colleague named Frankie.

The package contains a file with instructions, Python scripts, and a playbook reference containing the redlining rules. The example then shows the shared skill appearing in Copilot Cowork and in the plugins list for Copilot in SharePoint. That gives the same skill more than one place to be used, rather than limiting it to the maker’s original agent.

Sharing does not mean that later edits automatically reach previous recipients. The Microsoft documentation page cited in the demonstration says to share the skill again after editing it so recipients can get the latest version. Treat distribution as a point-in-time handoff, and plan to reshare when the skill changes.

Who it is for and what you need

This flow is for people creating and managing skills in the new Copilot Studio agent experience, and for colleagues who want to add a skill shared with them. The example uses a packaged skill uploaded as a ZIP file. Its contents include the instructions and supporting files needed for the redlining task.

The sharing options shown are “Only you,” specific people in the organization, and a security group. The person receiving a skill can browse the catalog and add it to an agent. The source material does not state which licenses, regions, or tenant configurations are required, or whether the preview is available to every organization.

Skill sharing is explicitly described as a preview, so the interface and behavior may change. Check the current Microsoft documentation and your environment before basing a production process on the behavior shown. The demonstrated walkthrough does not establish general availability or licensing requirements.

How it works

1. In the Copilot Studio agent experience, add a skill to your agent. The example uploads a ZIP containing , Python scripts, and a playbook reference.
2. Open the skill’s options and choose to share it. Select specific people or a security group, then publish the sharing change. The example shares it with one colleague.
3. As the recipient, create or edit an agent, open Skills, and choose Browse skills. Find the shared skill in the catalog and add it to the agent.
4. Check where the shared skill is available. In the walkthrough it also appears in Cowork and under plugins in Copilot in SharePoint.

The recipient’s controls are not identical to the owner’s. In the example, Frankie can download the skill but cannot share or replace it because someone else created it. The skill’s owner can manage the original sharing, while the recipient can use the skill they added.

Limitations and open questions

The demonstrated Copilot Studio preview does not provide a delete option for the skill. To remove it, the owner goes to Cowork’s Customize area and deletes it there. After a short delay, the shared skill disappears from Cowork and Copilot in SharePoint. The delay means removal may not be immediate across the surfaces shown.

Deletion did not remove the copy already added to Frankie’s agent: it remained available after refresh in the demonstration. This distinction matters when removing a skill. Removing the shared catalog entry is not the same as removing an instance already added to an agent.

The walkthrough tests one skill and one recipient, so it does not establish behavior for every kind of skill, tenant, or configuration. The demonstrated package includes scripts and a playbook, but the source material does not explain security review, governance controls, or access to content referenced by a skill. Those points need confirmation in your own environment and current documentation.

For updates, the documented instruction cited in the demonstration is to share the edited skill again. The walkthrough does not describe a version comparison or automatic update process for copies already added to agents, so do not assume those copies update when the owner changes the source.

Sources

• Microsoft documentation: Share a skill through the marketplace (preview)
• Daniel Anderson [MVP] demonstration of sharing a Copilot Studio skill

Frequently asked questions

How do I share a Copilot Studio skill?

Open the skill’s options in the Copilot Studio agent experience, choose sharing, select specific people or a security group, and publish the change. Recipients can use Browse skills to find and add it.

Can a shared Copilot Studio skill be used in Cowork and SharePoint?

The demonstration shows the shared skill in Copilot Cowork and in the plugins list for Copilot in SharePoint. The material does not confirm availability for every tenant or configuration.

What happens when I delete a shared skill?

In the demonstration, deleting it through Cowork removed it from Cowork and Copilot in SharePoint after a short delay. A copy that had already been added to an agent remained available.

Do I need to reshare an edited skill?

Yes. The Microsoft documentation cited in the demonstration says to share the skill again after editing so previous recipients can get the latest version.