# Share skills and agent instructions with your team

> Publish skills, CLAUDE.md and AGENTS.md, slash commands, subagents and Cursor rules to your workspace's team library, review them, and keep every teammate's agents on the same approved versions.

Source: https://docs.agentbeam.com/cookbooks/skill-sharing

The team library is how a workspace shares what makes its agents good: skills, project instructions (`CLAUDE.md`, `AGENTS.md`, `GEMINI.md`), slash commands, subagents and Cursor rules. Shares are scanned on the way in and again on the way out. They can require an administrator's review, and they're versioned, so everyone runs the same approved copy.

## What you'll have

- Your team's best skills and instructions in one library, in the CLI and under **Team library** in the dashboard.
- A review step for anything risky, or for everything if you choose.
- Every teammate installing with one command and staying up to date.
- An audit trail of every publish, approval and deletion.

## Before you start

| You need | Who | Why |
| --- | --- | --- |
| A machine connected with `beam setup` | Everyone sharing or installing | Shares belong to the workspace |
| Owner or admin role | Step 2 | Library settings and reviews |

## Step 1: Publish

```sh
beam share ./.claude/skills/release-checklist                     # a skill folder; the kind is detected from the path
beam share ./CLAUDE.md --name "Backend conventions" --description "How we write and test backend code"   # installs as backend-conventions
beam share ./.claude/commands/review.md                           # a slash command
beam share ./.claude/agents/migration-reviewer.md                 # a subagent
beam share ./.cursor/rules/api-style.mdc                          # a Cursor rule
```

Beam lists every file it will upload and shows its own scan before asking you to confirm. Hidden files, `node_modules`, symlinks and non-text files are left out, and each one left out is listed. If a file contains an API key, token, private key or a password in a URL, nothing is uploaded and the error names the file and line. Limits: 100 files, 128 KB a file, 512 KB a share.

To publish a new version, run the same command again with a note:

```sh
beam share ./.claude/skills/release-checklist -m "Covers database migrations"
```

Only you or an administrator can publish a new version of your share.

A share's install name is its name in lowercase with dashes ("Backend conventions" becomes `backend-conventions`).

**Check:** `beam share list` shows it.

## Step 2: Decide how much review you want

Under **Team library** in the dashboard, owners and admins choose the sharing setting:

- **On · review risky shares** (the default): the workspace scans every upload. Clean shares publish at once; prompt injection or another high-risk finding sends a share to an administrator for review before anyone can install it.
- **On · review every share:** every new share and version waits for an administrator.
- **Off · nobody can share:** the library is read-only. Existing shares can still be installed.

Reviewers approve or reject from **Team library**. Every publish, approval, rejection and deletion is in the audit log.

## Step 3: Install what teammates shared

```sh
beam share list                                       # everything shared, with kinds and versions
beam share list --kind skill
beam share install release-checklist                  # the newest approved version, into this project
beam share install release-checklist --all-agents -g  # for every supported agent, for your user
beam share install release-checklist@3                # pin version 3
```

Before anything is written, Beam checks the download against the workspace's content hash, re-validates every path and runs its full skill scan on your machine. Files go only inside the install folder, and never as executables. A file Beam didn't install, or one you've edited, is left alone unless you pass `--force`, which keeps a backup.

## Step 4: Stay current

```sh
beam share update                     # every installed share, to its newest approved version
beam share update release-checklist   # just one
```

Put `beam share update` in your team's onboarding notes and your dev container setup, so new machines start with the same skills and instructions as everyone else.

## Step 5: Onboard a new teammate in two commands

```sh
npm i -g @agent-beam/beam && beam setup
beam share install backend-conventions && beam share install release-checklist --all-agents
```

## Step 6: Retire a share

```sh
beam share delete release-checklist
```

It leaves the library; copies already installed stay where they are until their owners remove them.

## Coverage checklist

| Feature | Done when |
| --- | --- |
| Library seeded | Your team's key skills, instructions and commands are shared |
| Review policy | **Team library** settings match how much review you want |
| Installs | Teammates install with `beam share install` |
| Updates | `beam share update` is part of onboarding and dev containers |
| Audit | Publishes and approvals show in the audit log |
| Testing | Shares were tested with the [skill testing cookbook](https://docs.agentbeam.com/cookbooks/skill-testing) before publishing |