Publish Skills

Create and validate local OSS skills with the public package. Skills.md does not currently advertise customer skill publication; publishing to a separate compatible instance depends on its capabilities and your permissions. The hosted catalog can expose metadata and docs without exposing private implementation source.

Skill contract

A production skill should define:

• Lowercase hyphenated name, such as customer-feedback-report, 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

Use a local OSS configuration for these commands; do not select the Skills.md customer profile to test an unpublished local skill.

skills validate <name>

skills run --json <name>

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.