Publishing

Every publish runs static safety + quality checks (manifest schema, name-matches-slug, size, path-traversal) before promoting to an immutable integer version. Findings are attached to the version.

On the skill page, owners get a Checks tab (build/CI results for the current version) and a Builds tab (every build, with logs); the Security audits are shown publicly.

From the CLI

From a skill directory (one with a SKILL.md), skst publish uploads it, runs the checks, and promotes the version on success:

skst publish                       # publish the current directory
skst publish --dir ./my-skill      # ...or a specific directory
skst publish --org acme            # publish under an org you belong to
skst publish --visibility unlisted # public (default) | unlisted | private
skst publish --no-auto-publish     # upload + check only, leave as a draft

Manage versions afterward with skst versions <owner>/<skill> and skst unpublish <owner>/<skill>.

From GitHub

Connect a repo on the skill page (grant repo access once). Pushes to the connected branch sync a new version automatically.

Drag-and-drop

Drop a .zip on the dashboard (new skill) or a skill page (new version) — we audit it and publish.

Limits

Up to 5 MB per skill artifact and 50 skills per account.