Team library
Use your organisation's shared prompts as /org commands and its skills in every session, offline from a cache, and hide what you do not want.
When you are signed in to Venom Cloud (venom cloud login, or VENOM_CLOUD_URL and VENOM_CLOUD_KEY), venom uses your org's library: prompts and skills its admins publish in the console. Without a sign-in there is no library and venom makes no call for it.
Quick start
/library prompts and skills, versions, cache age
/org:review file=src/a.ts focus="error handling" be strict
/skill:incident-runbookvenom library list
venom library show review
venom library syncPrompts
Org prompts are slash commands named /org:<name>, so they never collide with yours.
name=valuesets a declared parameter ({{name}}in the prompt); quote values with spaces. A missing parameter takes its default; a required one with no default stops the command and nothing is sent.- Everything else is free text:
$ARGUMENTS, or$1,$2,${1:-default}by position. A prompt that uses none of these getsARGUMENTS: <text>appended. - The text is expanded once and sent as your message (your
UserPromptSubmithooks still run). Nothing in it runs, an org prompt grants no tools, and it changes no model. - A/B tests. An admin can test two versions of a prompt. venom picks your session's version from its id (the same on resume), tells you which, and reports once to your org's Cloud that the session ran that arm (never the text or your arguments).
/librarymarks such prompts[A/B test].
Skills
Org skills join your skills at session start. For skills of the same name, yours win over the org's and the org's win over venom's built-ins, except that an item the org marks required replaces a local skill of its name (venom says which). Skills in ~/.venom/agent/skills and a trusted project's .venom/skills load first and keep their name.
Configuration
library:
hidden: [org:standup, release-notes] # a name, org:<name> for a prompt, skill:<name> for a skill| Key | Type | Default | What |
|---|---|---|---|
library |
object | the section | |
library.hidden |
list of strings | [] |
items you do not want; required items ignore it |
Commands
| Command | What |
|---|---|
/library [list] |
prompts and skills: version, [required], [hidden], which wins, the org, the cache's age |
/library refresh |
sync now; the session reloads its skills and commands if something changed |
venom library list [--json] |
the same list from the shell |
venom library show <name> |
a prompt (name or org:name) or skill: text, parameters, files |
venom library sync |
fetch now (exit 0 updated or unchanged, 1 failed) |
Skills from the org's registry
Skills your admins publish in the skills registry arrive through the same sync, with no release. Each
loaded one is a command, /<name> [args], listed in the / menu with the organisation's name; it sends the skill's instructions
with your arguments, so the text enters the conversation only when you run it. The system prompt holds just its name and one line.
/skill:<name> runs it too, and /library marks it. venom checks each registry skill's hash before it writes it (a skill whose files
do not match is skipped, with a diagnostic), a skill your admins disable or take out of your scope disappears at the next sync, and the
cached copy keeps working offline. A name another command already has keeps that command.
Offline and privacy
The library is cached in ~/.venom/cache/library/<id>/, one directory per Cloud and key (the key itself is never written). venom syncs at start next to the policy, within the same 3 seconds, and uses the cache when the Cloud does not answer. -p reads the cache without syncing; venom serve and venom acp read it too. venom counts how often you run each org prompt and skill and sends only the counts with the next sync.
Related
- Session templates (org prompts tagged
template) - Skills and slash commands