Copilot skills: how to get AI to work the way your firm works

Ask ten people in your firm to get Copilot to write a client proposal and you’ll get ten different documents. Different structure, different tone, some on the template and some not.

It’s the conversation I have most often with clients. Copilot can do the work. The hard part is getting it to do the work the same way every time, in your format and to your standard.

You can get part of the way by uploading your template into Copilot Chat and asking it to work from there. That works, but not very consistently. It relies on every person remembering to do it and writing a good prompt each time, and the results vary even when they do. Skills are how you make it stick. A skill captures the whole procedure, not only the template, so Copilot knows how the work should be done as well as what it should look like.

What a skill is

A skill is one of your standard operating procedures, written down in a form Copilot can find and follow.

Think about how you’d brief a capable new starter on a task you do every week. You’d explain the steps, hand over the template, point to a good example and mention the mistakes to avoid. A skill is that briefing, saved once and used every time.

Under the bonnet it’s simpler than it sounds. A skill is a folder containing:

• A name
• A short description of what the skill is for and when to use it
• The instructions, written in plain language
• Supporting files such as reference documents, examples, checklists and, in some places, templates

The instructions live in a text file called SKILL.md. There’s no code involved unless you want there to be. If you can write a clear process document, you can write a skill.

The description is the clever part. Copilot reads the names and descriptions of every skill available to it. When your request matches one, it loads the full instructions and follows them. You don’t have to remember the skill exists or paste anything in.

That’s the difference between a skill and a saved prompt. A saved prompt is something you have to go and fetch. A skill carries its files with it and Copilot picks it up when the job calls for it.

How skills improve consistency

Microsoft’s own description is that skills provide “reusable instructions or workflows that help agents perform tasks consistently” (Microsoft Learn). In practice that comes down to four things:

• The process is written once, by the person who knows it best, instead of being reinvented in every prompt.
• Everyone works from the same instructions. Skills can be shared with colleagues or rolled out by IT, so the trainee and the partner get the same starting point.
• It only loads when it’s relevant. Copilot isn’t weighed down by fifty sets of instructions on every request. It picks the one that fits.
• You improve it in one place. When the process changes, you update the skill and everyone’s output changes with it.

Two caveats. First, Copilot decides when to use a skill by reading its description, so a vague description means the skill never fires or fires at the wrong time. Writing a good description is most of the craft. In PowerPoint and Excel you can also call a skill by name with an @mention when you want to be certain.

Second, skills narrow the variation a lot but they don’t remove it. Copilot is still an AI model, so two runs will match in structure and standard without being word for word identical. It also follows your process more reliably than it reproduces exact formatting, so keep using your templates and Brand kits for the look.

Where skills work in Microsoft 365 today

Skills aren’t one feature with one switch. Microsoft has added them product by product, and each is at a different stage. This is the picture as of 9 October 2026.

Two terms worth explaining. Generally available means it’s a finished feature anyone with the right licence should have. Frontier is Microsoft’s opt-in early access programme. Your IT admin has to switch it on, and features in it can change before full release.

Recording a skill in PowerPoint deserves a mention. You carry out a task while Copilot records it, and it turns your actions into a reusable skill. It’s brand new and rough around the edges, but the idea matters: you show Copilot how you do something once, and it can repeat it.

For how skills are packaged and uploaded in each product, see Copilot skills explained.

What you need to use them

You can start without the paid Microsoft 365 Copilot licence. In my own testing, an account without it can use skills in PowerPoint and Excel and create custom ones. Microsoft’s documentation doesn’t spell this out, so check it in your own tenant. The paid licence is needed for Cowork and SharePoint.

Three more things can catch you out:

• Cowork runs on usage-based billing. Your admin has to switch it on and set a spending policy before anyone can use Cowork, and skills running in Cowork count towards that usage.
• Copilot Studio is billed separately. Agents built on the newer experience consume Copilot Credits from the first test, whatever licence the user holds.
• Agent Builder skills need Frontier. If your organisation hasn’t opted in, you won’t see them.

In SharePoint, creating and running skills is covered by the licence. Skills used in scheduled automations need credits.

So before you promise the board anything, check two things with IT: who holds a paid Copilot licence, and whether usage-based billing and Frontier are switched on.

Where this is heading

On 25 September 2026 Microsoft announced a redesigned Copilot built around three parts:

• Home brings Chat and Cowork together in one place. Microsoft says that soon you won’t need to choose between them. You’ll describe what you need and Copilot will route the work.
• Code lets anyone describe an app, tracker, dashboard or workflow in plain language and have Copilot build it.
• Autopilot is an always-on agent you give a name, a role and a goal. It keeps working when you’re not there.

Home and Code are arriving through Frontier first, and Autopilot is in private preview, so most firms won’t see them yet.

In the same announcement Microsoft said skills “enable organizations to scale best practices through reusable, role-specific workflows”. It also introduced plugins, which bundle skills and connectors together, and a central registry where IT can approve and manage them.

My prediction: skills will be a big part of Code and Autopilot. Plugins already appear in both, and plugins are how skills travel. An agent that works unattended needs to know how your firm does things, and a skill is how you tell it.

Developers got here first

None of this started with Microsoft. Anthropic introduced skills for Claude in October 2025 and published the format as an open standard two months later. Skills are now built into every major AI coding tool, including Claude Code, OpenAI’s Codex, GitHub Copilot, Cursor and Gemini CLI. The general assistants Claude and ChatGPT support them too.

That matters for two reasons.

First, the idea is proven. Software teams have spent a year writing down how they want work done and letting AI follow it.

Second, you’re not locked in. Microsoft says Cowork skills use the same open standard as those coding tools (Microsoft Learn). A skill is a folder of plain text files, so the work you put into documenting a process isn’t tied to one product.

From what I see with clients, the wider workforce hasn’t caught up yet. Most Copilot users have never heard of skills. That’s the opportunity.

What to do now

You don’t need Frontier or the new Copilot to get started. The preparation is the same whatever Microsoft ships next.

1. List your repeatable tasks. Proposals, engagement letters, board packs, client updates, monthly reports. Anything your team produces again and again.
2. Pick the ones where consistency matters. Look for tasks with a clear right way of doing them and a visible cost when someone does them differently.
3. Write the procedure down. If the SOP only exists in someone’s head, this is the real work. Steps, template, a good example and the common mistakes. There’s more on what that document needs in from SOP to agent.
4. Turn it into a skill. Start where you already have access. For most firms that’s PowerPoint or Excel, where you don’t need the paid licence to begin.
5. Test it with real requests. Ask for the task the way your colleagues would. If Copilot doesn’t pick up the skill, fix the description.
6. Share it and give it an owner. A skill is a living document. Someone needs to keep it current when the process changes.

The firms that write it down will get ahead

The quality of what AI produces for your firm is going to depend less on who writes the best prompt and more on how well you’ve documented the way you work. Skills are where that documentation lives.

The firms that map their procedures now will be ready as each new piece of Copilot arrives. The ones that wait will still be getting ten different proposals.

If you’d like help working out which of your processes should become skills, and building them, get in touch with us at FiveForward.

Product details checked on 9 October 2026. Copilot changes quickly, so confirm what’s available in your own tenant.