Skill Hub is the registry and distribution layer for SELAT skills. It is backed by the public selat-skills repository, whose index.json lists every published skill. The SELAT CLI reads this registry to discover, install, and publish skills.
Discover
Browse the registry, ranked with a live reliability badge per skill (● ok · ● degraded · ● down · ○ unknown) produced by the registry’s auto-verify checks:
selat skill list --available
selat skill install market-snapshot
Publish
Publishing a skill is a guided lifecycle. Each step has a CLI command:
| Step | Command | Purpose |
|---|
| Scaffold | selat skill new <name> | Create a new skill folder in the Agent Skill SOP layout. |
| Validate | selat skill validate <path> | Check the folder against the SOP (structure, required fields). |
| Verify | selat skill verify <path> [--pay] | Live-check each endpoint’s real 402 price and rail; --pay makes a capped real call and writes a receipt. |
| Register | selat skill register <path> | Add or update the skill’s entry in index.json. |
| Submit | selat skill submit <path> | Open a PR to the selat-skills repo. |
selat skill new my-skill
selat skill validate ./my-skill
selat skill verify ./my-skill --pay
selat skill register ./my-skill
selat skill submit ./my-skill # use --dry-run to preview the PR
selat skill submit is gated on a passing verify receipt — a skill can’t be submitted until its endpoints have been live-checked. Use --dry-run to preview the branch, files, and PR body before anything is pushed.
Versioning and ownership
Skills are versioned and owned through the selat-skills repository: each published skill is an entry in index.json, and changes land as reviewed pull requests. Registry maintainers own the merge; the per-skill reliability badge shown during discovery reflects the latest auto-verify run, so consumers can see at a glance whether a skill’s endpoints are currently healthy.
