3 Ready-to-Use Copilot Cowork SKILL.md Examples for MSPs
Below are three practical, production‑ready Copilot Cowork custom skills designed specifically for MSP use cases.
Each skill follows Microsoft’s supported structure:
YAML frontmatter (name, description) followed by Markdown instructions,
and is intended to live in:
/Documents/Cowork/Skills/<skill-name>/SKILL.md
Copilot Cowork automatically discovers these skills at the start of each conversation.
Each one targets repeatable, high‑value MSP workflows rather than one‑off prompts.
1) MSP Client Monthly Executive Summary (QBR‑lite)
Folder: /Documents/Cowork/Skills/msp-client-exec-summary/
File: SKILL.md
---
name: MSP Client Executive Summary
description: Creates a monthly executive summary for an MSP client using M365 activity evidence (emails, meetings, files) and a consistent MSP-friendly format.
---
## Purpose
Produce a client-ready monthly executive summary (QBR-lite) that is consistent, factual, and easy for non-technical stakeholders to read.
## Inputs to request (ask if missing)
1. Client name (exact)
2. Reporting period (e.g., "March 2026")
3. Where client artefacts live (SharePoint site / Teams name / OneDrive folder path)
4. Any key initiatives/projects to include (list)
5. Any sensitive exclusions (e.g., "do not mention incident details")
## Data gathering rules
- Prefer evidence from Microsoft 365 content: emails, meeting notes, and files in OneDrive/SharePoint.
- Use only artefacts the user has access to.
- If you can’t find evidence for an item, mark it as “No supporting evidence found in M365 sources provided”.
## Output format (Word document)
Create a Word document titled:
"Executive Summary - <Client> - <Reporting Period>"
Use these sections and headings exactly:
1. Headline Summary (5 bullets max)
- Outcomes delivered (business language)
- Risks/issues (non-alarmist)
- Decisions needed from client (if any)
2. Service Health Snapshot
- Identity & access notes
- Device management posture
- Security themes at a high level
3. Work Completed (Outcomes, not tasks)
- Outcome
- Evidence reference
- Business value
4. Open Items & Blockers
- What’s stuck
- Who owns it
- Next trigger/date
5. Recommendations for Next Month
- 3–5 pragmatic recommendations
- Include effort (S/M/L) and impact (Low/Med/High)
6. Appendix: Evidence List
- Files, meetings, and email subjects used
## Tone & constraints
- Australian English.
- No vendor hype.
- Client-safe wording only.2) MSP Incident Communications Pack
Folder: /Documents/Cowork/Skills/msp-incident-comms-pack/
File: SKILL.md
---
name: MSP Incident Comms Pack
description: Drafts an MSP incident communications pack (client update + internal summary + next-steps checklist) with approval-safe wording.
---
## Purpose
Create consistent, calm, defensible communications during an incident.
## Inputs to request (ask if missing)
1. Client name
2. Incident label (short)
3. Timeline of events
4. Confirmed facts vs suspected items
5. Client audience
6. Desired update cadence
## Data gathering rules
- Use M365 artefacts only (emails, meetings, Teams messages, files).
- Do not invent technical detail.
- Ask for clarification where facts are missing.
## Outputs
### A) Client Update Email (Outlook draft)
Subject:
"Update: <Client> - <Incident> - <Date>"
Include:
- What we know
- What we’re doing
- What we need from the client
- Next update timing
### B) Internal Technician Summary (Teams)
- Incident label + severity
- Current status
- Owner and next actions
- Links to evidence
### C) Next-Steps Checklist (Word)
Include:
1. Containment
2. Investigation
3. Recovery
4. Communications
5. Post-incident follow-up
## Tone & constraints
- Calm, factual, non-alarmist.
- Australian English.
- No blame, no absolutes.3) MSP Onboarding Kickstart Pack (SMB‑friendly)
Folder: /Documents/Cowork/Skills/msp-onboarding-kickstart-pack/
File: SKILL.md
---
name: MSP Onboarding Kickstart Pack
description: Creates an MSP onboarding pack including welcome email, onboarding schedule, folder structure, and checklists.
---
## Purpose
Deliver a consistent, professional first-30-days onboarding experience for SMB clients.
## Inputs to request (ask if missing)
1. Client name and primary contact
2. Services in scope
3. Target go-live date
4. Preferred meeting times
5. Tenant state (new or existing)
## Outputs
### A) Welcome Email (Outlook draft)
Include:
- Week 1 expectations
- Required client inputs
- Communication model
- Links to onboarding artefacts
### B) Onboarding Plan (Word)
Title:
"Onboarding Plan - <Client> - First 30 Days"
Break down by week:
- Meetings
- Deliverables
- Dependencies
### C) Folder Structure
Create or propose:
- 01 - Commercial & Contacts
- 02 - Tenant Baseline
- 03 - Security & Compliance
- 04 - Devices & Intune
- 05 - Documentation & SOPs
- 06 - Projects
- 07 - Reports
### D) Onboarding Checklist (Word)
Include:
- Identity baseline
- Device enrolment
- Security configuration
- Documentation completion
- Client sign-off points
## Rules
- Step-by-step.
- SMB-realistic (no enterprise bloat).
- Australian English.
Implementation reminder:
Each skill must live in its own folder under /Documents/Cowork/Skills/,
must be named SKILL.md, and should have a specific description so Cowork knows when to load it.
“
CIAOPS 