Publish Skills

Publish skills as registry entries with clear usage contracts. The registry can expose metadata and docs without exposing implementation source.

Skill contract

A production skill should define:

• Name without the old skill- prefix.
• Category, tags, and short description.
• Free or premium pricing.
• Input schema.
• Output artifact contract.
• Approval requirements.
• User-facing docs.

Source-free distribution

Remote premium skills should publish docs, metadata, pricing, and run contracts. They should not publish private provider code or worker internals to local agent folders.

Validate before release

skills validate <name>

skills run <name> --json

Documentation expectations

Good docs show the command, required inputs, expected artifacts, pricing behavior, and failure modes. They should avoid internal provider names unless the user explicitly needs that information.