Skip to main content
Workspace admins control how skills enter the shared library.

​
Policies

Open Administration → Skills to configure these policies.

​
Review flow

1

Create personally

The author can test and revise the skill without exposing it to the workspace.
2

Submit for review

The skill enters the admin review queue and remains personal while pending.
3

Review the content

An admin reads the exact SKILL.md, description, source, and proposed scope.
4

Approve or reject

Approval publishes the skill to the workspace. Rejection leaves it with the author for revision.

​
What to review

Before approving a skill, confirm that it:
  • Has a clear trigger and outcome
  • Uses only the access needed for its task
  • Does not embed credentials or tenant-specific secrets
  • Points to stable context instead of one person’s local paths
  • Handles destructive or expensive actions explicitly
  • Includes source and reference files that reviewers can inspect
Importing a skill copies its current content into your library. Treat external instructions and bundled files as untrusted until someone reviews them.

​
Manage shared skills

Admins can manage team and workspace skills. Skill owners manage their personal skills. Access to a skill never expands access to the services the skill mentions; service and tool policies still apply at runtime.

Administration

Connect the admin MCP and govern the rest of the workspace.