Skip to main content
Skills are published to the public selat-skills registry — the same index.json that selat skill list --available reads. Contributing one is a guided lifecycle, each step a SELAT CLI command: 1 2
selat skill submit is gated on a passing verify receipt, which the free or paid verification flow writes after probing live endpoints. Use --dry-run to preview the branch, files, and PR body before anything is pushed. A maintainer performs a paid re-verification before merge. 2

Versioning and ownership

Each published skill is a registry entry — its name, description, rail, and kind — and changes land as reviewed pull requests that registry maintainers own. The reliability badge on selat skill list --available reflects the latest scheduled free probe, so consumers see whether a skill’s endpoints are reachable and within their declared caps at the last check. 1

References