Microsoft is quietly replacing the topic model in Copilot Studio with skills — markdown playbooks an agent discovers and follows at runtime. Everyone’s talking about the authoring change. Almost nobody is talking about the governance problem it ships with.
Here’s the mechanic that matters: a skill activates when its description matches user intent. The description is a retrieval query. Which means two skills with overlapping descriptions aren’t redundant documentation — they’re nondeterministic routing. The agent picks one. You don’t control which.
And the first skills every org will write are the unglamorous ones: which status field is source of truth, how the SLA actually gets calculated, what each pipeline stage means. Tribal knowledge that today lives in five agents’ instructions, drifting independently. The moment it becomes discoverable, it becomes collidable.
The good news: business skills land as Dataverse records (preview today). User-owned, RBAC-shared, solution-aware. So the fix is boring and already exists — a registry. A model-driven app over the skills table, with similarity flagging and a review gate before anything goes org-visible.
Here’s the part I like: the librarian doesn’t have to be a person. The same MCP server that serves skills to agents can serve them to a governance agent — one that inventories every skill, flags semantic overlap, and proposes consolidation for a human to approve. Agents keeping the agents’ knowledge clean. The platform governing itself.
Topic sprawl was visible — open the canvas, count the nodes. Skill sprawl is invisible until two playbooks disagree mid-conversation.
Trustworthy autonomy is an architecture problem, not a model problem. This is that, at the most unglamorous layer.