A skill written in Copilot chat now runs in Word, PowerPoint, Copilot Cowork, workspaces and Copilot Code, and an administrator can publish it to the whole organization from a single screen. The path is still full of traps: the wrong package type, missing surfaces, Copilot Credits consumption. Here is how to deploy it cleanly and how to check what actually happened.
What changed between June and October 2026
For a year, each Microsoft 365 app invented its own skill management: one OneDrive folder for PowerPoint, another for Excel, and separate skills for Copilot Studio agents, Cowork and SharePoint sites. A skill written for PowerPoint was useless elsewhere, and there was no way to turn it into a team asset rather than a file sitting in a user's OneDrive.
Microsoft fixes this with the plugin registry: a shared place to discover, publish and govern plugins in Home (Chat and Cowork), Code, Autopilot, Word, Excel, PowerPoint and SharePoint, according to the official registry announcement. The "Plugins" page replaces and extends the former "Agents" page, and agents become a component of plugins.
June 2026
Cowork generally available
Cowork is available to all Microsoft 365 Copilot tenants, in tier 1 languages. Its Customize page brings together plugins and skills.
September 2026
Plugin registry and organization skills in PowerPoint
The registry is announced, and PowerPoint lets an administrator publish approved skills.
October 2026
Skills arrive in Copilot Chat
Users create them in natural language and find them in the Agents & Plugins section. PowerPoint's "Record a skill" feature rolls out the same month.
October 2026
Chat/Cowork toggle in the Home tab
Still announced in Frontier, so not yet generally available.
Skill, plugin, registry: what each object contains
A skill is a folder containing a SKILL.md file. The header carries a name and a description that tells the model when to use it; the body contains the instructions in plain language; reference files or scripts can accompany it. A plugin groups skills, connectors and agents. The registry is the catalog where the administrator uploads and governs them.
Here is an illustrative example, a house style checker that separates what it fixes from what it flags:
1---2name: verificateur-style-maison3description: Vérifie un document selon le guide de style maison. Corrige les règles marquées corrigeables et signale celles qui exigent un éditeur. À utiliser pour toute relecture de contenu produit ou marketing.4---5 6# Vérificateur de style maison7 8## Règles corrigeables9- Écrire les unités au format « 12 kg ».10- Remplacer « solutions » par « produits » dans les fiches produit.11 12## Règles à signaler sans corriger13- Toute allégation de performance chiffrée sans source.14- Tout passage dont le ton relève d'une décision éditoriale.15 16## Format de sortie17- Dans Word : activer le suivi des modifications, un commentaire par signalement.18- Dans le chat : lister les corrections, puis les signalements.The Microsoft Learn documentation on developing Cowork plugins states that these packages are compatible with the Claude format: a SKILL.md is copied as is and a Claude plug.json is converted automatically. A plugin skill cannot override a built-in skill of the same name, so avoid generic names.
Microsoft 365 Copilot license required
Users of Cowork plugins must have a Microsoft 365 Copilot license. Cowork is billed on a pay-as-you-go basis in Copilot Credits: model responses and skill calls count toward consumption, and a spending policy can be created in the admin center.
On the personal storage side, Cowork imposes limits documented in its app listing:
50
Maximum custom skills in Cowork
Microsoft Learn
20
Maximum companion files per skill
Microsoft Learn
5 MB
Maximum size per companion file (10 MB total)
Microsoft Learn
These skills live in OneDrive under Documents/Cowork/skills/{name}/SKILL.md. Microsoft does not validate custom skills and asks that their results be reviewed carefully: a poorly written skill produces wrong corrections, with just as much confidence as good ones.
Where a skill created in chat works today
A skill saved from chat can be invoked in several surfaces, but not everywhere, and not in the same way. Field tests reveal clear gaps:
| Surface | Observed behavior | Activation |
|---|---|---|
| Copilot Chat | Works; list of changes and flags in the conversation | Selection via Context IQ, or automatic use if the task matches |
| Word (desktop) | Works; track changes and comments | Plugin list in the Copilot pane |
| Word for the web | Tracking enabled, but granular edits fail repeatedly | Plugin list; prefer desktop |
| PowerPoint | Works; direct correction of the slide, without track changes | Enable the organization in plugin management |
| Copilot Cowork | Works; batch processing of a folder of documents | Disabled by default; enable in plugins |
| Workspaces and projects | Works; used on the workspace's resources | Toggle in settings |
| Copilot Code | Works | Skill loading |
| Excel | Does not receive the skill; keeps its OneDrive folder and built-in finance and data skills | No organization toggle |
| SharePoint and OneDrive | Site skills stored in a dedicated library, outside this mechanism | Not applicable |
The registry nonetheless lists Excel and SharePoint among its surfaces. The gap between this promise and the observed behavior deserves testing on your tenant before announcing full coverage. Outlook is not covered either.
The use case where Cowork is justified is the batch of files. A company that needs to apply its style guide to an entire folder of product sheets benefits from loading the same skill into Cowork and getting a summary table of changes, whereas chat or Word handle one document at a time. For a single file, Cowork is disproportionate, and its Copilot Credits billing weighs on the decision.
The "Record a skill" feature remains specific to PowerPoint. The experience therefore differs from one app to another, which complicates adoption. Our guide on Copilot skills in PowerPoint, Excel and Cowork details these differences from the user side.
Publishing a skill to the whole organization
The main trap is the package type. The skill download offered by chat is not what the registry expects: you need an app package that encapsulates the skill with a manifest and two icons. Ask chat for it explicitly.
Get the right package
In chat, ask for an app package rather than the skill download. For PowerPoint, the expected package is a .zip containing manifest.json, color.png, outline.png and a folder with SKILL.md.
Upload to the registry
In the Microsoft 365 admin center: Agents > Tools > Registry, Upload button, then select the plugin or skill manifest.
Install and target
Under Agents > Tools > Plugins, install or block the plugin and choose its availability: all users, none, or specific groups.
Set access by publisher type
Under Agents > Settings > Agent and plugin access, define the policy according to the publisher. The documentation links this control to Microsoft Agent 365; the full procedure is on Microsoft Learn.
Verify on the user side
In PowerPoint, open the Copilot pane then the + > Choose skills menu. In Copilot Chat, the skill appears in the Agents & Plugins section.
An “all users” availability affects the entire tenant
The pages consulted give no propagation delay. Do not draw conclusions from an immediate test. Target a pilot group first, review the skill's outputs, then widen the scope. A skill that corrects documents on the user's behalf must have been reviewed by its business owner.
If your tenant has Purview Information Barriers enabled, uploading embedded knowledge files is blocked, which can prevent the publication of some plugins or skills.
Implementation: validate and assemble a package before upload
Uploading to the registry remains a portal action. However, you can locally check a skill folder, verify Cowork's limits and assemble the expected .zip. Prerequisites: PowerShell 7, no module to install, no admin role (the script reads and writes locally only). It produces a .zip and displays its contents; with -DryRun, it validates without writing anything. Provide the manifest.json and the two icons from the app package generated by chat: the script does not build a manifest.
1#Requires -Version 7.02[CmdletBinding()]3param(4 [Parameter(Mandatory)][string]$SkillFolder,5 [Parameter(Mandatory)][string]$ManifestPath,6 [Parameter(Mandatory)][string]$ColorIcon,7 [Parameter(Mandatory)][string]$OutlineIcon,8 [string]$OutputZip = (Join-Path (Get-Location).Path 'skill-package.zip'),9 [switch]$DryRun10)11 12$ErrorActionPreference = 'Stop'13$maxFileBytes = 5MB14$maxTotalBytes = 10MB15$maxCompanions = 2016 17# 1. Toutes les entrées existent18foreach ($path in @($SkillFolder, $ManifestPath, $ColorIcon, $OutlineIcon)) {19 if (-not (Test-Path -LiteralPath $path)) { throw "Introuvable : $path" }20}21$skillFolderItem = Get-Item -LiteralPath $SkillFolder22$skillFile = Join-Path $skillFolderItem.FullName 'SKILL.md'23if (-not (Test-Path -LiteralPath $skillFile)) { throw "SKILL.md absent de $($skillFolderItem.FullName)" }24 25# 2. Le manifeste est un JSON valide26$null = Get-Content -LiteralPath $ManifestPath -Raw | ConvertFrom-Json27 28# 3. L'en-tête de SKILL.md porte name et description29$content = Get-Content -LiteralPath $skillFile -Raw30if ($content -notmatch '(?s)^---(.*?)---') { throw 'En-tête manquant dans SKILL.md.' }31$header = $Matches[1]32foreach ($key in 'name', 'description') {33 if ($header -notmatch "(?m)^$($key):\s*\S+") { throw "Clé '$key' absente ou vide dans l'en-tête de SKILL.md." }34}35 36# 4. Fichiers compagnons : limites documentées pour Cowork37$companions = @(Get-ChildItem -LiteralPath $skillFolderItem.FullName -File -Recurse | Where-Object { $_.Name -ne 'SKILL.md' })38$totalBytes = ($companions | Measure-Object -Property Length -Sum).Sum ?? 039if ($companions.Count -gt $maxCompanions) { throw "Plus de $maxCompanions fichiers compagnons." }40$tooBig = @($companions | Where-Object { $_.Length -gt $maxFileBytes })41if ($tooBig.Count -gt 0) { throw "Fichier(s) de plus de 5 Mo : $($tooBig.Name -join ', ')" }42if ($totalBytes -gt $maxTotalBytes) { throw 'Plus de 10 Mo de fichiers compagnons au total.' }43 44Write-Host ('Compétence : {0} | fichiers compagnons : {1} | taille : {2:N2} Mo' -f $skillFolderItem.Name, $companions.Count, ($totalBytes / 1MB))45if ($DryRun) { Write-Host 'Mode simulation : aucun paquet créé.'; return }46 47# 5. Assemblage dans un dossier temporaire, puis compression48$staging = Join-Path ([System.IO.Path]::GetTempPath()) ([guid]::NewGuid().ToString())49try {50 New-Item -ItemType Directory -Path $staging | Out-Null51 Copy-Item -LiteralPath $ManifestPath -Destination (Join-Path $staging 'manifest.json')52 Copy-Item -LiteralPath $ColorIcon -Destination (Join-Path $staging 'color.png')53 Copy-Item -LiteralPath $OutlineIcon -Destination (Join-Path $staging 'outline.png')54 Copy-Item -LiteralPath $skillFolderItem.FullName -Destination (Join-Path $staging $skillFolderItem.Name) -Recurse55 Compress-Archive -Path (Join-Path $staging '*') -DestinationPath $OutputZip -Force56 57 # 6. Vérification : contenu réel de l'archive58 Add-Type -AssemblyName System.IO.Compression.FileSystem59 $zip = [System.IO.Compression.ZipFile]::OpenRead($OutputZip)60 try { $zip.Entries | Select-Object FullName, Length } finally { $zip.Dispose() }61}62finally {63 Remove-Item -LiteralPath $staging -Recurse -Force -ErrorAction SilentlyContinue64}Expected result: manifest.json, color.png, outline.png at the root of the archive, and the skill folder with its SKILL.md. If any of these entries is missing, do not upload.
To audit the personal skills on a workstation, this second script compares each folder in Documents/Cowork/skills against the documented limits. It uses the OneDriveCommercial variable; if it is empty or if Documents is redirected, pass -SkillsRoot.
1#Requires -Version 7.02[CmdletBinding()]3param(4 [string]$SkillsRoot = (Join-Path $env:OneDriveCommercial 'Documents/Cowork/skills')5)6 7$ErrorActionPreference = 'Stop'8if (-not (Test-Path -LiteralPath $SkillsRoot)) {9 throw "Dossier introuvable : $SkillsRoot (utilisez -SkillsRoot si Documents est redirigé)."10}11 12$skills = @(Get-ChildItem -LiteralPath $SkillsRoot -Directory)13if ($skills.Count -gt 50) { Write-Warning "$($skills.Count) compétences : la limite documentée est de 50." }14 15$report = foreach ($skill in $skills) {16 $companions = @(Get-ChildItem -LiteralPath $skill.FullName -File -Recurse | Where-Object { $_.Name -ne 'SKILL.md' })17 $total = ($companions | Measure-Object -Property Length -Sum).Sum ?? 018 19 $issues = @()20 if (-not (Test-Path -LiteralPath (Join-Path $skill.FullName 'SKILL.md'))) { $issues += 'SKILL.md absent' }21 if ($companions.Count -gt 20) { $issues += 'plus de 20 fichiers compagnons' }22 if ($companions | Where-Object { $_.Length -gt 5MB }) { $issues += 'fichier de plus de 5 Mo' }23 if ($total -gt 10MB) { $issues += 'plus de 10 Mo au total' }24 25 [pscustomobject]@{26 Competence = $skill.Name27 Compagnons = $companions.Count28 TailleMo = [math]::Round($total / 1MB, 2)29 Anomalies = if ($issues) { $issues -join ' ; ' } else { 'OK' }30 }31}32 33$report | Sort-Object Competence | Format-Table -AutoSize34Write-Host "Compétences : $($skills.Count) / 50"Limits, costs and common failures
Before generalizing, weigh three points. The first is cost: each skill call consumes Copilot Credits in Cowork, so batch processing hundreds of files needs a budget. The second is quality: no validation by Microsoft, so review remains human. The third is experience consistency: slash in chat, plugin list in Word, organization toggle in PowerPoint, settings toggle in workspaces. To structure your governance, the four levels of control over Copilot agents provide a useful framework.
| Symptom | Likely cause | Resolution |
|---|---|---|
| The registry rejects the uploaded file | Raw skill package instead of an app package | Ask chat again for an app package, then check the archive with the validation script |
| The skill does not appear in PowerPoint's plugin list | Personal skill filed under the organization, not enabled | Open plugin management and enable the organization |
| The skill is disabled in Cowork | Disabled by default | Enable it in plugins, from the Customize page |
| Publication blocked for a plugin or skill | Purview Information Barriers blocks uploading embedded knowledge files | Identify the files embedded in the package and validate the approach with the compliance team |
| A shared plugin only appears in Shared with me | It was not uploaded by an administrator | Upload the package in Agents > Tools > Registry to expose it in Discover |
| A plugin skill is not applied | It has the same name as a built-in skill | Rename it |
| Incomplete or failed Word edits | Running in Word for the web | Use desktop Word, which worked in field tests |
Frequently asked questions
Do you need a Microsoft 365 Copilot license to use a plugin's skills?
Yes for Cowork plugins: users must hold a Microsoft 365 Copilot license. Cowork is also billed on a pay-as-you-go basis in Copilot Credits, with a spending policy to create in the admin center.
Does a skill written for Claude work in Cowork?
It is compatible: a Claude SKILL.md is copied as is and a Claude plug.json is converted automatically. Review it anyway, because Microsoft does not validate custom skills.
Can you publish a skill for PowerPoint only?
Yes. An administrator can publish approved skills for users, groups or the whole organization, as a .zip with manifest.json, color.png, outline.png and a folder containing SKILL.md. Users choose them via the + > Choose skills menu.
Why doesn't my skill appear in Excel or SharePoint?
In field tests, these two surfaces did not receive the skill created in chat: Excel keeps its own OneDrive folder and SharePoint its dedicated library. Test on your tenant before promising full coverage.
Where to start: three decisions to make
Before publishing the first skill
- Choose a simple business process, already documented as a procedure or checklist
- Write the
SKILL.md, then validate the package with the script in-DryRunmode - Create the Copilot Credits spending policy before opening Cowork
- Check whether Purview Information Barriers is active on the tenant
- Publish first to a pilot group via Agents > Tools > Plugins, then test in chat, desktop Word and PowerPoint
If your organization works mostly in Word and PowerPoint, start with a review skill targeted at those two apps. If your usage relies on Excel or shared SharePoint sites, wait until you have verified their coverage on your tenant, then prepare the packages in parallel. Our selection of five reusable skills to master offers ideas for first use cases.
Going further
- Introducing the plugin registry – Microsoft Copilot blog: the registry announcement, what a plugin is and how the administrator governs it.
- Manage plugins, skills, and MCP servers in Microsoft 365 admin center: the procedure for uploading, installing, blocking and targeting.
- Customize Copilot Cowork: creating, importing and sharing skills and plugins, with formats and size limits.
- Deploy organization skills for Copilot in PowerPoint: the
.zippackage format and deployment steps in PowerPoint. - Copilot skills: PowerPoint, Excel and Cowork: our user-side comparison.



