Team sharing (share skills, automations & saved prompts with teammates)

What it is

A way to hand a skill, an automation (recipe), or a saved prompt (Super Prompt) to other people — either as a one-off link or through a shared team shelf. Before this, the only way to move a skill or prompt between installs was to copy files by hand; automations could go to the public marketplace but not privately to your own team.

There are two surfaces:

1. Share links — the "Share" button on a skill or a saved prompt (and the existing share flow on an automation) produces a short share code: a self-contained text string, no cloud involved. You send it however you like (chat, email); the recipient pastes it into Import a shared item to preview and install it. This works today for everyone.

2. Team Library — a members-only shelf, per workspace. A teammate publishes an item once and everyone in the same workspace sees it under a Team tab and installs it in one click. This is in development, off by default (the team-library flag). Cloud security rules are deployed and tested; the renderer data layer and list UI are wired; ready for final polish and release.

Where to find it

The Share button on a skill (Skills panel) or a saved prompt (Super Prompts) opens the Share dialog. Import sits in the Skills sidebar header, and the Team tab of that sidebar lists everything shared with your workspace.

How it behaves

How to use it

Send a share link

1. Select a skill (Skills panel) or a saved prompt (Super Prompts), and click Share.
2. The Share dialog shows a copyable share code, warns if the item looks like it contains a secret (an API key, a personal file path), and — for a skill too big to fit a link — tells you so instead of sending a broken partial copy.
3. Copy the code and send it. A share link exposes the item's contents to anyone who receives it, so don't post it publicly.

Import a shared item

1. Click Import in the Skills sidebar header. Paste the code.
2. You see a preview — what kind it is (skill / prompt / automation) and its name/contents — before anything is installed.
3. Confirm to import. Nothing runs on import: a skill lands as files in your skills folder (never executed until you use it), a prompt lands in your library, an automation lands paused until you approve it. A skill import shows a "only import from people you trust" note, because a skill can contain steps that run when you later use it.

Share to your team / browse the Team Library (when the flag is on)

• In the Share dialog, Share to your team publishes the prepared item to your workspace's Team Library.
• The Team tab in the Skills sidebar lists everything shared with your workspace; each row has Install (one click), and the person who published an item can Remove it. A workspace owner/admin can also remove anyone's item.

Safety model

• Inert on import — imported items never auto-run (files for skills, a row for prompts, a paused recipe for automations).
• Secret-scanned before a code exists — the same advisory scanner flags key/path shapes for all three kinds; you decide whether to strip and continue.
• Skills are size- and path-guarded — an over-cap skill is refused (never silently truncated), and every file path is checked so a shared skill can't write outside its own folder.
• Team Library is members-only — items live under your workspace (organizations/{orgId}/sharedLibrary or chatWorkspaces/{wsId}/sharedLibrary); only members can read, only a member can publish their own item, and only the creator or a workspace owner/admin can remove one. Enforced by the cloud access rules, not just the UI.
• A newer-version share code is rejected, not silently mangled into a lossy item.

For agents

Notes for agents

• Not the same as "Shares" (public artifact publishing, shares/{token}). Team sharing uses the shared-item:* IPC channels and the sharedLibrary collection. Contract: team-sharing-contract.md.
• The share/import engine is in the main process (src/main/services/skills/skill-share.ts, src/main/services/share/share-import-service.ts); the Team Library data layer is in the renderer (src/renderer/src/features/team-library/) via the same Firestore client Team Chat uses.
• Turning the Team Library on is a separate, gated step: flip team-library to shipped in the unreleased features registry. Cloud security rules are already deployed and tested (org + workspace roots). The renderer data layer (library-client.ts) and list UI (TeamLibraryList.tsx) are wired.

Related

Use Skills and Use Super Prompts cover the two libraries a shared item is imported into, and both carry the Share and Import controls described here. Share Artifacts is a different feature with a similar name: it publishes a public link to a file or pasted content, where team sharing keeps an item inside your workspace.