atrium-publish

Publishing skills to an on-chain marketplace with per-call pricing is done by constructing metadata frontmatter and executing the flow via the Atrium CLI. The process builds publish requests with DID-signed provenance and records results to memory.

DID-signed provenance is a cryptographic attribution record embedded in skill frontmatter during the publishing workflow. It is needed for on-chain monetization to verify the author_did and establish traceable ownership of published skills.

Queue local skills for batch publishing by explicitly opting designated skills into the queue before execution. The publishing workflow operates only on these queued skills, processing them sequentially and handling secrets management for scalable monetization.

Yes, you can publish skills when local sources or secrets are missing because the workflow is bootstrap-safe. It gracefully handles missing sources and automatically bootstraps necessary secrets at runtime during the CLI execution.

Required metadata frontmatter to monetize skills on-chain includes name, version, author_did, description, tags, categories, language, runtime, price_per_call_usdc, parent_skills, created_at, and derivation_method. This frontmatter is constructed and validated before publishing.

Yes, the Atrium CLI handles queue management and secrets for scalable skill publishing. The workflow manages the queue of opted-in skills and bootstraps secrets at runtime, ensuring graceful processing and traceable recording of publish results.