Copilot Playbook
Claude Skills / The Skills Guide
Updated November 2, 2026
Practice Guide · Skills

The definitive guide to skills

A skill is a folder of plain-text instructions that teaches an AI assistant to do one job your way. The same file now runs in Claude and across Microsoft's Copilot products. This guide covers what skills are, where to get and share them, what partners can build and sell, and what the economics really look like.

1 file format, two ecosystems
10 sellable offer concepts
12 sourced real-world examples
16 claims independently re-checked

Prepared by Ken Lince — Sr. Director, Cloud Engineering, TD SYNNEX · For Microsoft channel partners building skills into their practice · Researched and fact-checked 2 November 2026. Every number comes from a cited primary source or is labelled as an illustration. Skills and Microsoft pricing change quickly, so re-check before quoting.

1 · The idea

A skill is a playbook the AI can pick up

Think of onboarding a new colleague. You hand them a handbook and they open the right chapter when the situation comes up. A skill works the same way: written once, loaded only when it's relevant.

always on
~1 paragraph
Layer 1 · Always visible

Name and description

The AI sees this for every skill, in every conversation. It works like a label on a binder and is the only part that costs attention up front.

on a match
Layer 2 · Loaded when the task matches

The body of SKILL.md

The rules, the workflow and the order of steps. Read the moment your request matches the description.

on demand
Layer 3 · Opened step by step

Reference files, templates, scripts

Detailed specs, branded templates and deterministic scripts. Opened only when a step needs them, so a skill can be huge without slowing anything down.

What a real one looks like

The folder below is the actual event-app skill used to build the TD SYNNEX event apps: 256 lines of instructions in SKILL.md, backed by 98 reference files.

td-synnex-event-app/
SKILL.mdthe instructions
references/98 files
intake-interview.md
feature-catalog.md
design-system.md
render-qa.md
shell.htmlstarter template
… 93 more
GETTING-STARTED.htmlhuman guide
Header: always visible --- name: td-synnex-event-app description: Builds an event-guide PWA for a new event … Use whenever the user wants to build, clone or stand up an event app, agenda app or conference guide … Always run its intake before writing code. --- Body: read when triggered # TD SYNNEX Event App Builder ## Step 0: orient yourself ## Step 1: run the intake interview ## Step 2: build what the manifest lists ## Step 3: tell the user what's still manual ## Step 4: when new information arrives Rules inside: "Never hand over a screen you haven't scored." Final audit must score 95+.
2 · Why it matters

Why skills are more than a good prompt

A prompt you typeA skill
LifetimeGone when the chat endsA file that stays, versioned and shareable with a team
TriggerYou remember to paste itThe assistant recognises the task from the description
SizeLimited by what you'll pasteHundreds of pages, read only as needed
ConsistencyVaries by who wrote the promptEveryone gets your standards, templates and checks
ImprovementStart over each timeEdit one file and every future run improves
PortabilityCopy and pasteOne open format that now runs in several products
1

Encoded expertise

Your playbook, price book, policies and taxonomy, written once so every run follows them.

2

Deterministic parts

Scripts handle anything that must be exact, such as reconciliations and scoring, so the AI isn't guessing at arithmetic.

3

Skills are not connectors

Connectors and MCP servers give the assistant access to your systems. Skills tell it how to do the work. You usually need both.

When would someone use a skill?

Recurring documents

QBR decks, board packs, proposals and reports that must follow a template and a storyline.

Rule-heavy judgement

Contract review against a playbook, ticket triage against a priority taxonomy, expense checks against policy.

Brand and compliance

Anything where output must follow brand rules, regulatory wording or an approval gate.

Specialist know-how

Your firm's way of doing a job that a general assistant doesn't know and shouldn't improvise.

3 · Copilot and Claude

Skills in Copilot vs Claude: same file, different runtime

Anthropic published the SKILL.md format as an open standard in December 2025. Microsoft products now read the same format. What differs is where a skill is stored, how big it can be, whether its scripts can run, and how IT governs and pays for it.

The one-line answer to "are they interchangeable?" Mostly yes for the file, no for the runtime. A well-written skill usually moves between products unchanged. Microsoft's own conversion tooling copies a Claude plugin's skills "verbatim". But limits, scripts, tool names and governance differ, so test it in every product you deploy to.
ClaudeGitHub CopilotMicrosoft 365 Copilot
CalledAgent SkillsAgent skills"Skills" in Cowork, declarative agents, PowerPoint and Excel; also bundled in plugins. Copilot Studio agents have skills too
FormatSKILL.md folder (origin of the standard)SKILL.md folderSKILL.md folder
Where skills live.claude/skills, plugins, the Skills API, claude.ai upload.github/skills, .claude/skills or .agents/skills in a projectOneDrive (Cowork), an agent package, an M365 app package, or the admin center
LimitsVary by surfaceVary by surfaceDeclarative agents: 8 skills, each under 20,000 characters of instructions. Cowork: 50 personal skills, SKILL.md up to 1 MB; a Cowork plugin package up to 20 skills
ScriptsRun, with network access depending on the surfaceRun locally or in the cloud agentDeclarative agents run scripts in a sandbox with no network
Admin controlOwner-provisioned org skills, plugin marketplacesRepo-based. No org-wide skills policy foundAdmins install, scope and block skills in the admin center under Agents > Tools
BillingPlan seats, or API usageCopilot planCowork and Copilot Studio agents are billed in Copilot Credits ($0.01 each pay-as-you-go)

What carries over

The folder name and SKILL.md, matching name and a description up to 1,024 characters, a plain Markdown body, and text reference files one level deep.

What to check before moving a skill

Claude Code-only front-matter keys (such as model or hooks) can cause errors elsewhere. Tool names in allowed-tools differ by product. Scripts that need the network or pip install are blocked in Microsoft's declarative-agent sandbox. Size limits differ.

One portable trick

Keep descriptions free of colons. Some Microsoft tools require quoting them and others require them unquoted.

Watch the word "skill"

Microsoft uses it for several things. Cowork's built-in skills, Copilot Studio's topic skills and Agent 365 setup skills are not all the same thing as a SKILL.md you write.

Caveats on Cowork and Claude models Copilot Cowork has been generally available since 16 June 2026 and needs a Microsoft 365 Copilot licence. It can use Claude models, but admins can turn the Anthropic family off, and inside the EU Data Boundary only GPT models are offered. Don't tell a customer Cowork "runs on Claude everywhere".

What to say to a customer

"Skills are written instructions for an AI assistant, packaged as a folder with a SKILL.md file. They teach it to do a specific job your way, such as a QBR deck, a contract review or a release note. Anthropic created the format, and Microsoft has adopted the same open standard across GitHub Copilot, Copilot Cowork, Copilot agents, PowerPoint, Excel and Copilot Studio. So a well-written skill is a reusable company asset, not a bet on one vendor. What changes from product to product is where you store it, how big it can be, whether its scripts can run, and how IT governs and pays for it. Treat skills like software: get them from trusted sources, review them, and test them in each product you deploy to."

4 · Libraries

Where to download skills

Start with first-party sources. Treat the big community directories as discovery aids that need vetting, because supply is huge and review is thin.

SourceOperatorWhat's in it and how to use it
First-partyanthropics/skillsAnthropicExample skills (creative, technical, enterprise, documents). Claude Code: /plugin marketplace add anthropics/skills. Most are Apache-2.0, but the docx, pdf, pptx and xlsx skills are proprietary and can't be redistributed or sold
First-partyclaude-plugins-official and the Claude directoryAnthropicCurated plugins that can contain skills, plus partner listings browsable in claude.ai
First-partymicrosoft/skillsMicrosoftSkills for Azure SDKs and Microsoft Foundry. MIT licence. Install with npx skills add microsoft/skills
First-partyCAT Agent Skills galleryMicrosoft Copilot Studio teamDownloadable skills for Cowork and Copilot Studio, including partner-relevant ones such as Copilot Adoption Dashboard and Power BI Model Review
Community, GitHub-hostedgithub/awesome-copilotGitHub org, community contentThe built-in Copilot plugin marketplace. Its README asks you to inspect anything before installing
Discovery aidskills.sh, SkillsMP, ClawHub, SmitheryVercel and othersDirectories and registries with very large, self-reported counts and uneven review. Use the vetting checklist below

Microsoft has no separate store for bare skills. Skills ship inside repos, Copilot plugins, Copilot Studio agents or Microsoft 365 app packages.

Vet before you install

Why this matters Security researchers reported 341 malicious skills among 2,857 audited on ClawHub (Koi Security, via The Hacker News, February 2026). Snyk scanned 3,984 skills from ClawHub and skills.sh and confirmed 76 as malicious by human review; 13.4% had a critical issue. Whoever installs a third-party skill in a customer tenant owns the incident conversation.

1 · Source

Prefer first-party repos or a named, accountable publisher. Treat aggregators as discovery only.

2 · Read everything

Read SKILL.md and every file in scripts/ and references/.

3 · Install red flags

"Prerequisites" that download binaries, curl | sh, obfuscated commands.

4 · Exfiltration red flags

Outbound URLs, reading .env or credentials, "don't tell the user" instructions.

5 · Hidden text

Scan for invisible Unicode characters and HTML comments.

6 · Scope

Actions should match the description, and tool permissions should be no wider than needed.

7 · Scan and pin

Run a skill scanner, then pin to a commit or tag. Leave auto-update off for third-party sources.

8 · Govern

Use an allowlisted internal marketplace, or admin-deployed skills, and re-audit periodically.

Can a partner resell someone else's skill?

Apache-2.0 skills can be reused and sold if you keep the notices, but you get no trademark rights. Anthropic's docx, pdf, pptx and xlsx skills cannot be redistributed or sold, and one skill in the repo (doc-coauthoring) has no licence file at all. Check each folder's licence.

5 · Sharing

How to share a skill

Pick the path that matches who needs it. Keep the source in a Git repo whichever you choose, so every release is traceable.

Claude, one organisation (Team or Enterprise)

Best for sharing inside a customer or your own company.

  1. Write the skill folder. The name must match the folder (lowercase, hyphens).
  2. Add license and metadata (author, version) to the front-matter.
  3. Zip the folder, not just its contents.
  4. Test-upload it yourself (Customize > Skills > Upload a skill) and run real prompts.
  5. Owner: Organization settings > Plugins & skills. Confirm Skills and code execution are on.
  6. Owner: Add > Upload a skill. It goes live for all users.
  7. For a subset of users on Enterprise, wrap the skill in a plugin and assign it to a group.

Updating an owner-provisioned skill in place isn't documented, so plan on remove and re-add, and keep the version in metadata.

Claude Code plugin marketplace

Best for developers and partners distributing to many customers.

  1. Put each skill under my-plugin/skills/<name>/SKILL.md and add .claude-plugin/plugin.json.
  2. Run claude plugin validate --strict ./my-plugin.
  3. Create .claude-plugin/marketplace.json listing your plugins.
  4. Test locally with claude plugin marketplace add ./ then claude plugin install.
  5. Push to GitHub or another git host. Private repos work.
  6. Users run claude plugin marketplace add your-org/your-repo, then install.
  7. Org-wide, admins list the marketplace in managed settings so it installs automatically.
  8. Bump version in plugin.json on each release. Users get updates with claude plugin update.

A GitHub repo

The widest reach: works for Copilot, Claude Code and other agents that read the standard.

  1. Put skills in skills/<name>/SKILL.md with a LICENSE at the root.
  2. Run gh skill publish --dry-run to validate against the standard.
  3. Run gh skill publish. Releases tie to git tags.
  4. Consumers run gh skill install owner/repo <skill> and can pin a tag or commit.
  5. For in-repo use, commit to .github/skills/ (Copilot) or .claude/skills/ (Claude Code).

gh skill is a public preview.

Copilot Studio agent skill

Best when the customer's agent lives in Copilot Studio.

  1. Open the agent (on the GitHub Copilot harness) and go to Build > Skills > Add skill > Upload a skill.
  2. Upload a .md with front-matter, or a .zip with SKILL.md. Save as UTF-8 without BOM.
  3. Test in the test pane.
  4. Add the same skill to other agents as needed. Download it to share with other makers.
  5. To update, edit locally, then Replace.
  6. Publish the agent to Teams and Microsoft 365 Copilot. An admin approves it in the admin center.

Microsoft 365: a Cowork plugin

Best for packaging skills for a tenant, or for the public Microsoft 365 App Store.

  1. Scaffold with Microsoft's preview CLI, or convert an existing Claude plugin with Microsoft's conversion script.
  2. Package a manifest, icons and skills/<name>/SKILL.md. Stay within the companion-file limits.
  3. Validate, then sideload to test.
  4. Tenant-wide: Microsoft 365 admin center > Manage apps > Upload custom app.
  5. Admins deploy to groups. Users can't remove admin-deployed plugins.
  6. Public: submit through Partner Center (manual review). This requires the AI Cloud Partner Program and the Microsoft 365 and Copilot program.

Personal Cowork skills need no admin: drop the folder into OneDrive at /Documents/Cowork/skills/.

6 · Proof

What skills are doing in the real world

Everything in this section has a published source. Where a figure is self-reported by the company, we say so. Where there are no numbers, we say that too.

Read this before you quote a number The strongest published figures are two company-reported before-and-after results: Rakuten ("what once took a day, we can now accomplish in an hour") and Anthropic's own legal team (marketing review from two to three days down to 24 hours). Neither gives a method or sample size. Present them as "reports", never as a guarantee for your customer.
7 · What partners can build

Ten offers that earn every month

These are proposed offers, not case studies. Each one runs from exports (CSV, XLSX, PDF), so it can be demoed on day one with no integration, and each repeats on a monthly or quarterly rhythm, which is what makes it recurring revenue rather than a one-time build.

Concept Everything in this section is design thinking. Build-day figures are estimates for one experienced builder including quality tests, and exclude customer data-access approvals. Nothing here is a measured result.

The strongest five

Show the other five concepts

What makes a skill worth paying for

Trigger-precise description

Written in the customer's own words ("close the month", "respond to this RFP"), because the description is all the AI sees until the skill fires.

Expertise the AI doesn't have

The customer's playbook, answer library, taxonomy or schemas. Leave out generic explanations.

Templates and scripts

Branded Office templates so the output looks like the customer's own work, and scripts for anything that must be exact.

Checks and guardrails

Validation steps, approval limits, human-review gates, and statements of what the skill must not do.

What turns a skill into MRR The skill holds customer-specific knowledge that keeps changing (playbooks, price books, policies, benchmarks) and runs on a recurring business rhythm (month-end, QBR, renewal, audit). The file is easy to copy. The ongoing curation is the service.
8 · Channel economics

The honest economics

Is anyone building a business around skills? Yes, around the services that surround them, but not yet around the skill files themselves.

!

Skills are being given away

On 27 October 2026 TD SYNNEX announced "a new AI Skills Marketplace in StreamOne" for partners serving SMB customers. The skills are available at no cost; partners earn from the licences, consumption and services the skills drive.

13%

Few MSPs earn AI revenue yet

Kaseya's 2026 survey of more than 1,000 MSPs found just 13% generating meaningful revenue from AI and automation services. We found no named MSP that has published agent MRR.

3%

Marketplace fee

Microsoft charges a 3% standard store service fee on transactable offers, with a 50% discount available on qualifying private-offer renewals.

The one-sentence version Treat skills as free tooling that lowers your delivery cost, and charge for the outcome you run for the customer: build, govern, operate and prove results, with consumption passed through and capped.

Revenue models available

ModelWhat you sellReality check
Build or workshopDiscovery, build and deployment of skills or agentsOne-time, not recurring. We could not confirm market price points
Managed serviceMonitoring, credit management, change requests, governance and a monthly reportBest fit for MRR. Support time and consumption swings are the risks
Licence resale (CSP)Copilot, Copilot Studio credits, Agent 365Microsoft sets price and margin. No CSP margin rate on Copilot was found published
Own agent as SaaSA partner-built agent sold through Microsoft Marketplace or a CSP private offerNeeds a multitenant SaaS build. Inference cost can exceed the revenue per seat
Usage or outcome pricingCredits with markup, or a price per resolved taskIntercom Fin charges $0.99 per outcome and Salesforce Agentforce $2 per conversation. No vendor publishes a reseller margin
Retail skill packsDownloadable skillsPriced at about $9 to $299 a month by small vendors, none disclosing revenue, against a free open supply. A weak MRR base

What a Copilot Studio agent costs to run

The cost swings with how the agent is designed, which is the margin risk if you quote a flat monthly fee. This calculator uses Microsoft's published credit rates (classic answer 1 credit, generative answer 2, tenant-graph grounding 10). Packs are $200 per 25,000 credits; pay-as-you-go is $0.01 per credit.

Illustration Your assumptions, Microsoft's rates.
0
runs a month (21 workdays)
0
credits a month
$0
pay-as-you-go at $0.01
$0
prepaid packs only

If every user holds a Microsoft 365 Copilot licence and uses the agent interactively, the credit charge is $0 within fair-use limits. Autonomous triggers, some agent flows and Computer-Using Agents still consume credits, so quote the licence cost honestly alongside it. Agents stop at 125% of prepaid capacity unless pay-as-you-go is linked.

Real players and what they actually show

Risks to price in

Platform dependence

Microsoft set or changed licence prices, credit rates and partner margin programmes during 2026. A managed-service price built on today's burn rates can be repriced under you.

Commoditisation

A skill is a folder of text that can be copied, and supply is huge and often free. The defensible part is the customer's data, the integration and the ongoing operation.

Liability and security

Whoever installs a third-party skill in a customer tenant owns the incident. Review everything you deploy.

IP ownership

Skills built in a customer's tenant or repo are easy for the customer to keep. Put ownership language in the contract. No industry-standard term was found.

9 · Before you sell it

Five tests every skill must pass

Anthropic's guidance is to build evaluations first, measure a no-skill baseline, and test on every model you'll deploy to. These pass marks are suggestions. Agree the real ones with the customer.

1 · Trigger accuracy

Run 20 or more prompts that should fire the skill and 20 or more near-misses that shouldn't, on each target product. Suggested bar: at least 90% right in each set.

2 · Baseline A/B

Run three or more real customer tasks with and without the skill, blind-graded against a written rubric. The skill must clearly beat the baseline.

3 · Golden-file determinism

On fixture data with known answers, scripted outputs must match exactly across five or more runs, and every number must trace to a source row.

4 · Output and brand validation

Generated Office files open cleanly in desktop Office and pass the skill's own validator. Render to images and inspect.

5 · Adversarial and safety pass

Feed prompt-injection text, out-of-scope requests, PII and malformed files. The skill must ignore embedded instructions and flag missing data instead of inventing it.

Repeat per model tier

Run test 2 on each model tier you'll support. A skill that only works on the top model has a margin problem.

10 · Honesty section

What we couldn't confirm

Every claim in this guide was checked against a primary source. These are the ones that failed or came back different, so you don't repeat them.

Do not say
  • "Claude Marketplace takes no commission." Anthropic has published no commission or revenue-share terms. Say "terms not published, ask Anthropic".
  • "The TD SYNNEX skills marketplace works with Microsoft 365 Copilot (or Claude)", or any skill count or launch date. The release states none of these.
  • "A Pax8 survey found 13 of 600 partners…". It was one executive's remark, reported second-hand.
  • "36.82% of skills are malicious." That is the share with any security flaw. 76 were confirmed malicious.
  • "Licensed users always cost $0 in agent credits." Autonomous runs and some flows still consume credits.
  • "Microsoft's renewal fee is 1.5%." It's a 50% discount that applies only to qualifying private-offer renewals.
  • "A 50-user agent costs exactly $400 or $1,800." Those are pack-only figures for one assumed usage pattern.
Still open We could not find a published CSP margin rate on Microsoft AI licences, a named MSP with published agent MRR, or a GitHub organisation-level policy for skills. Microsoft lists Microsoft 365 E7 at $99 per user and Agent 365 at $15 per user (both generally available 1 May 2026); confirm the billing term with your licensing contact. Skill-directory sizes are self-reported by their operators.

Remember three things

  1. A skill is just a folder with a text file called SKILL.md, and the format is now open and shared across Claude and Microsoft's Copilot products.
  2. The file is easy to copy, so the value is in the expertise it encodes and the service that keeps it current.
  3. Skills are free tooling. Charge for the outcome you run, and cap the consumption underneath it.