About the Enclaw Marketplace
A central catalog for the things teams build on top of Enclaw — share once, install everywhere.
What it's for
The Enclaw Marketplace is where authors publish reusable building blocks — skills, integrations, agents, workflows, and squads — and where tenants install them with one click. Build a CSV-to-markdown skill, an opinionated sprint-planner agent, or a six-step launch workflow once, and the rest of the network can run it without redoing the work.
Every listing is reviewed by a platform operator before it goes public, so installing from the catalog is a known-safe operation rather than a roll-the-dice on internet code.
What you can publish
| Kind | What it is | Cloned on install? |
|---|---|---|
| Skill | A callable tool — wraps an API, runs a transformation, calls an external service. | Reference (bound via tool-registry) |
| Integration | Auth + tool family for an external service — Slack, Notion, Linear, etc. | Reference + tenant supplies config |
| Agent template | Pre-built agent: identity prompt, model defaults, default skills. | Yes — cloned into agent_templates |
| Workflow template | Frozen multi-step workflow with a trigger (cron, webhook, manual). | Yes — cloned into workflow_templates |
| Squad template | Multi-agent collaboration recipe — roles, handoffs, shared memory. | Yes — cloned into squad_templates |
How publishing works
- Sign in with GitHub. Publishing requires a GitHub identity — the marketplace uses it for authorship and audit trails. Anyone can sign in; admin permissions are granted separately by the operator.
- Submit a listing. Use the in-portal Publish wizard or the CLI (
@enclaw/marketplace-sdk) — same endpoints, same shape. - Review. Status flips to
pending_review. A platform operator approves or rejects; you can see the reviewer's notes in My Listings. - Approved. Status flips to
approvedand the listing shows up in the public catalog. Subsequent versions follow the same review path; old approved versions stay installable so existing tenants don't break.
Architecture
The marketplace is a standalone Next.js app, served at a dedicated hostname. Its browse / publish / admin pages and its API routes all live on the same origin — no cross-origin call back to the Enclaw API for the marketplace's own operations.
Storage is its own dedicated PostgreSQL Flexible Server (enclaw-marketplace-db-<env>), separate from the customer Enclaw instances. Authorship identity (marketplace_users) comes from GitHub OAuth, distinct from a tenant's normal user table — leaked customer creds can't publish to the marketplace and vice versa.
When a tenant installs from the marketplace, the assets are copied into the tenant's own Enclaw instance: agent / workflow / squad templates become first-class rows in the tenant's tables, skill payloads register into the tenant's tool registry. Tenants can edit their copy without affecting the source listing, and a future publisher update doesn't overwrite local customisations.
Get started
- Browse the catalog — see what's already published, filter by kind.
- Read the authoring guide — manifest shape, per-kind payload schemas, worked examples.
- Open the Publish wizard — sign in with GitHub and submit your first listing.