Library
Approved, versioned skills your team’s AI follows, served to Claude, ChatGPT and Codex through your connector.
The Library holds your organization’s skills: instructions your team’s AI follows, like how to review a deal. Each new version is reviewed by an approver before anyone is served it, and every version is kept, so you can pin one in place.
An approved skill shows up in the Smoo AI connector and in every brain connector within a few seconds, for everyone with access. There is nothing to install. Versions still in review, skills that are turned off, and versions with files that run code are never served.
How to
- 1
Create a skill, then submit its first version as a zip.
Zip the skill folder. Its SKILL.md must start with frontmatter whose name is the skill name you chose. The zip can be up to 4 MB (10 MB unpacked).
- 2
An approver opens Awaiting review, reads the files, and approves or rejects.
Nobody can approve their own version. Opening a version for review is recorded in the audit log.
- 3
Org admins choose the approval policy: one approver, two approvers, or trusted publishers.
Trusted publishers are approved on submit. You can’t list yourself; another admin has to. A version with files that run code always needs two approvers.
- 4
On the skill’s Install tab, turn it on or off, and pin a version if it should not move.
Without a pin, the org uses the newest approved version.
- 5
On the Access tab, choose who can use, submit or curate the skill.
- 6
Optionally, download the Claude.ai zip from the Install tab and upload it to Claude.ai.
If something goes wrong
- Submitting a version says the zip contains secrets.
- The message names the kind of key and the file it is in. Remove the key from that file, zip it again and resubmit. Nothing was stored.
- Submitting says the name must equal the item slug.
- The name in SKILL.md’s frontmatter must match the skill name shown on the skill’s page.
- An approved skill does not appear in Claude.
- Check that it is turned on, and that the person has access to it on the Access tab. A version with files that run code is never served over the connector.
- There is no Awaiting review tab.
- Reviewing needs the “Approve library versions” permission. Ask an org admin for it.