Skill Sharing

Share a skill registered in your project with other people, and install skills others have shared into your own project. Installation creates a copy, so an installed skill belongs to your project, and revoking a share does not remove copies that were already installed.

Share scopes

Publish a skill under any of three scopes.

Scopes are not exclusive. The same skill can have a team share and a link share alive at once, and each is revoked separately. Each scope allows one active share per skill. Publishing a share that matches one that is already active returns “A share is already active”, so revoke it first and publish again.

Share options

With Include executable files on, the scripts under scripts/ and the files under assets/ are handed over as they are and get copied into the installer’s project as well. The share screen lists exactly which files will be included — check them for API keys, internal addresses, and other sensitive values before publishing.

Sharing from the web

Sharing is available to members with skill management permission in the project. A skill owned at Personal scope can only be shared by the member who created it.

1. Open Skills in the sidebar and select the skill you want to share.
2. Click Manage skill sharing at the top of the detail screen.
3. Pick everyone, team, or link under Share with. Picking team shares with the team of the project the skill belongs to.
4. Set include content, include executable files, allow installation, and the expiry date.
5. Click Publish share.

A link share shows the New share link after publishing. The link is shown only once, so grab it right away with Copy link. If you lose it, revoke the share and publish again to get a new link.

Active shares are listed under Published shares in the same dialog, each with its scope, the options in effect (metadata only, executable files excluded, installation disabled), and its expiry date.

Turn on the Shared by me filter in the skill list to see only skills that have a share published.

Sharing from the CLI

Run the sharing commands without --apply to see what would be published without changing anything on the server.

# Share with everyone
agentteams skill share --id <skillId> --scope public --apply
 
# Share with a team
agentteams skill share --id <skillId> --scope team --apply
 
# Share by link, including executable files, with an expiry
agentteams skill share --id <skillId> --scope link \
  --include-executable --expires-at 2026-12-31T00:00:00Z --apply

The link URL in the result is also printed only this once.

To see the shares you published and who installed them:

agentteams skill shares --id <skillId>

Installing a shared skill

Web

1. Open Shared skills in the sidebar. Shares visible in the current project appear together — those shared with everyone, and those shared with the team that project belongs to.
2. Search for the skill you want and click its card.
3. Review the list of included files. If the share includes executable files, a warning appears along with an I reviewed the executable files and agree to install checkbox that must be checked before you can install.
4. Choose the target Project, then click Install. For a team share the target team is locked to the share’s team; for everyone and link shares you can also choose a Team.
5. When it finishes, you land on the installed skill’s detail screen.

If the publisher disabled installation, the share shows a notice instead of the install button and you can only browse the files. A share published without the body cannot be installed either and shows the same notice.

CLI

# Browse shares visible in this project (everyone + this project's team)
agentteams skill browse
agentteams skill browse --search "review"
 
# List the files that would be installed
agentteams skill install --share <shareId>
 
# Install into the current project
agentteams skill install --share <shareId> --apply
 
# A share received as a link installs with the link token or the share link URL instead of a share ID
agentteams skill install --token <linkToken> --apply
agentteams skill install --token "<shareLinkUrl>" --apply

To pull the installed skill into your local .agentteams/skills/, run:

agentteams skill download --id <installed skillId>

What to know about installed copies

• An installed skill is an independent copy. Changes to the original do not reach it, and your edits do not reach the original.
• If a skill with the same name already exists, the copy is installed under a numbered name such as -2 or -3.
• Installing a share published without Include executable files does not copy any scripts/ or assets/ files.

What a link recipient sees

Opening a share link shows the skill name, version, the list of included files, and the SKILL.md and references/ content — no sign-in required. A share that includes executable scripts shows a warning at the top of the screen, and asset files are retrieved with Download.

Installing into your own project requires signing in. Follow the on-screen prompt to sign in, then install it on the same screen. Pick the target project and click Install.

A metadata-only share shows a notice in place of the content and cannot be installed.

Revoking a share

Once revoked, the share no longer opens from the list, detail screen, link, or install path. Copies that were already installed are not removed.

On the web, click Revoke in the Published shares list.

# Check which share would be revoked
agentteams skill unshare --id <shareId> --skill <skillId>
 
# Revoke it
agentteams skill unshare --id <shareId> --skill <skillId> --apply

A share whose expiry date has passed closes the same way. To share it again, revoke the expired share and publish a new one. Republishing a link share produces a new link, and the previous link stops working.

Related pages

• CLI — registering and syncing skill packages, and including assets/ files
• Conventions — deploying the rules agents follow