SharePoint already knows who can do what. Use that to stop the AI from offering skills your users can't actually run.
SharePoint sites already know who is allowed to do what. A skill that updates payroll only makes sense for HR. A skill that deletes archived files only makes sense for owners. If you leave every skill open to every user, the AI will happily suggest a skill the caller has no rights to actually execute — and the run fails halfway through.
The author's phrasing in the video: "Don't let users try to execute skills that won't actually work for them." Permissions are a first-class context signal — they tell the agent which moves are even legal for this person.
The Skills Library is the per-site catalogue of every skill installed in that SharePoint site. Open it and you see a list of skills with their triggers, descriptions, and — crucially — a permission column. Click any skill to manage who can use it, who can edit it, and who can't see it at all.
This is where you go to lock down sensitive skills, audit who is using what, or push a permission change after you've added a new skill. The same UI handles install and access.
An admin-only skill is one whose persona access has been narrowed so only site owners (or another designated group) can call it. In the demo the author creates a skill named "admin only," opens the Skills Library, finds the skill, and removes visitor access — visitors can no longer see or trigger it.
Use this pattern for destructive actions, finance flows, hiring workflows, or anything where a wrong person triggering the skill would cause damage. The skill still lives in the library — it's just invisible to the wrong audience.
Out of the box, visitors can leverage skills the owner has built but can't edit them. Members can edit. Owners have full control. You can override any of these per-skill — visitor read-only is a default, not a ceiling.
Always ask: "Should every persona who can use this site also be able to run this skill?" If the answer is no — even for one persona — open the skill in the Skills Library and tighten its access before publishing.