A weekly Excel export to clean up, a pricing table to match, then a project report to produce: a simple prompt leaves too much room for variation. A Copilot skill formalizes the method to follow, but you still need to choose the right environment and check what it actually produced.
A skill describes a method, not a guaranteed result
A skill brings together reusable instructions for an identifiable task. It tells the agent when to act and how to proceed, rather than requiring the user to restate the entire procedure with every request. An agent’s general instructions define its role; a skill provides a specialized method it can use for a particular task.
This is useful when a task has several consistent steps: normalize data, apply calculation rules, then present anomalies. It does not remove the need to provide the right inputs or check the outputs. An agent can follow a procedure and still make a mistake with source data or a match.
The operational benefit is therefore verifiable repeatability, not a promise of unsupervised automation. Our article on reusable skills in Microsoft 365 Copilot offers more ideas for identifying tasks worth formalizing.
SKILL.md: the file that connects activation to instructions
For a declarative agent, the Microsoft Learn documentation on skills describes a folder that must contain SKILL.md. Resources or scripts can be added: a skill is not necessarily a standalone file. Instructions are limited to 20,000 characters.
Here is a minimal example for an editorial review. The name identifies the skill; the description helps determine when to use it. The detailed instructions specify what it should do once selected.
1---2name: revue-communique3description: Utiliser pour relire un communiqué et contrôler la cohérence de marque.4---5# Revue du communiqué6 7## Méthode8- Repérer les formulations incohérentes avec les consignes de marque fournies.9- Signaler les informations absentes sans les inventer.10- Proposer des corrections et distinguer les faits à valider.A description that is too broad may cause the skill to be selected for an unrelated request; one that is too narrow may prevent its use for a legitimate variation. Write it as an activation criterion, then test requests that should activate it and others that should not.
An imported file is still an instruction that needs auditing
Review skills obtained from a third party before adding them to an agent. Check their instructions, resources and any scripts; do not give them access to data their author should not have.
Excel, Agent Builder and Cowork have different prerequisites
The concept is shared, but the entry points and access requirements differ. Copilot Cowork has been generally available since June 2026 for Microsoft 365 Copilot tenants, according to the updates published by Microsoft. That availability does not make custom skills for declarative agents generally available: they remain in Frontier preview.
| Environment | How the skill is used | Requirement to check |
|---|---|---|
| Copilot in Excel | Procedure applied to a workbook | Custom skills in preview; version 2608 (build 20305.20002) or later and the Beta or Current Channel (Preview) channel of the Microsoft 365 Insider program |
| Agent Builder | Method integrated into a declarative agent | Eligible Microsoft 365 Copilot license or pay-as-you-go billing, and an organization enrolled in the Frontier program |
| Copilot Cowork | Method used in a delegated task | Microsoft 365 Copilot tenant; work access governed by a spending policy that selects Cowork |
| Copilot in PowerPoint | Skills offered in the presentation experience | Check which features are actually available in the relevant environment |
For Agent Builder, Microsoft specifies a maximum of eight skills per agent and a maximum ZIP file size of 50 MB per skill in its instructions for adding skills. Cowork accepts up to 50 custom skills and allows you to create them through a guided conversation or import them under Customize > Skills, as its documentation explains. These limits apply to different environments: they are not interchangeable.
Microsoft advises against using custom Excel skills in a production Copilot extension. To put PowerPoint and Cowork use cases in context, see our comparison of Copilot skills by application.
Practical example: make client project reports more reliable
Imagine an export containing projects, their owners, budgets, dates and statuses, accompanied by a pricing table. The expected procedure is to standardize formats, match prices, calculate the requested metrics and produce a readable report. The agent must neither invent a missing price nor claim to have modified the workbook if it could not write to it.
Before writing the skill, establish the business rules the workbook cannot infer: which field to use to match the pricing table, how to handle a missing value, and which columns the output should contain. Without these decisions, two runs may appear consistent while answering different questions.
A test request can be brief because the method is contained in the skill:
1À partir de cet export de projets et de la grille tarifaire fournie, effectue le bilan de santé des projets clients. Signale toute donnée manquante et précise quelles modifications ont réellement été écrites dans le classeur.Test the resulting artifact, not just the conversational response: new columns, formats, matches and cases without a price. The Microsoft engineering documentation for Excel specifically recommends requesting that the result be written to the workbook, prohibiting the invention of missing data, and not reporting a change that could not be made as complete. A broader agent could use this report alongside other tasks; our guide to Copilot agent maturity levels helps frame that distinction.
Implementation
The script below prepares a local folder for a project-reporting skill and its SKILL.md. It does not publish anything to Microsoft 365. No external PowerShell module or installation is required for this local preparation; the minimum permission needed is write access to the working directory. The expected output is first a preview without writing, then, after changing $DryRun, the path of the created file.
Prepare a client-project-health-check folder and a file named SKILL.md containing the instructions for your procedure. To test it in Excel, place them in the dedicated OneDrive location for Excel skills, enable custom skills in the relevant interface, then refresh the list. For Agent Builder, prepare the ZIP package required for import; check its structure before submitting it.
The length check in this script applies to the instructions, in line with the limit specified for declarative agents; it does not, by itself, validate whether the package is compatible with each application. For Agent Builder, importing a custom skill and creating one with natural language are described in the Microsoft Learn instructions.
Check the import, the results and any blockers
The cited resources establish no specific propagation time: do not plan around a fixed wait. After adding the skill, refresh the skill list in the target application, then test it with non-sensitive data and an easily verifiable result.
Check the prepared file
Check its name, description and instructions before importing it. A local check does not prove that the application will accept the package.
Import it into the chosen environment
Use the location expected by Excel or the import option provided by Agent Builder or Cowork. Do not assume that a skill present in one environment is automatically deployed to the others.
Compare the output with the inputs
Confirm that the skill appears, that the test request activates it, and that the reported changes actually exist in the workbook. Examine at least one row without a matching price.
After running the script in write mode, this second check, which can be copied independently, confirms that the file and expected identification fields are present:
1$path = [System.IO.Path]::Combine($PWD.Path, 'client-project-health-check', 'SKILL.md')2if (-not [System.IO.File]::Exists($path)) {3 throw "Fichier introuvable : $path"4}5$contents = [System.IO.File]::ReadAllText($path)6if (-not $contents.Contains('name: client-project-health-check') -or7 -not $contents.Contains('description:')) {8 throw 'Nom ou description introuvable dans SKILL.md.'9}10"Contrôle local réussi : $path"| Symptom | Likely cause | Resolution |
|---|---|---|
| The Excel skill does not appear in the list | Folder or file in the wrong location, custom skills not enabled, or preview environment not eligible | Check the expected location, enable the feature, check the channel and version, then refresh the list |
| Agent Builder does not select the skill | Description too vague or ambiguous agent instructions | Clarify the activation criteria and test a request that explicitly mentions the skill |
| The report claims the workbook was modified, but no change is visible | The environment did not write the result or the skill does not require it clearly enough | Check the workbook and strengthen the instruction to verify that changes were written |
| Cowork is inaccessible | Spending policy does not select Cowork or the limit has been exhausted | Ask the authorized team to check the policy and its limit |
Frequently asked questions
Are both Cowork and declarative agent skills generally available?
No. Cowork has been generally available since June 2026 for Microsoft 365 Copilot tenants, while custom skills added to declarative agents remain in Frontier preview. Check access to Cowork and your organization’s eligibility for Frontier separately.
Do you need a particular license to add a skill in Agent Builder?
Yes: Microsoft specifies an eligible Microsoft 365 Copilot license or access to pay-as-you-go billing, as well as an organization enrolled in the Frontier program. For custom Excel skills, the version and Insider channel requirements must also be checked alongside your access rights in the environment.
Does the same skill automatically work in Excel, Cowork and Agent Builder?
No. The approach and instructions can be reused, but each environment has its own way of adding skills and its own constraints. Import and test the skill separately, particularly if it must write to a workbook.
Does a skill guarantee lower credit consumption?
No. Formalizing the procedure can reduce repeated explanations and make it easier to select, but the available information does not guarantee credit savings. Since Cowork became generally available, work access has depended on a spending policy that selects Cowork; according to the Microsoft governance documentation, a one-credit limit allows access until that credit is exhausted.
Start with a testable skill
Choose a procedure whose inputs you know and whose output you can verify. If your goal is a production Excel extension, do not base its deployment on custom Excel skills while they remain in preview and Microsoft advises against them for that use; start with a controlled test instead.
Before expanding use
- Define the task, its required inputs and the cases where the skill should not apply.
- Review
SKILL.mdand any resources or scripts added to the folder. - Confirm the license, preview program or spending policy for the target environment.
- Test the import, activation and actual changes using a controlled dataset.
- Document any discrepancies before reusing the skill elsewhere.
Further reading
- Customize Copilot Cowork and manage its skills — for creation, import and management in Cowork.
- Add a skill to an agent with Agent Builder — for prerequisites and import limits.
- Reference for custom skills in declarative agents — for the folder format and its restrictions.
- Create skills for Copilot in Excel — for compatible versions and precautions when writing to a workbook.



