Skip to main content

Skills Commands

pan skills lists skills and sets per-level on/off overrides for native skills and skill packs. See Skills for the on/off levels and Skill Packs for what a pack is, the pack catalog, and the trust model.

pan skills list

Lists skills with their effective on/off state and the level that decided it, then skill packs and their skills. This is the default command: pan skills alone runs it.
Exits 1 for an unknown --project, or for an --issue that no registered project owns. An issue file whose YAML does not parse is read as empty, and no error is shown.

pan skills set

Sets a native skill, a pack skill (<pack>/<skill>), a whole pack, or every pack of a pack group to on, off, or inherit, at the global, project, or issue level.
Takes exactly one positional (the state) with --pack or --group, two (the skill and the state) without them. Exits 1 on the wrong positional count, a state that is not on, off, or inherit, passing --pack and --group together, or passing --project and --issue together. It also exits 1 on any of these store errors, each with its own message:
  • core skill cannot be overridden: <skill>
  • unknown skill: <id>
  • unknown pack: <id>
  • pack <id> is not cached; run pan skills pack sync <id>
  • unknown project: <key>
  • no registered project owns issue <ISSUE>
  • cannot parse <path>: … (the global config.yaml)
  • could not commit <path>: …
With --group, it also exits 1 with unknown pack group: <name> (known: …), or with pack <id> is not added; run pan skills pack add --group <name> for each member that is not added; nothing is set then. With --issue, set writes <planHome>/.pan/skill-overrides/<ISSUE>.yaml, committed in the plan home on its checked-out branch (normally main) and pushed to that branch’s upstream, and prints (committed <sha>, pushed) or (committed <sha>, push pending: <reason>).

pan skills add

Adds pack skills to a conversation that is already running, and loads them. In the dashboard, the same action is Add skills… in the conversation menus. A Claude Code conversation loads them in place with /reload-plugins and keeps its context; Codex, native skills and launch-wired packs (deft, sageox, gstack-runtime packs, packs with MCP servers) need a restart. <conversation> is a conversation name, or self for the conversation the command runs in.
Prints one sentence for the outcome (hot, sent, queued, needs-restart, restarted or next-launch; see Adding skills to a running conversation), then each warning on its own line. Only Claude Code and Codex conversations take skill packs; for any other harness the dashboard refuses with Skill packs apply only to Claude Code and Codex conversations. It exits 1 when the dashboard is not reachable, when the dashboard refuses the request (the message is printed), for self outside a conversation, and for self --restart, which a conversation cannot do to itself.

pan skills pack add

Registers a git skill pack at the commit a ref resolves to and trusts it; enables nothing. Known packs (mattpocock, pstack, gstack, deft, sageox, atlassian, remotion, hyperframes, openmontage, video-use) default the url and, for every one except mattpocock, gstack and deft, the ref. For sageox, the preview also lists the go build commands, the paths they write and the downloads, and trusting the commit builds ox and its two adapters before the pack is registered. When a claude-plugin pack declares applied MCP servers (see Pack MCP servers), the preview adds an MCP servers row, <name> (<url>) for each one, and trusting the commit records your consent to them.
Exits 1 on an unknown --adapter value, a pack with no default url or ref when none is given, a pack source error, or when the commit was not trusted (declined, or not written without a terminal and --yes). For sageox, a missing Go (pack sageox needs go on PATH (https://go.dev/dl/)) or a failed build is a pack source error. With --browser, the pack is registered as soon as the commit is trusted; a declined or failed browser-runtime step then exits 1 with the pack already registered. Finish it with pan skills pack browser <id> rather than retrying pack add. With --group, a member that is already added prints <id>: already added and is skipped; any declined or failed member exits 1 after the rest are tried. --group takes no id, url, --ref, --adapter or --browser.

pan skills pack update

Moves a pack to the commit its ref (or --ref) now resolves to, after showing the preview again. For gstack, a moved commit is also rendered (pack-mode setup) after you confirm; with browser consent recorded, the browser runtime is built for the new commit too, and the commit moves only when both succeed. For sageox, a moved commit is built after you confirm.
Exits 1 on a pack source error, or when the new commit was not trusted.

pan skills pack list

Lists registered skill packs with their source, cache state, license, skill count, what is not applied, and update available: <commit> when the ref has moved. Text output then lists the known packs you have not added, each with the command that adds it, and the pack groups with any members not added; --json prints only the registered packs.

pan skills pack remove

Unregisters a pack, clears its global toggles, and deletes its cache, every mount that contains it, and dangling launch links, and Codex plugin caches. For sageox, it keeps the stored SageOx links and prints kept SageOx link files in <packdir>/bindings/ (delete them by hand to forget every project's SageOx link).
Exits 1 if the pack is not registered, or if removing a mount or cache failed (rerun to retry). The unregister step runs before the cache and mount sweep, so a retry after a failed sweep still exits 1 with “pack is not registered” even when that retry’s sweep itself succeeds; that exit does not by itself mean the cleanup failed.

pan skills pack sync

Re-fetches a pack and extracts its trusted commit, or every registered pack when id is omitted; it never moves the commit. For gstack, it also re-renders the trusted commit and builds a missing browser runtime without asking when consent is recorded. For sageox, it also builds ox for the trusted commit when that build is missing, without asking (the commit is already trusted).
Exits 1 if any pack fails to sync.

pan skills pack gc

Removes unused skill pack mounts, dangling launch links, stale renders, and orphaned pack state for packs that are no longer registered.
Exits 1 if --max-age-days is not a number of days of 0 or more, or if the global config cannot be read or parsed (gc then removes nothing).

pan skills pack browser

Turns a runtime pack’s browser runtime on or off (gstack only). state defaults to on.
Exits 1 if state is not on or off, on a pack source error, or when the browser runtime was not trusted.

pan skills pack sageox status

Shows, per project, whether the sageox pack is on, whether uploads are enabled, and the SageOx link state in the LINK column: committed (the project committed .sageox/, or has sageox_binding: committed), held (a link is stored for it), or none. --json adds a "link" field with the same values.
Exits 1 if --project names a project Overdeck does not know.

pan skills pack sageox upload

Turns SageOx uploads on or off for a project. Uploads are off by default.
Exits 1 if state is not on or off, or on a SageOx config error.
Creates the project’s SageOx link without changing any of its checkouts. It checks that the SageOx login file exists (it never reads it), fetches the default branch, and runs the Overdeck-built ox init in a throwaway detached worktree of origin/<default> under ~/.overdeck/packs/sageox/tmp/, in host-managed mode with the network on. The untracked files ox init writes under .sageox/ are stored in ~/.overdeck/packs/sageox/bindings/<key>/. It then waits up to 120 seconds for ox to clone the project’s ledger, and removes the throwaway worktree.
Run <built ox> login once before the first link. When the default branch already tracks .sageox/, link changes nothing and says that the committed link is used. When a link is already stored, it prints already linked: <dir>. When the ledger is not cloned within 120 seconds, it prints the SageOx ledger is not cloned yet; ox clones it in the background. Check with: <bin> status and still exits 0. Exits 1 on an unknown project, when the sageox pack is not registered (pan skills pack add sageox), when ox is not built (pan skills pack sync sageox), when the login file is missing (SageOx login not found. Run: <bin> login), when the fetch fails, when ox init fails (the last 20 lines of its output are printed), or when ox init writes outside .sageox/ even in the fresh-clone fallback.

pan skills pack sageox commit

Opens one PR that adds the project’s stored SageOx link files as .sageox/, then records sageox_binding: committed for the project in ~/.overdeck/projects.yaml. The commit is made in a throwaway worktree on the branch overdeck/sageox-link from origin/<default>; no project checkout changes. Re-running it reuses the branch and an open PR. The flag is written only after the PR exists, so a failed run records nothing.
Prints opened <url> or reused <url>, then recorded sageox_binding: committed for <key>. When the default branch already tracks .sageox/config.json, it records the flag and prints already committed on <default>. The commit runs the project’s git hooks in the throwaway worktree, so a project whose hooks need node_modules (husky, for example) fails there; --no-verify is not used. The local overdeck/sageox-link branch stays in the repository. Exits 1 on an unknown project, when the project has no stored link (run pan skills pack sageox link --project <key>), when the fetch, worktree, commit or push fails, or when the forge returns no PR URL.

pan skills deft status

Shows Directive detection, the deft pack, the skill map, managed mode, and the ownership report for a project (the current repository when --project is omitted).
Exits 1 if --project names a project Overdeck does not know.

pan skills deft enable

Prints the ownership plan for a Directive project and, once accepted, stores the decision to enable managed mode.
Exits 1 if --project names an unknown project, the project is not a Directive project, or the plan was not accepted.

pan skills deft disable

Removes the managed-mode decision for a project. Project files are untouched.
Exits 1 if --project names a project Overdeck does not know.

pan skills deft use

Run an issue on Deft Directive’s pipeline: install Directive into its workspace, hidden from git. See Running an issue on Deft.

pan skills deft back

Switch an issue back to Overdeck’s pipeline: save the Deft state, then remove the install. See Running an issue on Deft.

pan skills deft save

Commit the issue’s Deft state archive under .pan/deft/<ISSUE>/. See Running an issue on Deft.

pan skills deft show

Show an issue’s pipeline, Deft install, drift, and merge-guard verdict. See Running an issue on Deft.