Share skills with your organization
The console's Skills pages give your organization one catalog of approved agent skills. An administrator imports skills from a public Git repository and grants each one to directory groups. Users then browse the skills their groups can see and download them from the console.
The Enterprise Manager stores this catalog. The skills that the Stacklok CLI
installs with thv skill install come from a separate catalog on the
Registry Server.
Prerequisites
- The platform admin grant to import and grant skills. Users only need to belong to a group you grant a skill to.
- A public Git repository that the Enterprise Manager can reach over HTTPS, with each skill in its own folder. See Prepare the repository.
In the console, select Administration under Experience in the account menu, then open Skills.
Prepare the repository
The import reads the repository's default branch. Each folder that contains a
SKILL.md file is one skill, and the skill holds every file under that folder.
Put each skill in its own folder: a SKILL.md at the repository root isn't
imported.
Each skill follows the Agent Skills format that ToolHive installs, with these rules:
- The
namein theSKILL.mdfrontmatter matches the folder name. It uses lowercase letters, digits, and single hyphens, and is 2 to 64 characters long. - The frontmatter has a
description. - The folder holds at most 100 files, each at most 2 MiB, and at most 10 MiB in total. It contains no symlinks, Git submodules, or executable files.
The import rejects a folder that breaks a rule and names the rule in its result. The other folders still import.
Import skills from the repository
- Select Configure source.
- In Repository URL, enter the repository's HTTPS URL, for example
https://github.com/<OWNER>/<REPO>. - Select Set up source.
The import can take a few minutes, and the dialog stays open until it finishes. The result shows how many skills were imported and lists rejected folders with the reason for each.
Imported skills start with no groups, so no user sees them yet. Grant them to groups next.
The console holds one source at a time. To switch to another repository, delete the source and configure the new one. Users see no skills in between.
Grant skills to groups
A user sees a skill when it's enabled and granted to at least one of their groups. The Access column shows how many groups each skill is granted to.
To change the groups for one skill, open the row's menu and select Edit access. Select or clear groups, then select Save. If you clear every group, the console asks you to confirm, because no user can see the skill afterward.
To change the groups for many skills at once:
- Select the skills' checkboxes. The header checkbox selects every skill, up to 500 at a time, across all pages.
- In the selection bar, select Assign groups or Remove groups.
- Pick the groups, then select Assign or Remove.
Assigning adds the groups to each selected skill and keeps the groups it already has. Removing takes away only the groups you pick.
Disable a skill
To hide a skill from every user and keep its groups, open the row's menu and select Disable. The row shows a Disabled badge. Select Enable to make the skill visible again to the same groups.
Update skills from the repository
The Enterprise Manager reads the repository only when you ask it to. To pick up changes, select Update all, then select Update all in the dialog. Each skill folder in the repository is compared with the stored copy:
| Folder in the repository | Result |
|---|---|
| New | Imported with no groups |
| Changed | Stored copy replaced. The skill keeps its groups and its enabled or disabled state. |
| Unchanged | No change |
| Breaks an import rule | Rejected. The stored copy stays as it was. |
| Removed | Skill kept and marked Missing from source. Users who could see it still see it. |
An update never deletes a skill, so you can run it again safely. To hide a skill that's missing from the source, disable it.
Delete the source
Select Delete source and confirm. Deleting removes the source, all its skills, and their group access, so users lose access to every skill. You can't undo a delete. If you configure the same repository again, its skills import as new skills with no groups.
Download a skill
Any user can do this, including administrators in the user experience.
- In the console, open Skills. The list shows the skills your groups can see, with each one's description, number of files, and size.
- Select a skill to open its summary.
- Select Download to save the skill as
<SKILL_NAME>.zip. - Extract the zip into your AI client's skills directory. The zip holds one
folder named after the skill, for example
~/.claude/skills/<SKILL_NAME>/for Claude Code. The client compatibility page lists which clients support skills.
Your client picks up the skill the next time it loads its skills.
Next steps
- Manage users and groups to organize who receives each skill.
- Configure the Registry Server to serve skills that users install with the Stacklok CLI.
Troubleshooting
Skills is missing from the navigation
The Skills pages need the Enterprise Manager's directory service. Check that the console can reach the Enterprise Manager. The administration page also needs the platform admin grant.
A user can't see a skill
Check that the skill has no Disabled badge and that its Access column counts at least one group. Then check that the user belongs to one of those groups in User management.
An import or update ends with an error
The import or update can keep running after the dialog reports an error, for example when a proxy in front of the console times out. Close the dialog and reload the page to check the result before you try again. If the source exists, the console shows Update all instead of Configure source.