The non-obvious thesis
The real productivity gain from Copilot in PowerPoint is not the chat interface — it is the ability to encode repeatable deck tasks as @-mentionable skills that Copilot can invoke automatically or on demand. A single well-written SKILL.md file replaces the same prompt you type dozens of times a month. Yet the mechanism is buried three menus deep, and one underdocumented name-matching rule silently breaks most first attempts. This playbook surfaces both.
Skills are only available if your Microsoft 365 subscription includes Copilot in PowerPoint, and only on PowerPoint for Microsoft 365, PowerPoint for Microsoft 365 for Mac, and PowerPoint for iPad. Confirm your licence before going further. Learn which Copilot licence you have.
Prerequisites before you write a single skill
Three things must be true before step one:
- Copilot is visible in the PowerPoint ribbon. Open any deck and look for the Copilot button. No button means no skill support yet — resolve the licence question first.
- OneDrive is connected and syncing. Custom skills are stored in a specific OneDrive folder. If OneDrive is paused or blocked by your IT policy, skills will not persist.
- You have a well-scoped, repeatable task in mind. Skills work best on tightly defined requests — “create an executive summary slide matching the deck’s design” rather than “make this presentation better”. Vague scope produces inconsistent results regardless of how well the SKILL.md is written.
Follow the steps below in order. Skipping the folder-creation step is the single most common reason a skill never appears in the menu.
Step 1 — Create the OneDrive skills folder
Open the Copilot pane in PowerPoint. Select the … menu in the upper-right corner, then choose Manage skills → Custom skills → Create OneDrive folder. Copilot provisions the folder automatically. Select Open skills folder to confirm it exists. Do not rename or move this folder — Copilot resolves skills relative to this exact path, and relocating it breaks all skills silently.
Step 2 — Author your SKILL.md file
Every custom skill needs its own subfolder inside the skills folder, and that subfolder must contain a file named SKILL.md. The folder name and the name field inside the file must match exactly — including hyphens and capitalisation. A single character difference causes Copilot to silently skip the skill with no error or warning.
The SKILL.md format follows the Agent skills specification at agentskills.io. It has two required parts:
- Frontmatter (between
---delimiters): holdsnameanddescription. Write the description as a trigger condition — it tells Copilot when to invoke the skill automatically. A description written as a title rather than a condition reduces automatic invocation reliability. - Body: plain instructions telling Copilot how to complete the task. No format restrictions apply. Numbered steps, prose or a mix all work.
Here is the example Microsoft supplies for an executive-summary skill:
--- name: create-executive-summary-slide description: Use when I ask Copilot to create executive summary slide of a given deck. After the summary is created, add it to a new slide. --- # Create Executive Summary When Copilot creates executive summary content, add it to a new slide and follow the design style of existing presentation. ## Steps 1. Create the summary as requested. 2. Analyze design style of existing deck. 3. Add summary in new slide but following existing presentation design style
The description here doubles as an automatic-trigger sentence. When you later type a prompt that matches that condition, Copilot can invoke the skill without an explicit @mention.
Step 3 — Upload the skill and verify it appears
Three upload paths are available. Choose the one that fits your workflow:
- Drag-and-drop inside Copilot: In the Copilot pane, select + → Choose skills, scroll to the bottom, select Manage skills → Add skill. Drag your skill file or ZIP directly into the upload area. Copilot saves it to OneDrive automatically.
- Paste via the Add skill form: Same navigation path as above, but copy-paste the skill content into the form field instead of uploading a file.
- Drop directly into OneDrive: Place the correctly named folder and SKILL.md into the skills folder in OneDrive, then select Refresh in the Custom skills dialog. Without the Refresh step, Copilot will not detect the new skill.
After uploading, open the Choose skills menu and confirm the skill appears. If it does not, select Refresh in Manage skills. Still missing? Verify the folder name matches the name field in SKILL.md exactly — including hyphens and capitalisation.
Important limitation: custom skills uploaded this way are for your personal use only. They are not automatically shared with colleagues via the same upload path. Teams seeking consistent output across multiple users will need to distribute the SKILL.md files separately and have each person upload them individually — or wait for organisational-level deployment options.
Step 4 — Invoke and test the skill
Type @your-skill-name in the Copilot prompt field to call the skill explicitly, or select it from the Choose skills dropdown before submitting your prompt. Test against a real deck, not a blank file — skills that reference design style or existing slide content need actual slides to analyse. A blank file produces misleading results and makes a working skill appear broken.
Toggle the skill off in Manage skills if you want to prevent automatic invocation while you refine the instructions. A toggled-off skill disappears from the dropdown and from automatic invocation — it is not deleted.
Common failure modes
Four problems account for most broken skills:
- Name mismatch: The folder name and the
namefield in SKILL.md differ. Copilot skips any folder whose name does not match its internal name declaration — no error is surfaced. - Missing frontmatter delimiters: Forgetting the opening or closing
---breaks the metadata parse. The skill may upload without error but will not trigger correctly. - Unsupported file types in a ZIP: Supported types include md, txt, csv, json, xml, html, svg, py and js. PNG, PDF and nested ZIP folders are not currently supported — remove them before packaging.
- OneDrive sync lag: Skills added directly to OneDrive do not appear until you select Refresh in the Custom skills dialog. This is easy to miss and looks identical to a failed upload.
The fair counterpoint
Skills are currently personal, not shared across a team via the same upload path. A manager hoping to standardise output across a whole team today will find the leverage limited — each person must upload their own copy of the skill. That is a real constraint, not a reason to delay individual adoption, but it should inform expectations about team-wide ROI before deployment begins.
Implementation checklist
- ☐ Confirmed Copilot is visible in PowerPoint ribbon
- ☐ OneDrive connected and syncing
- ☐ Skills folder created via Manage skills → Custom skills → Create OneDrive folder
- ☐ Subfolder named to match intended skill name exactly
- ☐ SKILL.md authored with frontmatter (
name+descriptionas trigger condition) and body instructions - ☐ Skill uploaded via preferred method
- ☐ Skill confirmed visible in Choose skills menu (Refresh if not)
- ☐ Skill tested with @mention against a real deck with existing slides
- ☐ Toggle behaviour confirmed in Manage skills
Your one next action: list the five prompts you type most often in Copilot for PowerPoint. Any prompt you repeat more than twice a week is a skill candidate. Take the most frequent one, write it as a SKILL.md file with a trigger-condition description, and upload it using the drag-and-drop method. The name-matching rule is the only thing that will stop you — get that right and you will have a working, @-mentionable skill before your next deck is due.
Eagentix helps growth-focused enterprises redesign and automate manual business processes. We combine executive strategy, implementation support, and managed services to build dependable operations across Southeast Asia.