Your department’s best Copilot instructions need a better home.

Skills are coming to Copilot Chat. Start with a recurring team task—and check the sharing rules before sending everyone to look for it.

Someone finally figures out how to get Copilot to produce the department's weekly update properly. Naturally, the instructions are now buried in a chat nobody else can find.

Skills could make that handoff less ridiculous. Microsoft defines a skill as reusable instructions or a workflow for a task in its Tools overview. Think of it as a place to keep the department's method, rather than asking everyone to reconstruct it from last week's conversation.

The sharing detail worth knowing

The public reproduction of Microsoft's October 9 notice, MC1493223, describes skills coming to Microsoft 365 Copilot Chat. Users can create, edit, upload and share them. The announced rollout runs from October through mid-November 2026, so check actual availability before telling everybody to use it.

There's a wrinkle: skills created in Chat can also be used in Cowork. Skills created in Cowork become available in Chat only if they are shared, according to that notice. For organizations using Information Barriers, support starts in November, and sharing user-created skills is not supported initially.

That is not quite “make it once and forget where you made it.” Write down where the skill was created and where colleagues should find it.

Start with one department's recurring job

Here's an illustrative starting point for an operations team: a weekly update that always includes completed work, delays, decisions needed and the person responsible for each next step. Put that structure into the instructions. Tell Copilot to flag missing information instead of filling the gaps with optimism.

Then ask a colleague with authorized access to try it against a non-sensitive practice example. Compare the output with what the team actually needs. This is a suggested exercise, not a Newsdesk-tested result.

Skills can include supporting files or scripts, and the notice says relevant skills can be invoked automatically, with an option to disable that behavior. Review what you're sharing. Don't assume a skill grants access to its underlying data or that a work account establishes every entitlement.

Give the skill an owner, too. Otherwise you've just found a more sophisticated place to store instructions nobody maintains.