Copilot Studio: Free Agent Skills Guide

by HubSite 365 about Andrew Hess - MySPQuestions

Currently I am sharing my knowledge with the Power Platform, with PowerApps and Power Automate. With over 8 years of experience, I have been learning SharePoint and SharePoint Online

Citizen Developer Microsoft Copilot Studio Learning Selection

Free CAT Agent Skills for Copilot Studio, Cowork and Scout adds drop-in skills for charts OCR templates and redlines

Key insights

CAT Agent Skills Library: A free, open-source gallery hosted by Microsoft that offers drop-in skill packages for Copilot Studio, Copilot Cowork, and Scout.
Skills load on demand as Markdown and optional files so teams can add capabilities quickly.
Skills for Copilot Studio: An experimental plugin from the Copilot Acceleration Team that helps you author and test Copilot Studio agents from code editors and the terminal.
It supports tools like VS Code, GitHub Copilot CLI, and Claude Code; the public release noted is v1.0.11 (May 13, 2026).
skill: A self-contained set of instructions and logic with a name, description, and Markdown guidance that gives an agent a specific capability.
The agent runtime invokes a skill when a user request matches the skill’s purpose, and skills can include scripts or supporting files.
YAML: The plugin uses YAML files to author and validate Copilot Studio agent configurations, enabling a code-first workflow for faster authoring and troubleshooting.
This helps developers generate valid agent topics and test changes from their editor or terminal.
reusable: Skills improve speed and consistency by letting teams reuse the same behavior across agents and projects.
Skills can move with an agent through application lifecycle management and Power Platform solutions, reducing repeated work.
experimental: The plugin and some formats are labeled experimental or beta, so schemas and behaviors can change without notice.
The community gallery offers many examples, but quality and completeness vary by contributor, so review before production use.

Video overview

In a new YouTube video, Andrew Hess of MySPQuestions walks viewers through Microsoft’s community-driven toolkit for AI agents, focusing on the free CAT Agent Skills library and the related experimental Skills for Copilot Studio plugin. He explains what each component does, shows examples, and highlights practical steps to add capabilities to a Copilot agent. Consequently, the video serves both as a demo and as a quick reference for teams considering reusable skills.

What the CAT Agent Skills library offers

The video describes the CAT Agent Skills gallery as an open, Microsoft-hosted collection of drop-in skill packages for Copilot Studio, Copilot Cowork, and Microsoft Scout. Each skill typically includes a markdown file with instructions and sometimes supporting scripts or assets, which means teams can download and enable capabilities like chart generation, document redlining, and Monte Carlo simulations in minutes. Therefore, the gallery aims to shorten development cycles by providing ready-made, documented building blocks rather than forcing authors to recreate common behaviors.

What Andrew demonstrates

Hess walks through chaptered demos that include an introduction, an inventory of available skills, an "Agent Harness" skill, a broad overview of everything in the gallery, a RapidOCR demonstration, and an image update example. Through these segments, he shows how a skill’s markdown instructions load on demand and how the agent invokes the skill when the user’s request matches its purpose. As a result, viewers can see both the authoring model and the runtime behavior in a single session.

Skills for Copilot Studio plugin: code-first authoring

The video also covers Microsoft’s experimental Skills for Copilot Studio plugin, which targets developers who prefer code-first tooling. Hess highlights that the plugin supports tools like Claude Code, GitHub Copilot CLI, and VS Code, enabling authoring and validating Copilot Studio YAML directly from the editor or terminal. Importantly, he stresses that the plugin is experimental, warning that the YAML schema may change and that the plugin is intended as a research project from the Copilot Acceleration Team.

Tradeoffs between gallery and plugin approaches

Hess balances the convenience of the gallery against the control offered by the code-first plugin, noting that each has advantages and limitations. On the one hand, the community gallery accelerates adoption with ready-made examples and encourages reuse across teams; on the other hand, using YAML-driven workflows gives developers finer control and faster iteration when troubleshooting or integrating with CI/CD. Thus, organizations must weigh speed and ease against maintainability and governance when choosing how to adopt skills.

Challenges and caveats

Throughout the video, Hess flags several important caveats. He points out that the plugin is labeled experimental and that Microsoft’s Copilot Studio schema could change, which increases maintenance risk for YAML-driven setups. Additionally, because the gallery is community contributed, quality and completeness vary; teams may need to audit or extend downloaded skills to meet security, compliance, or brand requirements.

How skills fit into enterprise workflows

Hess explains that skills can be added to an agent from the Skills tab in Copilot Studio by uploading a SKILL.md file or a packaged zip, and that traditional Azure Bot Service skills can also be registered and used as tools in topics. He emphasizes that skills are currently described as scoped to the agent they are added to and follow that agent through ALM and Power Platform solutions, which simplifies packaging but can complicate reuse across siloed teams. Therefore, planning around deployment, change control, and shared catalogs will matter for larger organizations.

Security, governance, and quality tradeoffs

Moreover, Hess raises governance questions that teams must consider when they rely on shared skills. For example, reuse improves consistency, but it also concentrates risk if a widely used skill has a flaw or an unvetted dependency; consequently, teams must balance reuse against the need for audits and secure development practices. In short, shared skills speed development but require governance guardrails to manage dependencies and ensure compliance.

What to watch next and practical advice

Finally, Hess suggests monitoring whether Microsoft expands a centralized shared catalog or keeps skills primarily per-agent, since that decision will influence long-term reuse strategies. He also recommends teams try the gallery for quick wins and evaluate the experimental plugin if they prefer a code-first workflow, while remaining prepared for schema changes and additional maintenance. Overall, the video offers a measured look at a promising ecosystem and encourages viewers to experiment while planning for governance and change management.