PromptDock CLI
One command puts a reviewed, versioned skill folder into your coding agent. Every file is checksum-verified before anything is written, and installs are all-or-nothing.
Install a skill
npx promptdock@latest install someone/their-skillNeeds Node 18 or newer and a Prompt Dock account. The first run signs you in through the browser — if you are creating the account then, have your inbox open, because it confirms by email before the terminal continues.
Latest published version: 1.2.0.
Commands
| Command | What it does |
|---|---|
| install <handle>/<slug> | Install a skill into an agent. Picks the tool and scope interactively, or takes --target and --dir. |
| update | Update installed skills. One package failing does not stop the rest. |
| uninstall <handle>/<slug> | Remove a skill. Only files the install receipt owns are deleted. |
| list | What is installed, where, and at which version. |
| login | Authenticate. Opens a browser and pairs with a code. |
| logout | Revoke this machine's token server-side, then clear it locally. |
| whoami | Which account this machine is signed in as. |
Run promptdock <command> --help for the flags on any one of them.
Exit codes
Stable across releases — scripts and CI can depend on them. They are never renumbered.
| Code | Name | Meaning |
|---|---|---|
| 0 | OK | Success. |
| 1 | USAGE | Bad flags or arguments, or a non-interactive run missing --target/--dir/-y. |
| 2 | AUTH | Not logged in, or the stored token was rejected. |
| 3 | DENIED | The server refused: tier, daily cap, rate limit, version floor, or not found — and a package this CLI is too old to install. |
| 4 | INTEGRITY | The server sent something impossible: a checksum mismatch, an unsafe path, or a manifest beyond this CLI's safety fuses. Nothing was written. |
| 5 | IO | Filesystem: permissions, disk space, or a directory that already exists. |
| 6 | NETWORK | Could not reach the API. |
| 130 | INTERRUPT | Ctrl-C during an interactive picker (128 + SIGINT, the shell convention). |
Upgrading
There are two separate version gates and they differ in blast radius. A package can need a newer CLI than yours — only that package is refused, and everything else keeps working. Separately, the API enforces a minimum CLI version for wire-breaking changes; below it, every command fails, including login.
The same upgrade fixes both. Using npx promptdock@latest means you are never below either gate.
Installs are latest-only. There is no version pinning for a skill — a new approved version can land between two runs of the same pipeline. The per-file checksums verify what the server sent; they do not make a CI run reproducible.
When something goes wrong
Every named error the CLI prints carries a link to the error reference, with what happened, why, and what to do about it. Publishing your own skill is covered in the publishing guide.