Publishing

ClawNet publishing is a two-stage model:

1. Draft publish to the API (no funds required)
2. On-chain broadcast later using the stored signature

What Can Be Published

clawnet publish auto-detects the package type from the file or directory you pass in:

Target	Detection
Skill	SKILL.md or skill.md
Agent	A .md file with model and color frontmatter
Organization	COMPANY.md or ORGANIZATION.md
App	APP.md or app.md
Component registry	registry.json

If a directory contains both agents/ and skills/, ClawNet can infer an organization and synthesize an ORGANIZATION.md for publish.

Skill Format

Skills follow the Agent Skills spec (https://agentskills.io/specification). Required frontmatter:

• name -- slug identifier
• description -- what the skill does and when to use it
• version -- semver

Optional: homepage, tags, allowed-tools, compatibility.

Draft Publish

clawnet publish [path]

Validates the detected manifest, runs a content scan, collects package files, and stores a draft in the API. If you have a signing key, ClawNet also generates an OP_RETURN and AIP signature for future on-chain broadcast.

Examples:

clawnet publish .                    # auto-detect from current directory
clawnet publish agents/researcher.md # publish a single agent
clawnet publish ORGANIZATION.md      # publish an organization
clawnet publish . --on-chain         # publish and fund on-chain immediately

What Else Works Today

Publishing support is broader than discovery and install support.

Type	Publish	CLI install/add	CLI info	CLI search	Web browse
Skill	Yes	Yes	Yes	Yes	Yes
Agent	Yes	No direct install	No	No	Yes
Organization	Yes	Yes	Yes	No	Yes
App	Yes	No	No	No	No
Component registry	Yes	No	No	No	No

Notes:

• clawnet add <slug> installs a skill
• clawnet add <org-slug> installs an organization roster: agents plus skills
• clawnet search still searches skills only
• The web UI currently exposes skills, agents, and organizations, but not apps or component registries

Enable Cryptographic Authorship

clawnet setup-key

Creates a signing key for AIP authorship. Once set up, all future publishes include a cryptographic signature.

On-Chain Transaction Format

When broadcast, the transaction uses three protocols:

• B protocol for markdown/content payloads
• MAP protocol for metadata (name, version, description, homepage, type)
• AIP for the author signature (linked to BAP identity)

Updates reference the prior version via MAP SET ... prev <prior-txid>.