Skills governance

Skills spread. One person writes a good one, others attach it, and before long it's part of how the organization works. This is where you keep that healthy.

Who can do what

Task	User	Agent owner	Admin
Create a skill	✅	✅	✅
Attach a skill to their agent	— as Editor	✅	✅
See every skill in the organization	—	—	✅
Change a skill's status	—	—	✅
Change a skill's visibility	—	—	✅
Set which agents may author skills	—	—	✅
Assign a skill to agents in bulk	—	—	✅
Delete a skill	—	—	✅
Export a skill	—	—	✅

Organization → Skills.

The skills inventory

Every skill in the organization, with its status and which agents have it attached. The complementary view — every agent and the skills it holds — answers the other question: what is this agent actually capable of?

Bulk assignment attaches or detaches one skill across many agents at once, which is how you roll out a corrected version without visiting each agent.

Statuses

Status	Meaning
Draft	Being worked on
Pending review	Submitted for approval
Active	Available for use
Deprecated	Still works, shouldn't be adopted
Archived	Retired

Draft → Active is your approval gate. Deprecated is the useful one people forget: it keeps existing agents working while stopping new adoption, which beats deleting a skill out from under someone.

Visibility

Each skill is Private (this organization), Tenant (all agents here), or Public (discoverable by any organization). Set the organization's Default Skill Visibility Scope for new skills, and change any individual skill's scope.

Public is a real publication — treat it as one, and check the skill's instructions and files for anything organization-specific before promoting it.

Which agents may author skills

Agent Authoring Permissions controls, per agent, whether it can create skills at all, and the maximum visibility it may set:

Scope	The agent may create
Private only	Private skills only
Tenant allowed	Private or organization-wide skills
All allowed	Any visibility, including public

The default is private only, and the ceiling is per agent, not per user. An agent granted all allowed can publish to every organization on the platform, so grant it deliberately and to specific agents rather than broadly.

Deleting and exporting

Export produces a portable Agent Skills package — the right way to back up a skill, move it, or review its full contents outside the app.

Delete removes the skill from the organization, detaching it from every agent that had it. Export first if there's any doubt; prefer Archived when you only want it out of the way.

Keeping it tidy

• Review Pending review regularly. A queue nobody empties teaches people to route around it.
• Watch for near-duplicates. Two skills doing almost the same thing is worse than one, because agents pick unpredictably between them.
• Deprecate rather than delete, and delete only after nothing is attached.