Publish a Skill guide
Publishing splits across two surfaces on purpose. You validate and pack locally
with cmdop skill check --strict and cmdop skill pack, which never execute
your code and never touch the network — then you publish a saved revision from
the web console, which needs a Cmdop platform key on that device. The CLI has no
publish command at all, and that is deliberate rather than missing.
Publishing a Skill has two halves, and they live in different places on purpose.
1. Validate and pack locally
cmdop skill check ./my-skill --strict
cmdop skill pack ./my-skillThese commands are offline: they never execute your Skill’s code and never reach
the network. pack requires a warning-free strict check and prints the
sha256: digest that identifies the artifact. See
Write your first Skill for the full
authoring loop.
2. Publish from the console
The CLI does not publish — the console does. Open the Skill-authoring workspace in the web console and publish a saved revision. It packs the project and ships the release. Publishing requires a Cmdop platform key on that device.
Publishing resumes rather than restarts: a release already waiting on review or validation stays where it is instead of being duplicated, so re-running it after an interruption is safe.
What each surface owns
| Surface | Owns |
|---|---|
cmdop skill check / pack | Offline validation and the artifact, including its digest. |
| Console Skill-authoring workspace | Preparing a release and publishing it to the marketplace. |
| The marketplace | Discovery. A public listing is not proof that a Skill is installed anywhere. |
| Local Cmdop | Installed state on this machine — see Use installed Skills. |
For the lifecycle boundary between these, see Publication status.
Common questions
How do I publish a Cmdop Skill?
Validate and pack the Skill locally with cmdop skill check --strict and
cmdop skill pack, then publish a saved revision from the web console. The CLI
does not publish.
Why is there no cmdop skill publish command?
Publishing belongs to the console because it needs the platform publishing surface and a Cmdop platform key on that device. The CLI owns offline validation and packaging only.
Can I safely rerun publishing after an interruption?
Yes. Publishing resumes a release that is already waiting on review or validation rather than duplicating it.
Cmdop