CLI command reference

promptdock login [--token pdk_…]

Log in via the browser hand-off: the CLI prints a code, opens promptdock.ai,
you approve there, and the terminal continues. --token stores a token minted in
Settings → Account → CLI sessions (the CI path; or set PROMPTDOCK_TOKEN).

promptdock logout

Revokes the session server-side FIRST — the token this machine holds stops
working immediately — then removes the local copy from ~/.promptdock/config.json.

If the revoke cannot reach the server (offline), the local token is still
removed and the CLI says so on stderr: that session stays valid until it
expires, so revoke it at Settings → Account → CLI sessions.

promptdock whoami [--json]

Shows the signed-in handle, role, and token expiry.

promptdock install <handle>/<slug> [-g] [--target <tool>] [--dir <path>] [-y] [--force] [--dry-run] [--json]

Installs a skill. Interactively it asks two things: which TOOL, then whether
to install for THIS PROJECT or for your USER ACCOUNT (each shown as its real
destination path). -g answers the second one up front; --dir answers both.

Non-interactive sessions (CI) must pass --target or --dir plus -y, and
authenticate via PROMPTDOCK_TOKEN. -y skips the prompts ONLY — a non-empty
foreign directory still requires --force, and scope stays project-local
unless -g is passed. --dry-run resolves and prints the plan without
installing (and without spending any premium-unlock slot).

Installing over a copy you changed: files you added are kept. A file you
edited, or a file of yours where the new version ships one, stops the install
(exit 4) and nothing is changed. --force replaces those files and keeps every
other file you added. With no receipt in a non-empty folder (what an uninstall
leaves when you had added files), --force keeps your files that do not collide
with the new version's; another skill's folder is replaced, and the CLI lists
what it removed.

promptdock uninstall <handle>/<slug> | --all [-g] [--target <tool>] [--dir <path>] [--force] [-y] [--allow-partial] [--json]

Removes an installed skill using its .promptdock.json receipt — only files the
receipt lists are ever deleted. Locally-modified files block removal without
--force (copy your changes out first).

Across a batch (--all, or a scope holding several skills) one bad item no
longer aborts the rest: the others are still removed and the command exits
with that item's code at the end. --allow-partial exits 0 instead. Declining
a confirm is not a failure.

promptdock update [<handle>/<slug>] [--all] [--check] [-g] [-y] [--force] [--allow-partial] [--json]

`promptdock upgrade` updates your installed skills; it does not update the promptdock CLI. To update the CLI: npm i -g promptdock@latest (or use npx promptdock@latest).

Updates installed skills to the latest approved version. Bare `update` covers
the project-local scope; -g the global scope; --all both. --check reports
without applying, including local changes that would block. Files you added
are kept; a file you edited, or a file of yours where the new version ships
one, blocks the update without --force (which replaces those files and keeps
every other file you added).

An item that FAILS (unreachable, gated, blocked by local edits) no longer
stops the batch — the rest still update — but the command exits non-zero at
the end so CI cannot go green on an update that did nothing. --allow-partial
exits 0 instead. "Up to date" and a declined confirm are not failures.

promptdock list [--json] [-g] [--all]

Lists installed skills from their receipts: ref, version, target, installed-at.

promptdock help — prints the global command map.