Marketplace

Installing skills

Via CLI

cmdop skills install ssl-cert-checker

This:

1. Downloads the skill from the marketplace
2. Writes all files into the global skills directory (<data-dir>/skills/ssl-cert-checker/ — see Skill directories)
3. Writes meta.json with install metadata
4. Validates the skill
5. Creates a virtual environment and installs dependencies
6. Runs an optional verification check

Via deep link

A marketplace link or cmdop://skills/install/ssl-cert-checker opens the CMDOP desktop app on the skill’s detail card, where you confirm the install with one in-app click.

cmdop://skills/install/ssl-cert-checker

Via pip (standalone)

Skills are also regular pip packages:

pip install ssl-cert-checker

This installs the package but does not register it with the CMDOP agent. Use cmdop-skill install . after a pip install to register.

Uninstalling skills

Via CLI

cmdop skills uninstall ssl-cert-checker

Removes both the skill directory and its environment from the platform data directory (<data-dir>/skills/ssl-cert-checker/ and <data-dir>/skill-envs/ssl-cert-checker/ — see Skill directories).

Via desktop app

In Settings → Skills, click the delete button on any marketplace-installed skill.

Listing skills

Your published skills

cmdop-skill list

Shows a table with name, status, installs, and stars for all your published skills.

Installed skills

The agent automatically loads all skills from three sources, in priority order:

A workspace skill overrides a global skill of the same name, which overrides a builtin.

Skill directories

The global skills directory and the per-skill environments both live under the agent’s platform data directory, which follows OS conventions:

Run cmdop skills dir to print the resolved global skills directory on your machine.

Dependency management

Each skill gets an isolated environment under the skill-envs/ directory (see Skill directories):

Python skills: A virtual environment at <data-dir>/skill-envs/<name>/.venv/. Dependencies from requirements.txt are installed using uv pip install (if available) or regular pip. The installer detects changes via content hash — dependencies are only reinstalled when requirements.txt changes.

Node skills: node_modules at <data-dir>/skill-envs/<name>/. Uses pnpm (if available) or npm.

Dependency failure is non-fatal

If dependency installation fails, the skill files are kept. You can retry later:

cmdop skills install my-skill

meta.json

Each marketplace-installed skill has a meta.json:

{
  "installed_from": "marketplace",
  "installed_version": "1.2.0",
  "installed_at": "2026-03-05T10:30:00Z",
  "updated_at": null
}

This tracks install origin and version for update detection.

Version pinning

Skills installed from the marketplace use flexible version constraints:

• Python (pip): >=1.2.0 — allows compatible updates
• Node (npm): ^1.2.0 — allows minor and patch updates