Skill publishing reference
Publishing a Cmdop Skill to the marketplace happens in the web console, not on the command line — the authoring commands are deliberately offline and never reach the network. Publishing packs the project, prepares a release, uploads the artifact, and lists it. A listing is discovery; it installs the Skill nowhere.
Publishing happens in the browser, not on the command line.
The CLI does not publish. cmdop skill create, check, and pack are
deliberately offline — none of them reaches the network. That is the boundary:
authoring is local and verifiable, publishing is an explicit online action you
take somewhere else.
Publish from the web console
- Open the Skill-authoring workspace in the web console.
- Save the revision you want to publish.
- Publish it.
Cmdop packs the project, prepares a release, uploads the artifact, and publishes it to the marketplace. The machine you publish from needs a Cmdop platform key.
Publishing resumes rather than restarts. If a release is already waiting on review or validation, publishing again leaves it where it is instead of creating a duplicate.
The artifact’s identity is its digest
cmdop skill pack prints a logical sha256: digest. That digest identifies the
Skill’s canonical metadata and uncompressed file bytes — it does not depend on
the output path, file timestamps, umask, or ZIP metadata. Two people packing the
same project get the same digest, which is what makes a published artifact
verifiable.
Packing requires a warning-free --strict check, and it will not overwrite an
existing artifact. See Validate a Skill.
What publishing does not do
A published listing is discovery. It does not install the Skill on anyone’s machine, and it does not make an executable Skill runnable — executable Skills still wait on an enforcing isolation runtime. See Runtime status.
Related
Common questions
How do I publish a Cmdop Skill?
Publish from the web console. The CLI owns offline authoring, validation, and packing; the browser publishing workflow prepares the release, uploads the artifact, and lists it.
Does publishing install the Skill anywhere?
No. A marketplace listing is discovery. It does not install the Skill on any machine and does not make executable Skills runnable.
Why does publishing use a digest?
The digest identifies the Skill’s canonical metadata and uncompressed file bytes. It lets the same project produce the same identity regardless of output path, timestamps, or ZIP packaging details.
Cmdop