Marketplace and installed state
The Cmdop marketplace is where you find Skills; your machine is where they live. A catalogue entry is never evidence that a Skill is installed, trusted, or usable. Install by marketplace slug, uninstall by the installed name, and treat “found in another app’s configuration” as discovery rather than adoption.
The marketplace is where you find Skills. Your machine is where they live. Confusing the two is the most common Skills mistake, so Cmdop keeps them visibly separate.
Find and install
In the web console, Marketplace → Discover searches the public catalogue. Marketplace → Installed shows what this machine actually has.
From the command line:
cmdop skill install <slug>
cmdop skill list
cmdop skill show <name>
cmdop skill uninstall <name>install takes the marketplace slug; uninstall takes the installed
name. cmdop skill dir prints where installed Skills live on the machine.
What Cmdop found in your other apps
Cmdop can passively read Skill metadata from other apps you already have installed, so you can see what is on the machine without hunting for configuration files. This is discovery, not adoption:
- It reads bounded metadata only. It never executes the Skill body, its scripts, or its assets to find out what it is.
- A found Skill still belongs to the app that owns it. Cmdop does not edit another app’s files, and it does not take over its Skill.
- Nothing found becomes usable until you import it explicitly.
Which apps Cmdop may inspect is your choice. The Sources control on the Marketplace → Installed page decides it. You can add custom folders there too — note that custom folders on that shared page apply to Skills only, not to MCP servers.
Four states, one of which means “usable”
| State | Meaning |
|---|---|
| Discover | A catalogue entry. Nothing is on your machine. |
| Found | Read from another app’s configuration. Not owned, not executed, not usable. |
| Installed | Cmdop owns a local record of it on this machine. |
| Available at runtime | The runtime can actually use it. |
A catalogue result is never evidence that a Skill is installed, trusted, or available. Installed state belongs to the machine and does not travel with a listing.
Instruction Skills reach the last state on install. Executable ones wait on an isolation runtime — see Runtime status.
Related
Common questions
Where do I find Cmdop Skills?
Use Marketplace → Discover in the web console to search the public catalogue. Use Marketplace → Installed to see what the current machine actually has.
What is the difference between discovered and installed?
Discovered means a catalogue entry or metadata was found. Installed means Cmdop owns a local record of the Skill on this machine. Only installed and runtime- available Skills can be used by the agent.
Does Cmdop execute Skills it finds in other apps?
No. Passive discovery reads bounded metadata only. Cmdop does not execute the Skill body, scripts, or assets, and it does not take over another app’s files.
Cmdop