Author and run Skills

cmdop skill is the current command tree. The plural cmdop skills remains a deprecated alias.

Create an offline Skill project

Create an instructions-based Skill, validate it strictly, then package it:

cmdop skill create release-check \
  --description "Review release readiness before deployment"
cmdop skill check ./release-check --strict
cmdop skill pack ./release-check

create, check, and pack do not execute Skill code. Packaging produces an artifact; it does not publish or install it. By default pack writes the archive into the Skill’s own dist directory — pass --output to put it somewhere else:

cmdop skill pack ./release-check --output ./artifacts/release-check.zip

Use --kind python or --kind node only when the Skill needs that project shape. Use --json with authoring commands in automation.

Work with installed Skills

cmdop skill list
cmdop skill show <name>
cmdop skill dir
cmdop run <name> "optional prompt"

Install and remove Skills from the marketplace:

cmdop skill install <slug>
cmdop skill install <slug> --version 1.2.0
cmdop skill uninstall <name>

--version pins an exact version; without it you get the current one. Review a Skill before installing it — an installed Skill runs with the agent’s permissions on this machine.

For a complete authoring walkthrough, see Write your first Skill.

Authoring versus running

Authoring commands work on a local project directory. Runtime commands work on installed Skills by name. Keep those two states separate: changing a source directory does not update an installed Skill until you package and install the new artifact.

Use strict checks before packaging. They catch missing metadata, invalid structure, and unsafe assumptions before the Skill reaches a machine where it can run with agent permissions.

Related

• Validate a Skill
• Publish a Skill
• cmdop run