Team library and starter packs
Publish prompts and skills your members get in venom, version and roll them back, and install a vertical starter pack from the Venom Cloud console.
The Library holds prompts members run as /org:<name> in venom and skills the agent loads when a task
matches. Members get the published versions when venom starts (and offline, from their cache). Starter packs
set up gears, filters, library items, budgets, permissions and memory for a kind of practice in one step.
| Page | What it does | Read | Change |
|---|---|---|---|
/library |
the list: search, kind and tag filters, scope, status, runs over 30 days | routing:read (owner, admin, developer, viewer) |
org:manage |
/library/new |
a new prompt (?kind=prompt), skill (?kind=skill) or import (?import=1) |
org:manage |
|
/library/{id} |
one item: editor, live preview, who gets it, versions, usage, tests | routing:read |
org:manage |
/packs |
the starter pack catalog | routing:read |
org:manage to install |
/packs/{id} |
one pack: what it creates, the install form, uninstall | routing:read |
org:manage |
Publish a prompt
- Open
/libraryand choose New prompt. - Name it
review-pr(lowercase letters, digits and hyphens, no hyphen at either end, at most 64 characters), add a description and the body.$ARGUMENTSand named parameters are filled in when it runs. - Use the Try it box to see the expansion exactly as the CLI does it.
- Choose who gets it (the whole organisation or some key groups) and whether it is required.
- Publish with an optional changelog note (500 characters). The console answers "Published version 1."
Members then run it in venom:
/org:review-pr 1234They get new versions at the next venom start or /library refresh. The CLI side is described in
Team library.
Items and versions
| Field | Limit |
|---|---|
| items per org | 200 |
| name | 64 characters, [a-z0-9-] |
| description | 1024 characters |
| tags | 10, each 32 characters, lowercase letters, digits and hyphens |
| argument hint | 200 characters |
| parameters | 20; description 200, default 1000 characters |
| prompt body | 32 KiB |
skill body (SKILL.md) |
64 KiB, plus up to 20 supporting files of 64 KiB, 256 KiB in total |
| file path | 200 characters |
- Save draft keeps unpublished content; members keep getting the published version. Discarding the draft removes it.
- Publish turns the draft into the next version. Published versions never change.
- Roll back publishes an older version's content as a new version, so version numbers only grow. The history shows each version with Compare (a line diff between two versions).
- Who gets it: the whole org or a list of key groups (the API calls them teams), and
required(members may not hide it). A change applies at once to the published version. - Delete removes the item and every version; members' venom drops it at the next sync.
- Import reads a pasted or uploaded
SKILL.mdor command file in the browser. Nothing is fetched from the network.
On /library/{id} a prompt also has a Test card (run the golden tasks with version A and version B on an eval
runner, see Evals and experiments) and Test on live sessions, a prompt A/B test whose
results are at /experiments/prompts/{id}.
Every change is in the audit log as library.* with names, versions and hashes, never the text.
Starter packs
The catalog has three packs: legal (Law firm), accounting (Accounting practice) and clinics (Clinic). Each
pack's page lists what it will create: two gears (a private one that keeps client data on your daemons, and a local
one that never reaches the cloud), filter rules that redact identifiers before text reaches a cloud model, library
items, budgets, permission rules and memory facts.
The install form:
| Field | Default | Notes |
|---|---|---|
| Model for client data | a model your daemons serve | runs on your own daemons; if none serves a model yet, venom-auto picks one once they do |
| Cloud model for hard reasoning | none | not offered when the org is sovereign-only |
| Names to redact | empty | one per line (client, party or patient names), redacted as whole words before text reaches a cloud model; kept only in the filter rule |
| Monthly budget per private gear (USD) | the pack's suggestion | 0 for no budget; members are warned at 80% and the gear is blocked at 100% |
Preview shows what would be created without changing anything. Install creates each resource through its
own page's operation, with your permissions, and skips anything that already exists. Uninstall removes only what
the install created and is still there; library items it created are deleted with their versions. Installs are
audited as starter_pack.installed, plus each resource's own audit row.
Troubleshooting
| Message | Cause and fix |
|---|---|
| "Your library holds the most items it can (200)." | remove an item before adding another |
| "Your role cannot change the library (org:manage)." | only owners and admins edit; others can read and try |
| "Pick at least one key group, or choose the whole organisation." | the scope list was empty |
| "A name uses lowercase letters, digits and hyphens…" | rename the item, for example review-pr |
| "Installing a starter pack needs org:manage (owners and admins)." | ask an owner or admin |
| Members don't see a new version | they get it at the next venom start or /library refresh; drafts are never sent |
Related
- Team library: the CLI's side (
venom library,/org:<name>). - Marketplace and MCP servers: library skills also appear in the marketplace.
- Org memory: facts a starter pack can add.