Skip to main content
The one-shot publish for humans: packages the folder, shows the full manifest — target @org/slug, version bump, file list, total size, and every secret-excluded file — asks for confirmation, then uploads and publishes. path defaults to the current directory. Agents use the split flow instead — prepare then publish-draft — so the approval step is explicit in the conversation.

​
Options

​
Requirements and limits

  • The folder must contain a SKILL.md at its root.
  • Slugs are lowercase letters, digits, and dashes.
  • Package limits: 100 MB total, 50 MB per file.
  • You must be a member of the target organization.

​
Behavior worth knowing

  • Versioning is automatic — integer versions bump when content changes; the target version is part of the manifest you confirm.
  • Secret scanning runs twice — secret-looking files are excluded client-side and reported in the manifest; the server’s authoritative scan rejects findings with a 422 before any version is created. See Trust & approvals.
  • Adopt-on-publish — publishing a folder that lives in an agent’s global skills directory moves it into the central store and links it back, so it updates like any registry skill from then on. Repo-local folders are never touched.