Skip to main content
Open Admin → Skills to set these policies.

​
Review a skill

  1. The author creates the skill as personal and tests it.
  2. The author submits it for review. It stays personal while it waits.
  3. An admin reads the SKILL.md, description, source, and proposed scope.
  4. The admin approves it, which publishes it to the workspace, or rejects it, which returns it to the author.

​
What to check

Before approving a skill, confirm that it:
  • Has a clear trigger and outcome
  • Uses only the access it needs
  • Contains no credentials or tenant-specific secrets
  • Refers to stable context, not one person’s local paths
  • Handles destructive or expensive actions explicitly
An imported skill is a copy of someone else’s instructions and files. Treat it as untrusted until someone has reviewed it. Access to a skill does not grant access to the services it mentions. Service and tool rules still apply when the skill runs.