Skip to content

Packaging and installation

A persona package brings together the root skill, published configuration, portable definitions, and pins for linked resources. The root commit versions the local files. Registry entries identify the exact linked definitions the runtime should import.

Publish child definitions first, then the persona root with updated pins. A workspace verifies the published definition and supplies its own resource bindings and grants. A compiled custom app follows the app package and installation contract. A self-hosted appliance can import a separately compiled, signed release candidate.

See publishing and reuse and custom app packages and installations.

Gabriel distributes three package types as npm archives. The public marketplace uses npmjs.com by default. Private installations can use an administrator-configured npm-compatible registry such as Artifactory. Administrators allow registry URLs with GABRIEL_PACKAGE_REGISTRIES, a comma-separated list of HTTPS URLs ending in a slash. An install preview shows the exact versions and integrity digests, local bindings, and executable hooks.

Package Content Install destination
Playbook A structured or goal playbook, or a supported Studio graph, plus its saved skill files and pinned playbook dependencies. An existing team’s Canvas.
Team Purpose, Canvas placements, handoffs, portable team resources, and exact playbook pins. A new team in an existing persona workspace.
Persona A persona profile, optional ontology, logical resource requirements, and exact team pins. A new private persona and workspace.

An archive contains package.json, gabriel-package.json, and the manifest’s entry file. The playbook entry is playbook.json. A graph entry includes its authored files under graph/. The team entry is team.json. The persona entry is persona.json. A skill folder belongs to its playbook and lives under skills/<name>/. Package versions are independent of Studio’s local revision numbers.

Download the version 1 manifest JSON Schema. Registry allowlists, archive integrity, and exact version resolution are validated during installation.

Field Value
schemaVersion 1
kind playbook, team, or persona
title, description Display text for the release
entry The file that matches the package kind
runtime An object with contract: "gabriel-studio-v1" and a boolean hooks
dependencies An object mapping logical names to a registry URL, scoped name, exact version, and SHA-512 integrity digest

The persona installs the Accountants team. That team places Verify signals on its Canvas. Each manifest pins its child by exact version and SHA-512 digest. The archives below were built and validated together. The names are illustrative; the example releases have not been published to npm.

Package Manifest with exact pins Archive
@example/verify-signals@1.0.0 Playbook manifest Playbook archive
@example/accountants@1.0.0 Team manifest Team archive
@example/accounting@1.0.0 Persona manifest Persona archive

Publish under your own scope, starting with the playbook. When you publish the team and persona, Studio includes the digests verified against your registry. A new release of Verify stays independent until the team reviews and adopts it.

SKILL.md, references, assets, and bundled scripts follow the Agent Skills folder format. Gabriel adds eval files and supports BeforeTask and AfterTask in gabriel/hooks.json. In installed packages, those hooks invoke bundled Node scripts on a verified E2B Studio computer with Node.js 22 or newer and outbound networking disabled. They receive declared input or output fields and can stop the run. Connector credentials and approval authority stay in the destination workspace. Persona resource references are setup requirements. The installer records them in assets/package-resource-requirements.json so the destination owner can connect the appropriate resources. Agent Skills specification

Follow the package composition example.

A playbook requires a target team. A team requires a persona workspace. A persona creates a private workspace containing its packaged teams. In each case the package graph resolves before installation. The workspace supplies the accounts, role assignments, output bindings, compute, and permissions shown in the preview.

This is one dependency entry from the downloadable Accountants team manifest. The team pins the release whose authored skill and executable it will install.

{
"studio:verify-signals": {
"registry": "https://registry.npmjs.org/",
"name": "@example/verify-signals",
"version": "1.0.0",
"integrity": "sha512-a6FvGfHRNlp5W2u4Zt2vgfyp1n7PfBvFwVfjZIFcaLrkcKcwvnDfcrejSu/+ngEUv1377Xf2NN1njANZa7qigQ=="
}
}

Publish the child first and preview the new version of the package that uses it. Compare executable content, skill files, hooks, connector requirements, and changed Canvas placements. Review local skill edits before applying an update. Rebind or repair changed requirements before starting new work.

Inspect the installed package and the definitions that still use it. A team placement or another package’s dependency can block removal. Historical runs and their receipts remain available for auditing the revision that ran.

See marketplace discovery and installation and the package composition example.

Portable playbook archives declare gabriel-studio-v2 and use a version 2 playbook.json entry. See portable playbooks for the schema, package files, and runtime bindings.