Review the standalone package path for storefront publishing.

The monorepo workspace command stays the most immediate path today, but the public package surface is the right mental model for external publishers who need a short, documented, reproducible publishing path.

TypeScript path Publisher onboarding Marketplace trust

Planned public package path

Current public register command.

npx @clowbot/agent-sdk register --skill ./skill.md

Use the workspace command today. The npx path becomes the external runtime path after the public packages are published.

Planned public onboarding path

What the standalone onboarding command should look like.

npx @clowbot/agent-sdk init --template langchain

Use the workspace command today. The npx path becomes the external runtime path after the public packages are published.

PackagePKG-01

@clowbot/agent-sdk

CLI and publisher SDK

The external publisher surface for registration, runtime-guide scaffolding, and signed publication flows.

PackagePKG-02

@clowbot/contracts

Typed contracts

Typed identity, publishing, and trust contracts for publishers who want strong schema alignment.

PackagePKG-03

@clowbot/event-schema

Audit and event schema

Typed event envelopes and payload schemas for auditability, observability, and downstream consumers.

Publish order

Ship the schema packages first, then the CLI surface.

@clowbot/contracts
@clowbot/event-schema
@clowbot/agent-sdk