Omniscio

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

Team sharing hands a skill, an automation, a saved prompt or a document to other people, either as a one-off share code you send however you like, or through a members-only Team Library shelf that everyone in the same workspace can install from in one click. Imports are inert, secret-scanned and size-guarded. Every change to the shelf goes through one server-side callable that checks who you are, so no client can write the library directly, and the library keeps itself small. The Team Library is still off by default.

On this page

What it is

A way to hand a skill, an automation (recipe), a saved prompt (Super Prompt), or a document 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.

A library item is one of four kinds: a skill, a document (PDF, Word, Markdown or plain text, up to 25 MB), a saved prompt, or an automation. Each kind says how it installs, and a document opens read-only rather than installing anything.

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

  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.
  • Publishing the same item again does not create a duplicate: it adds a version to the item everyone already has, and the shelf shows the newest one.
  • A workspace owner or admin can also approve an item for everyone, decline it with a reason, restore a removed one, and set the library's publishing mode and its team instructions — the standing notes an agent reads before it works in that workspace.

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.
  • The library is members-only, and read-only to every client — items live under your workspace (organizations/{orgId}/sharedLibrary or chatWorkspaces/{wsId}/sharedLibrary). A member may read them; every direct client create, update and delete is refused by the cloud rules. One server-side callable (workspaceLibraryWrite) is the only writer, and it checks that the caller is a live member of that workspace before it writes anything.
  • The role decides the action — publishing needs a member; taking a new version of an item, or removing it, needs the author or a workspace admin; approving, declining, restoring and setting the library's publishing mode or instructions need an owner or an admin.
  • A repeated request applies once — every write carries a request id, so a retried click returns the first result instead of publishing twice.
  • A newer-version share code is rejected, not silently mangled into a lossy item.

What keeps the library small

  • 10 versions per item — the newest ten are kept; older ones are dropped as new ones are published.
  • A removed item is purged after 30 days, files and all. Until then it can be restored by an owner or admin.
  • Activity lines are kept for 90 days, and a holding area for files waiting on a cancelled write is cleared within 24 hours.
  • A workspace has 1 GB of library storage. A document is capped at 25 MB and an inline item at the shared-skill cap; storage is counted in the same transaction that stores the file, so the count and the bytes cannot drift apart.
  • An account deletion takes the person's library with it — the items they authored, their versions and files, the activity lines that name them, and their name on anyone else's item are all erased.

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.

Last verified 2026-11-16