Beyond 13 Skills: How Copilot Cowork Is Redefining AI Workflows

-

Cowork has 13 skills. Here is why the architecture matters more than the count.

When I first looked at Copilot Cowork, I did what most of us do.

I scanned the list.

Word. Excel. Email. Research.

Familiar tools, repackaged.

But that framing does not hold for long.

Because Cowork is not designed as one system doing everything.

It is designed as a system that decides what to do, when and shows you as it does it.






Cowork helping me prep for my NMTC talk (NO)- Register to join online 24.04.26 (08:30-09:30 CEST 


What is actually happening

Cowork loads skills on demand.

Not all at once. Not invisibly.

When it needs something, it activates it.

You see it in the interface:

  • Preparing to compose email
  • Loading Deep Research
  • Building a document

It is a small detail, but it changes something important.

In environments where decisions matter care, public sector, regulated spaces, knowing what is acting is part of trust.

Not just the output.


The 13 skills (and why the list is not the point)

They fall into four groups:

  • File & Office  - Word, Excel, PowerPoint, PDF
  • Communication - Email, Communications, Adaptive Cards
  • Time & Meetings - Scheduling, Calendar Management, Meetings
  • Intelligence - Daily Briefing, Enterprise Search, Deep Research

On their own, these are expected.

The value shows up when they are used together.



What this looks like in practice

For roles built around coordination, the work is not linear.

It is layered.

You gather context.
You communicate.
You adjust timelines.
You follow up.

And you carry that context across every step.

With Cowork, that flow can happen in one place:

  • Use Deep Research to understand the situation
  • Use Email to communicate clearly
  • Use Calendar Management to act on it

No switching. No resetting context.

It sounds small.

But in practice, that is where most friction lives.

Custom Skills 

You can extend Cowork with your own custom skills. A SKILL.md file, saved in a specific OneDrive folder, with a name, a description, and plain Markdown instructions. Cowork discovers it automatically at the start of each conversation. Up to 20 custom skills per user.

That is a low-code extensibility model accessible to any practitioner who can write a structured document. It does not require a developer or a deployment pipeline.


Image source: Microsoft

Three things worth knowing right now

1. Schedule prompts
You can schedule a prompt to run automatically on a recurring basis. To create a scheduled prompt, describe what you want and when in your message. For example, "Send me a daily briefing every morning at 9 AM" or "Create a weekly status report every Friday."

Cowork sets up the schedule based on your request. You can manage your scheduled prompts from the Scheduled tab in the Tasks view, or from the Schedule section of the side panel. From there, you can edit, pause, resume, or delete any scheduled prompt.

2. Purview audit logs capture everything. 
All Cowork interactions are logged under Copilot activities in Microsoft Purview / whether you are on E3 or E5. If your organisation is not maximising Purview today, I genuinely recommend raising it with your Microsoft account team. It is one of the most underused governance assets in the stack.

3. Governance documentation is live. 
Admins, this one is for you. → Cowork admin governance documentation

The governance question this raises

Thirteen out-of-the-box skills, plus up to twenty custom ones, loading dynamically in a single agentic session. That is a conversation organisations need to have before they roll this out, not after.

What skills should be available to which roles? What actions require explicit approval? How do you audit what ran in a given session?

The approval model built into Cowork (risk level indicators, explicit confirmation before sensitive actions) is a start. But the skill architecture makes this a governance design problem, not just a product configuration one.

⚠️ Cowork is currently available through the Microsoft 365 Frontier preview programme. Pre-release feature, subject to change.

Which of these 13 skills would change your day-to-day work the most  and which one is missing? 

Read more:



Comments

Post a Comment

Popular posts from this blog

I passed AB-730 (Microsoft AI Business professional certification). Here is the Copilot Studio agent I built to do it.

-
Image
A practical walkthrough of building a Copilot Studio agent connected to the Microsoft Learn MCP server - what worked, what confused me, and what I would do differently. If you have been putting off studying for AB-730 -AI Business professional , this might change that. I built a dedicated study tutoring agent in Copilot Studio, connected it to the Microsoft Learn MCP server, and used it to prepare for the AI Business Professional exam. Here is exactly what I built and what I wish I had known earlier. Why I built it this way and what is MCP? The AB-730 exam tests precision, not broad knowledge. It focuses on specific details about how Copilot works across Microsoft 365, Responsible AI guardrails, and governance boundaries. A general AI chat tool drifts. It gives answers that sound right but are not grounded in the actual Microsoft documentation. I needed something that stayed on source. That is what MCP makes possible. Model Context Protocol (MCP) allows users to connect with existing ...
Read more

From Social Work to Microsoft Functional Consultant Associate: Governing the Process of a Career Pivot.

-
Image
On 17 January 2026, I passed PL‑200! This desk. Same spot. Same time. Same drink. Every single day. Pink sticky notes = my daily minimums. Laptop = 45 minutes of focused work. No exceptions. Coming from social work, my job has always been to design systems that still work when people are tired, stressed, or having a bad day, so I applied that same mindset to learning.   Instead of relying on willpower, I built a system around my motivation, which let me catch mistakes before they snowballed. The core idea: Govern the process, not just the output. Step 1: make discipline measurable (SMART) I didn’t set a vague goal like “study more.” I needed structure and hands-on experience, so I joined the Microsoft Power Up Program (Cohort 28, Fall 2025), a free program designed to help people build practical skills through guided, hands-on learning. For three months, I deep-dived into Power Apps with one clear outcome: build an end-to-end Smart Parking & Permit Management solution whil...
Read more

Deploying Copilot Studio Kit the Enterprise Way

-
Image
We all shift into that AI-first mindset where we ask, "How can AI help here?" but the real question for production is: What happens when things get complex? The Copilot Studio Kit and its Compliance Hub are interesting because they don't just stop at building. They introduce a theory of governance that focuses on risk thresholds and automated enforcement. It’s less about stopping innovation and more about building a safety net that works even when we aren't looking. To implement the Copilot Studio Kit successfully, we have to look at the prerequisites, the settings and dependencies that aren't just recommendations, but technical requirements for the solution to import and run. According to Microsoft documentation, the setup begins with preparing the environment's "physical" infrastructure. Phase 1: Preparation & Prerequisites Step 1: Enable Power Apps Code Components (PCF)   A Power Platform environment with Dataverse as a data store:  Microsof...
Read more