Most Copilot users are still at the prompt stage: you type a request, read the response, move on. It's useful, but it's the bare minimum. Those who get truly different results have started transforming their repetitive work — the Friday status slide, the month-end variance explanation, the brief before a client call — into skills that Copilot executes the same way every time. This article is for Microsoft 365 administrators and engineers who want to industrialize these tasks rather than re-prompt them each week.
What is a Copilot skill
Under the hood, a skill is just a text file: a name, a description that clarifies when to use it, and a set of instructions. No code, no macros, no add-ins. Copilot reads the description and knows by itself when to tap into the skill if your prompt matches what it describes.
The distinction from a standard prompt comes down to one sentence: a prompt tells Copilot what you need now, a skill teaches it how you do the work. Think of the decision tree of your usual process: high-level instructions are general rules, but some branches require a very specific method, domain vocabulary, particular weighting. That's exactly where a skill comes in, applied systematically to that type of task.
What changed recently is where these skills can run. They already existed in Copilot Cowork; they are now also natively available in Copilot for PowerPoint and Copilot for Excel.
Three execution environments, three billing models
Choosing where to build a skill isn't just a matter of convenience: it's also a matter of cost. According to Microsoft documentation on Copilot credits, services currently subject to consumption-based billing are Cowork, applications built with Cowork, and the Work IQ API, with other services coming. Copilot in PowerPoint and Excel are not among them: these two uses are covered by the standard Microsoft 365 Copilot license.
| Environment | Billing mode | Typical use case |
|---|---|---|
| Copilot in PowerPoint | Included in Microsoft 365 Copilot license | Build, correct, and revise slides |
| Copilot in Excel | Included in Microsoft 365 Copilot license | Analyze, explain, clean, and verify a workbook |
| Copilot Cowork | Consumption-based billing, in Copilot credits | Multi-step tasks involving multiple applications, multiple sources, and multiple deliverables |
The practical rule to remember: use what your license already covers first. No need for Cowork to edit a presentation or explain a spreadsheet. Reserve Cowork for work that normally requires someone to navigate between multiple applications, aggregate data from different sources, and produce more than one deliverable. That's where the credits are justified.
Identifying skills already delivered by Microsoft
Before building anything, inventory what already exists. Open the Copilot pane, select the + in the prompt area, then Choose skills in PowerPoint or Choose plugins & skills in Excel. You can also type @ and choose a skill directly from the dropdown list.
Some built-in skills worth knowing:
- PowerPoint — Explain this presentation : opens a 20-slide deck you've never seen and returns an impartial guide (key messages, inconsistencies, jargon to know). Useful before any meeting where someone sends you a deck an hour in advance.
- PowerPoint — Visualize this slide : transforms a dense text slide into a polished visual. Adding your own brand guidelines in the prompt brings the result much closer to your standard.
- PowerPoint — Review this presentation and Prepare for questions : the first tests narrative structure, the second anticipates audience questions.
- PowerPoint — Sharpen slide titles : rewrites thematic titles into actionable conclusions.
- Excel — brandkit and theme-design : enabled by default; chart-design : must be enabled manually, per Microsoft documentation on Excel skills.
- Excel — Finance folder : depending on the tenant, a Finance folder offers skills like 3-statements, check-model, comps-analysis, dd-meeting-prep, lbo-model, or unit-economics, disabled by default.
The exact list varies from tenant to tenant and evolves constantly: consider your own skill menu as the only reliable source.
Tip
Built-in descriptions are often too terse. Ask Copilot directly "what is this skill for?" before using it blindly.
To enable or disable a skill, open the three dots of the Copilot pane then Manage plugins & skills. Disabling a skill prevents Copilot from triggering it automatically. In PowerPoint, it also disappears from the menu; in Excel, it remains callable via an @ mention.
The five criteria that distinguish an actionable skill
A basic skill does a single shot: "summarize this." A good skill does the work. Five principles come up consistently in the most useful skills:
- It works in steps : read, analyze, produce, verify — never a single blind pass.
- It asks before assuming. This is the biggest quality gain: a few clarifying questions before any production.
- It anchors in reality : the deck, the workbook, your exchanges. Missing information becomes an explicit marker in brackets, never an invented figure.
- It produces a concrete deliverable without overwriting the original : a finished slide, a new sheet, an email draft — never an automatic send without validation.
- It self-checks before handing over, rereading with a skeptical eye ("reread this like a CFO looking to say no") to correct the weakest point.
This last criterion makes all the difference between a result you keep as-is and one you have to rewrite entirely.
The step that changes everything: customize before deploying
Any skill delivered "out of the box" is written for a generic person doing generic work — so it gives a generic result. Value appears when the skill aligns with your actual context: your role, your audience, your format, your brand, your data, your guardrails.
The principle is simple: never upload the basic skill as-is. Customize it first, and let Copilot build the final file.
Copy the basic skill
Retrieve the text of the basic skill you want to adapt (see the two examples below).
Launch the customization prompt in Copilot Chat
Open Copilot Chat — not Cowork, whose "low cost" banner recommends handling this type of task in Chat rather than credits — then paste the customization prompt below, inserting the basic skill.
1I want to transform a basic Copilot skill into a customized skill. It will run in [PowerPoint / Excel / Copilot Cowork].2 3Here is the basic skill:4[paste the basic skill here]5 6Before writing anything, interview me. Ask me up to 8 discovery questions, a few at a time, covering:7- my role and the work this skill supports8- who the result is for and what matters to that audience9- what an excellent result looks like to me, with a past example if I have one10- my format, my template, my brand guidelines or house style11- the files, data, or sources it should use, and those it should ignore12- the terms, metrics, and thresholds that matter in my work13- what it must never do14 15Then rewrite the skill around my answers. Keep the step-by-step flow, the clarification questions step, the final self-check, and the rule of never inventing a fact, figure, name, or quote.16 17Deliver it as a SKILL.md file ready to upload. Start with a header with a short lowercase-and-dashes name and a description specifying exactly when to use the skill, then the instructions in markdown. Give me a download link or code block I can copy into a .md file.Answer Copilot's questions
Copilot interviews you before writing anything: role, audience, format, business thresholds, prohibitions.
Retrieve the SKILL.md file
Download the file returned by Copilot: it's your customized skill, ready to deploy.
Deploy the skill where it needs to run
Follow the procedure specific to each application, detailed below.
Test on a real case
Execute the skill on a real deck or real workbook, then tell Copilot what needs to be tightened before sharing it with the team.
Common pitfall
In PowerPoint and Excel, the name of the skill folder must match exactly the name indicated at the top of the SKILL.md file. If the two don't match, Copilot silently ignores the skill. Cowork is more forgiving, but adopting a lowercase-and-dashes convention everywhere (for example executive-summary-slide) makes the same file reusable across all three environments.
In Excel, two additional customization layers complement your skills: Personalization, accessible via the three dots then Customize Copilot, where you set once-and-for-all rules like currency format, negative number display, or fiscal year start; and workbook rules, created via the + then Create workbook rules, which add a .Rules sheet traveling with the file, guaranteeing the same standards to anyone sharing the workbook.
Anatomy of a SKILL.md file
Every well-built skill follows the same structure, the one Copilot automatically generates after customization.
| Section | Role |
|---|---|
| Name | Short lowercase name, for example customer-success-slide |
| Description | Specifies when to use the skill — this is what Copilot reads to trigger it automatically |
| Inputs | What you provide, and what to do if information is missing |
| Workflow | The ordered sequence, including clarification questions |
| Rules | What the skill must always do, and what it must never do |
| Output | Exactly what you get in return |
| Self-check | The critical review done before handing over |
Two basic skills ready to customize
Here are two complete skills, one for PowerPoint and one for Excel, that you can copy as-is and then run through the customization prompt above.
PowerPoint: executive summary in one slide
The classic problem: a 25-slide deck and an executive who will only look at one slide. This skill reads the entire deck and builds that single slide, conclusion first.
1Name: executive-summary-slide2Description: use when I ask for an executive summary, a one-slide summary, a BLUF (Bottom Line Up Front) slide, or a summary slide for leadership from the current presentation.3 4Inputs:5- The current presentation.6- Optional: the target audience and the decision or action expected. If not specified, ask before building.7 8Workflow:91. Read the entire presentation and identify the most important message.102. Ask who the audience is and what is expected of them, if not already specified.113. Create ONE new slide at the beginning of the deck, just after the title page.124. Title the slide with the conclusion, phrased as a complete sentence, not as a topic. Example: "We need to expand the pilot to three regions in Q3" rather than "Pilot summary."135. Below the title, add three supporting points, each with the strongest evidence drawn from the deck.146. Add at the bottom a short "Expected decision" line that specifies exactly what is being asked.157. Respect the existing theme, fonts, and colors. Do not modify any other slides.16 17Rules:18- Use only facts, figures, and statements present in the deck. If important information is missing, insert a marker in brackets, for example [ADD COST ESTIMATE].19- Keep each supporting point to two short lines.20- Direct, sober language, without flourish.21 22Output:23- An executive summary slide.24- In the chat, a line flagging any contradiction between the summary and the rest of the deck.25 26Self-check:27- Before finishing, reread the slide as a busy, skeptical executive would. If the conclusion isn't obvious in five seconds, rewrite the title.Prioritize customizing: your usual audiences and what matters to each, your template and summary layout, how you phrase recommendations, and your length limits.
Excel: turn data into narrative
A figure doesn't explain itself, and "here's the Excel file" is not an update. This skill reads the data and writes the narrative behind it, with calculations to back it up.
1Name: data-to-narrative2Description: use when I ask what this data tells us, explain the figures, summarize a sheet, or write the narrative for a report from this workbook.3 4Inputs:5- The designated sheet or table.6- Optional: the question I'm trying to answer and the recipient of the narrative. If unclear, ask.7 8Workflow:91. Confirm what the data represents and the question being asked. For any ambiguous column or field, ask rather than guess.102. Identify the 3 most important pieces of information the data reveals.113. Identify the drivers: what moves the figures, with the precise values behind each claim.124. Flag anomalies and outlier values to watch.135. Create a new sheet named "Narrative" containing: a title section, the drivers with supporting figures, anomalies, a "implications" section with 2 decisions or questions this raises, and a short written narrative ready to paste into a report.146. If useful, add a summary chart to the Narrative sheet, built from actual data.15 16Rules:17- Do not modify the original data.18- Show the calculation: each claim points to the figures backing it.19- Never invent a figure or fill a gap with an assumption. Flag it explicitly.20 21Output:22- A new Narrative sheet, plus a one-paragraph summary in the chat.23 24Self-check:25- Before finishing, reread the narrative as the owner of these figures would. Flag any claim they would contest, and back it up or nuance it.Prioritize customizing: the type of data handled, your metrics and targets, the recipients of your narratives, your reporting format and preferred chart types.
Deploying the skill in each application
The upload procedure differs depending on the execution environment:
- PowerPoint : three dots in the Copilot pane → Manage plugins & skills → Custom skills → Add skill → Upload the file. It is also possible to choose Create manually and paste the content directly into the form.
- Excel : three dots → Manage plugins & skills → Custom skills. Excel retrieves custom skills from a OneDrive "Skills" folder: save the file in a subfolder with exactly the skill's name, then click Refresh.
- Cowork : Customize → Skills tab → Add then Upload skill, or New skill for guided creation. Per Microsoft documentation on using Copilot Cowork, a tenant can host up to 50 custom skills.
Tenant-wide impact
Deploying a custom skill in Cowork or a shared Skills folder makes it available to anyone with access. Validate its behavior on a real case first and verify that no sensitive information is hard-coded in the instructions before sharing it across your team.
Troubleshooting: the most common errors
- The skill doesn't appear in the PowerPoint menu : verify it's enabled in Manage plugins & skills — a disabled toggle removes it from the menu.
- Excel ignores the custom skill : the OneDrive subfolder name probably doesn't match exactly the name declared in the SKILL.md file. Correct the name then relaunch Refresh.
- Copilot never triggers the skill spontaneously : the description is too vague. Rephrase it with the exact vocabulary you actually use in your prompts.
- The result contains an invented figure : verify that the rule "never invent a figure" appears explicitly in the Rules section, and that the self-check step is present in the Workflow.
Key takeaways
This first installment covers two complete, customizable skills out of fourteen planned (four more for PowerPoint, three more for Excel, five for Cowork) — the customization and deployment method, however, applies identically to all twelve remaining.
- Start by inventorying the built-in skills in your own tenant before building anything.
- Never upload a basic skill as-is: always go through the customization prompt, in Copilot Chat rather than Cowork.
- Reserve Cowork for multi-application tasks with multiple deliverables, to avoid consuming credits on tasks your Microsoft 365 Copilot license already covers.
- Name your skills in lowercase and dashes so they work seamlessly in PowerPoint, Excel, and Cowork.
- Test each skill on a real case before sharing it with your team.
If your organization rebuilds the same type of deliverable each week — status slide, variance note, meeting brief — that's exactly the ideal candidate for a first customized skill before the end of the quarter.



