Skip to content

Marketplace

A marketplace helps teams discover and review reusable playbook, team, and persona packages. The installation preview ties a specific release to the workspace where it will run.

Package Destination What the install creates
Playbook An existing team A playbook placement on its Canvas.
Team An existing persona workspace A team with pinned playbooks and handoffs.
Persona A new private workspace The persona and its packaged teams.

A listing identifies the package and its available versions. A team selects a specific release for review. Private releases can be resolved by exact registry reference when the destination has access.

The following exact reference uses the downloadable Accounting example’s illustrative release. Replace it with a release available in your registry before requesting a preview.

{
"registry": "https://registry.npmjs.org/",
"name": "@example/verify-signals",
"version": "1.0.0"
}

The preview identifies the destination, the exact version and digest of each dependency, the affected placements, connector operations, output bindings, and executable hooks. The workspace owner authorizes the reviewed installation. If the destination changed since review, generate a fresh preview.

A team goal can invoke an installed playbook after the workspace binds its required resources. Updates and removals should be reviewed against the installed revisions and their dependents. A marketplace lists packages people can discover. The npm-compatible registry supplies the archive and its release metadata.

See archive contents and pins and package composition and installation.