Your emails and Teams messages already contain everything Copilot needs to stop writing like a generic assistant: Copilot can write a style file itself, which you then plug into an agent. One pitfall has changed since the first tutorials: Microsoft now asks for a .zip package, not a standalone skill.md file. This guide takes you from generating the file to checking the result, with two alternatives for Outlook drafts.
A style skill: what it is and what has changed
A skill is a SKILL.md file that describes a reusable capability for an agent. Here, the capability is your way of writing: voice, tone, terminology, formatting rules. Skills follow an open specification, Agent Skills: according to the Microsoft Copilot Studio documentation, the same SKILL.md works in Copilot Studio, Cowork, VS Code and other tools. Your style is therefore not locked into a single agent.
Preview: a .zip package, not a single file
As of 3 October 2026, adding custom skills in Agent Builder is still in preview. The Microsoft Learn documentation asks you to upload a complete .zip package containing a mandatory SKILL.md file, and states that you should not upload SKILL.md on its own. Tutorials that show uploading a simple skill.md file are therefore out of date.
Two constraints from the documentation matter for what follows: the YAML header of SKILL.md must contain a name and a description, and the instructions must stay under 20,000 characters. The file generated by Copilot does not necessarily have this header: we will check it in step 2.
Prerequisites
What to gather before you start
- A Microsoft 365 Copilot licence (required for skills, according to the Microsoft Tech Community post on skills in PowerPoint)
- Access to Microsoft 365 Copilot with the Agents section and the agent builder (Agent Builder)
- A sufficient history of sent emails and Teams messages: the richer it is, the more reliable the style profile
- A text editor to review and correct the generated file
- Optional: PowerShell 5.1 or 7 to automate the packaging ("Implementation" section)
- Acceptance of a preview feature, whose behaviour may change
Create your style agent, step by step
Ask Copilot to describe your style
Open Microsoft 365 Copilot chat and paste the prompt below. It asks Copilot to analyse your messages from the last two years and produce the file. The last sentence avoids the header problem mentioned above.
1If you look at the emails I have sent or replied to, as well as my Teams messages from the last 2 years, can you define my voice, style, tone, terminology and formatting rules? Create a SKILL.md file based on your findings that I can use as a reference to create content in my style. The file must start with a YAML header containing the fields name (kebab-case) and description.You should see Copilot summarise your dominant traits (for example: practical rather than theoretical, direct, conversational, rich in examples), then offer a file to download further down in the response.
Download the file, review it and correct it
Download the file and open it in a text editor. Check three points: the YAML header with name and description, the absence of colleagues' names or confidential information drawn from your exchanges, and a description rich in trigger phrases ("write an email", "prepare a document"). Rename the file to SKILL.md.
Package the skill as a .zip
Create a folder whose name is identical to the name field of SKILL.md, place the file in it, then compress the folder into a .zip. This name match is detailed in the "If something goes wrong" section. The script in the "Implementation" section does these operations for you.
Launch the agent builder
In Microsoft 365 Copilot, hover over the Agents section in the left pane, then select the option to create a new agent, at the bottom of the list. The agent builder opens. To understand where this building block sits among the other types of agents, see our article on the 4 levels of mastery of Microsoft 365 Copilot agents.
Describe the agent in one sentence
Paste a message like this: "This agent creates content for me using my brand style file. It offers options for creating emails, Word, Excel and PowerPoint documents, and every result uses my voice. Offer only one option at a time and, once a suggestion is selected, ask whether there are additional details or attachments."
After a few seconds, Copilot generates an agent (for example "Brand voice studio") with a description, instructions and prompt suggestions.
Customise the name and image
Click the edit icon next to the title and enter a meaningful name, for example "My voice". Then click the agent's edit icon to generate an image with AI, browse images or upload one, then select Apply. The new title and image appear at the top of the configuration.
Simplify the instructions
The generated instructions work as they are. You can also replace them with your initial prompt, which is shorter and more readable: the agent keeps the name, description and suggestions already produced.
Delete the automatically generated skill
At the top of the configuration, find the custom skill that Copilot created on its own. Click the three dots, then delete: you want your own file, not an improvised version.
Add your skill
In the skills section, select Add, then Browse, and choose your .zip package. If the file does not appear in the window, display all files in the file type filter. Click Open then upload.
You should see the name of your skill appear in the list, with no error message.
Set the knowledge settings
In the knowledge section, click the cog. Turn on the option that prevents the model from using its own knowledge, so that it relies on your emails, your Teams messages and your files. Also check image and document creation, as well as access to your organisational and personal data. Leave the Outlook and Teams settings at their defaults.
Create the agent and pin it
Click Create at the top, then Start chatting. Then go back to the Agents section, hover over "My voice" and select Pin: the agent stays visible in the left pane.
Checking the result
The agent shows four starter prompts: email, Word, Excel and PowerPoint. Run the email one without context: a well-tuned agent replies that it needs details before writing. Then give it a concrete instruction, for example "Write an email to Albert and highlight the key points of this document", attaching a file via the plus sign.
The draft should reuse your usual turns of phrase. You can ask "Did you use my usual tone?": Copilot then cites the characteristics applied (warm, direct, action-oriented). Keep in mind, however, that a self-assessment proves nothing: compare the draft with three or four real messages from your sent items. To then refine the file through iterations, our article on skills, feedback and iteration in Copilot details the approach.
A style file can contain personal data
The file comes from your real exchanges. Review it before sharing it, and if you store it in SharePoint, be aware that the Agent Assets library inherits the site's permissions: according to the Sharepoint Maven post, any member of the site can then edit or delete a SKILL.md.
Two alternatives without a dedicated agent
The agent is not the only route. Two other places accept the content of your file, with a different scope.
| Method | Scope | Where to configure it | File format |
|---|---|---|---|
| Agent with skill | Only when you use this agent | Microsoft 365 Copilot > Agents > Create an agent | .zip package with SKILL.md |
| Custom instructions | The requests you send to Copilot | Cog > Settings > Personalisation > Custom instructions | File content pasted as text |
| Outlook draft instructions | Emails created in Outlook | Outlook > three dots at top right > Settings > Copilot > Draft instructions | File content pasted as text |
For custom instructions: select Edit instructions, paste the whole content of the file, click Save instructions and check that custom instructions are turned on. For Outlook: open the draft instructions, turn them on, paste the content and save. Every new email will then use this style.
If you are unsure: the agent offers the best control (knowledge, documents, suggestions), custom instructions apply everywhere but are less tested, and Outlook targets email precisely.
Implementation: packaging the skill with a script
To repeat the operation across several profiles or several tenants, this PowerShell script builds the folder, generates the YAML header and creates the .zip. It requires no module and needs no Microsoft 365 permission: it works only locally. As output, you get a folder named after the skill and a .zip file of the same name. The -DryRun mode checks the constraints without writing anything.
1# Save this script as New-SkillPackage.ps12param(3 [Parameter(Mandatory)][string]$Name,4 [Parameter(Mandatory)][string]$Description,5 [Parameter(Mandatory)][string]$InstructionsPath,6 [string]$OutputFolder = '.',7 [switch]$DryRun8)9 10# 1. Checks : nom en kebab-case (1 à 64 caractères), description de 1 à 1024 caractères11if ($Name -cnotmatch '^[a-z0-9]+(-[a-z0-9]+)*$' -or $Name.Length -gt 64) {12 throw 'Le nom doit être en kebab-case (minuscules, chiffres, tirets) et faire 64 caractères au plus.'13}14if ($Description.Length -lt 1 -or $Description.Length -gt 1024) {15 throw 'La description doit faire entre 1 et 1024 caractères.'16}17 18# 2. Lecture des instructions : moins de 20 000 caractères, sans en-tête YAML existant19$body = Get-Content -Path $InstructionsPath -Raw20if ($body.Length -ge 20000) { throw 'Les instructions dépassent 20 000 caractères.' }21if ($body.TrimStart().StartsWith('---')) { throw 'Retirez l''en-tête YAML existant : le script en génère un.' }22 23# 3. Construction de l'en-tête YAML (apostrophes doublées pour rester valide)24$apos = [string][char]3925$descYaml = $Description.Replace($apos, $apos + $apos)26$lines = @(27 '---',28 ('name: ' + $Name),29 ('description: ' + $apos + $descYaml + $apos),30 '---',31 '',32 $body33)34 35$skillDir = Join-Path $OutputFolder $Name36$zipPath = Join-Path $OutputFolder ($Name + '.zip')37 38# 4. Mode simulation : on s'arrête avant toute écriture39if ($DryRun) {40 Write-Host ('Simulation OK : ' + $skillDir + ' puis ' + $zipPath)41 return42}43 44# 5. Le dossier porte exactement le nom du champ name ; le fichier s'appelle SKILL.md45New-Item -ItemType Directory -Path $skillDir -Force | Out-Null46Set-Content -Path (Join-Path $skillDir 'SKILL.md') -Value $lines -Encoding UTF847 48# 6. Création du paquet .zip49Compress-Archive -Path $skillDir -DestinationPath $zipPath -Force50Write-Host ('Paquet créé : ' + $zipPath)Example of a call in simulation mode:
1./New-SkillPackage.ps1 -Name 'ma-voix' -Description 'Style d''écriture personnel. À utiliser quand je demande de rédiger un e-mail, un document ou une présentation.' -InstructionsPath './instructions.md' -DryRunAgents Toolkit: a folder, not a .zip
If you add the skill via Agents Toolkit, the Microsoft documentation states that the .zip is not accepted: a folder is required. Each agent is limited to 8 skills and the complete package to 10 MB. The feature requires version 1.9 of the declarative agent manifest and remains in preview. Check the exact structure expected on the page Add custom skills to your declarative agent in Agent Builder (preview).
If something goes wrong
- The file does not appear in the Browse window. Display all files in the file type filter, then select the package.
- The skill is ignored with no error message. The folder name must match the
namefield of SKILL.md exactly: the Cowork documentation says this mismatch is the most common cause of failure, and the Tech Community post confirms that Copilot then silently ignores the folder. Also check that the description (1 to 1,024 characters) contains trigger phrases: a vague description prevents the skill from launching. - The import fails. Check three points: the YAML header with
nameanddescription, uploading a complete .zip package rather than SKILL.md alone, and instructions under 20,000 characters.
Where to start
Your next actions
- Generate the style file with the prompt from step 1 and review it to remove sensitive data
- Run the script in
-DryRunmode, then create the .zip package - Create the "My voice" agent and test it with three real cases: email, document, presentation
- Compare the drafts with your real messages before widening usage
If you mostly write emails, start with the Outlook draft instructions: it is the fastest setup. If you also produce Word documents or presentations, the agent with a skill is the best starting point. To go further on agent governance, read our overview of publishing, governance and skills in Agent Builder.
Going further
- Add custom skills to your declarative agent in Agent Builder (preview): the official packaging and upload procedure, with the expected format and limits.
- Skills overview for agents - Microsoft Copilot Studio: what a skill is, how it differs from instructions and knowledge, and the three ways to add one.
- How to Set Up Copilot Skills in PowerPoint (and Build Your Own): a hands-on account of the folder name and description pitfalls.
- How to create SharePoint Skills using Copilot: creating and storing skills in SharePoint, with the permission nuances.



