Add post: Modern Agents Have Skills Now in Copilot Studio by Roelzz · Pull Request #329 · microsoft/mcscatblog

Roelzz · 2026-06-15T18:50:45Z

Summary

New post introducing Skills in modern Copilot Studio agents: an on-demand procedural layer based on the Agent Skills open format.
Covers why builders should care (manageability, context window, sometimes accuracy), the add/invoke UX, how Copilot Studio Skills differ from coding-agent Skills, how Skills tighten the agent loop and direct tool use, and when to use Skills vs instructions.
Two Mermaid diagrams (on-demand selection, Skills-vs-instructions decision path) and three screenshots.

Checklist

Ran /review-post and addressed feedback
Local server renders correctly (./tools/run.sh)
All images have alt text and captions
2-3 internal links to related posts
Tags chosen for Chirpy "Further Reading" overlap

…tudioNow Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

microsoft-github-policy-service · 2026-06-15T18:50:58Z

@Roelzz please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

github-actions · 2026-06-15T18:51:57Z

Blog preview check passed for 08a8f5e.

The Jekyll site compiled successfully. No newly added _posts/*.md files were detected in this PR.

adilei

Thanks!

adilei · 2026-06-15T20:26:35Z

+mermaid: true
+---
+
+Enterprise agents rarely fail for lack of facts. They fail because the organization has a specific way of doing the work, and that procedure ends up scattered across one ever-growing system prompt. Modern agents have a cleaner place to put it: **Skills**.


It's a nice intro but "rarely fail" is a little clickbaity and somewhat untrue :)

adilei · 2026-06-15T20:29:03Z

+
+Enterprise agents rarely fail for lack of facts. They fail because the organization has a specific way of doing the work, and that procedure ends up scattered across one ever-growing system prompt. Modern agents have a cleaner place to put it: **Skills**.
+
+If you have spent time with coding agents recently, you have probably already met them. A Skill is a small, self-contained package of procedural knowledge: a `SKILL.md` file with a name, a description, and instructions that tell the agent how to do a specific kind of task. The agent loads it only when a task actually needs it.


I think this is too soon to introduce "procedural knowledge". It's a loaded term that should be explained, probably later?

adilei · 2026-06-15T20:30:13Z

+
+Skills are based on the [Agent Skills open format](https://agentskills.io/), an open standard originally developed by Anthropic. The shape is deliberately simple, but the benefits are real:
+
+- **Manageability.** Instead of one ever-growing instruction blob, each procedure lives in its own focused Skill. You can reason about, review, and version them one at a time.


Again, procedure. Better to frame skills as instructions (which is what they are) and talk about procedural knowledge in the section that dicusses when to use skills

adilei · 2026-06-15T20:31:42Z

+
+- **Manageability.** Instead of one ever-growing instruction blob, each procedure lives in its own focused Skill. You can reason about, review, and version them one at a time.
+- **You avoid saturating the context window.** Skills load *on demand*. The agent keeps only the names and descriptions in view by default, and pulls the full instructions into context only when a task matches. Ten procedures cost you ten short descriptions, not ten full playbooks, in every turn.
+- **Sometimes accuracy.** This one is genuinely use-case dependent. In specific scenarios, like large toolsets or sophisticated retrieval, keeping irrelevant procedure out of context and bringing in the right one can improve how reliably the agent acts. It is not a guarantee. Treat it as something to evaluate, not assume.


this isn't clear: n specific scenarios, like large toolsets or sophisticated retrieval. I know this is my comment verbatim, but it the sentence ends up being awkward here

adilei · 2026-06-15T20:32:46Z

+
+## The same benefits show up in Copilot Studio
+
+The good news is that the modern Copilot Studio orchestrator works the same way: it can reason over a set of available Skills, select the relevant one, and bring its procedure into context for that task. So the manageability and context benefits carry over directly, and the accuracy question is still yours to evaluate.


"that task" -- which task?

adilei · 2026-06-15T20:51:08Z

+
+## What Skills look like in practice
+
+Skills shine wherever the *right answer depends on following a sequence*. A few shapes worth recognizing:


I think this is the wrong framing. I think what you want to say is: here are some useful patterns that leveraging skill. The whole bit about following a sequence/being a procedure is a little reparative and not always informative. E.g. is generating a file based on a template a procedure? A bit of a strech.

adilei · 2026-06-15T20:52:00Z

+- **Generating a file from a template.** The output must follow a fixed structure every time, like a report, a summary, or a standardized record. The Skill carries the template and the rules for filling it in.
+- **A specific order of execution.** The task is a pipeline: discover available processes, then run the analysis, then add the ROI pre-scan, then format the result. The Skill keeps the steps in the correct sequence and points at the right tool at each one, exactly what the reasoning view above is showing.
+
+In every case the Skill is the *playbook*, not the data and not the system access. Knowledge gives the agent facts, tools give it reach, and Skills give it the operating procedure that ties them together.


System access?

adilei · 2026-06-15T20:53:03Z

+
+## A Skill, or a new agent?
+
+Before Skills, the instinct for every new process was to build another specialized agent: one for HR leave, one for IT incidents, one for refunds. Sometimes that is right: security boundaries, distinct audiences, and clear business ownership still justify a separate agent.


But the examples you give here are ones that do justify seperate agents.

adilei · 2026-06-15T20:55:32Z

+
+Before Skills, the instinct for every new process was to build another specialized agent: one for HR leave, one for IT incidents, one for refunds. Sometimes that is right: security boundaries, distinct audiences, and clear business ownership still justify a separate agent.
+
+But often the real need is not a new agent, it is a new *procedure*. If the same agent serves the same audience, shares the same knowledge boundary, and already has the right tools, a Skill is the better unit of modularity. You are not building another agent to maintain; you are teaching the existing one another way of working. That is how Skills cut down on agent sprawl.


I know I've already said that, but I'm really not sure "procedure" is doing the work we want it to do for the reader. Is driving the conversation in a certain way (e.g. questions to ask) a procedure? Procedure sounds too much like policy or a playbook, which gives the wrong connotation I think.

It is useful to explain "common sense" vs "how the organization does things" but I think there's an inflation of this term here

adilei · 2026-06-15T20:56:17Z

+
+## A word on trust
+
+Because a Skill shapes how the agent behaves, it is a trust surface, especially one copied from a community source, generated by AI, or reused from another environment. Review Skills before adding them: keep them focused (a Skill is not a place to dump an entire policy manual), avoid overlapping vague Skills that confuse routing, and check for prompt injection or instructions to misuse tools.


Couple of different points get conflated here. If trust is important, stay on topic

…dback - Replace 'procedural memory' framing with 'instructions and resources loaded on demand' - Add mental-model analogy section (table + hub diagram) and colored context-flow diagrams - Update for shipped support: bundled resources and executable scripts - Address review feedback (intro, accuracy/speed bullets, tool soft-pointing, agent-vs-skill examples, trust, dead link) - New header image Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

adilei · 2026-06-20T09:37:06Z

Hi @Roelzz — @adilei did an editor's pass on this post and I've opened it as a separate branch on the main repo so you can review and approve before we publish: #332

It builds on your PR with some tightening (intro reframe, dropped the standalone Speed benefit, reworked the 'Skill vs. new agent' heuristic), a few accuracy fixes, and the required agent_edition: modern front matter. Full change list is in #332.

If you're happy with the edits, approve #332 and we'll merge it. If you'd rather keep iterating here on your own branch, just say the word and we'll port anything useful back over.

Add post: Modern Agents Have Skills Here's How They Work in Copilot S…

56a5ca3

…tudioNow Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

adilei reviewed Jun 15, 2026

View reviewed changes

adilei mentioned this pull request Jun 20, 2026

Review edits: Modern Agents Have Skills Now (for @Roelzz to approve) #332

Merged


		Enterprise agents rarely fail for lack of facts. They fail because the organization has a specific way of doing the work, and that procedure ends up scattered across one ever-growing system prompt. Modern agents have a cleaner place to put it: Skills.

		If you have spent time with coding agents recently, you have probably already met them. A Skill is a small, self-contained package of procedural knowledge: a `SKILL.md` file with a name, a description, and instructions that tell the agent how to do a specific kind of task. The agent loads it only when a task actually needs it.


		Skills are based on the [Agent Skills open format](https://agentskills.io/), an open standard originally developed by Anthropic. The shape is deliberately simple, but the benefits are real:

		- Manageability. Instead of one ever-growing instruction blob, each procedure lives in its own focused Skill. You can reason about, review, and version them one at a time.


		## The same benefits show up in Copilot Studio

		The good news is that the modern Copilot Studio orchestrator works the same way: it can reason over a set of available Skills, select the relevant one, and bring its procedure into context for that task. So the manageability and context benefits carry over directly, and the accuracy question is still yours to evaluate.


		## What Skills look like in practice

		Skills shine wherever the right answer depends on following a sequence. A few shapes worth recognizing:


		## A Skill, or a new agent?

		Before Skills, the instinct for every new process was to build another specialized agent: one for HR leave, one for IT incidents, one for refunds. Sometimes that is right: security boundaries, distinct audiences, and clear business ownership still justify a separate agent.


		Before Skills, the instinct for every new process was to build another specialized agent: one for HR leave, one for IT incidents, one for refunds. Sometimes that is right: security boundaries, distinct audiences, and clear business ownership still justify a separate agent.

		But often the real need is not a new agent, it is a new procedure. If the same agent serves the same audience, shares the same knowledge boundary, and already has the right tools, a Skill is the better unit of modularity. You are not building another agent to maintain; you are teaching the existing one another way of working. That is how Skills cut down on agent sprawl.


		## A word on trust

		Because a Skill shapes how the agent behaves, it is a trust surface, especially one copied from a community source, generated by AI, or reused from another environment. Review Skills before adding them: keep them focused (a Skill is not a place to dump an entire policy manual), avoid overlapping vague Skills that confuse routing, and check for prompt injection or instructions to misuse tools.

Uh oh!

Conversation

Roelzz commented Jun 15, 2026

Summary

Checklist

Uh oh!

microsoft-github-policy-service Bot commented Jun 15, 2026

Contribution License Agreement

Uh oh!

github-actions Bot commented Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

adilei left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

adilei commented Jun 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

github-actions Bot commented Jun 15, 2026 •

edited

Loading