Skip to content

CLI Quick Tour

Mel edited this page Nov 10, 2026 · 1 revision

Five commands, in the human layout. Pipes never get colour, so the blocks below have none; on a terminal the same output is coloured.

List the entries, one group per kind:

$ stack list --human
skills (33)
  skills/agent-prompt-design               link       experimental  Design token-efficient, prefix-…
  skills/babysit-pr                        link                     Watch a pull request through CI…
  skills/components-build                  link       experimental  Build the base UI component set…
...

160 entries · stack list <kind> · stack show <id>

Search by keyword. At most 10 matches, best first:

$ stack search button --human
components (10)
  components/base/button             copy  experimental  Button that triggers an action, with shadc…
  components/base/facet-button       copy  experimental  Diamond-shaped hero call-to-action button …
...

10 matches for "button" (top 10)

Show one entry: its summary, where it lives, what it needs and its files:

$ stack show skills/file-pr --human
skills/file-pr  skill · stable · link
File a short pull request that leads with the problem rather than an inventory of changes. Use when
asked to file, open or create a PR.
path      /path/to/stack/skills/file-pr
use       `stack import skills/file-pr` installs it in the project's .agents/skills and .claude/ski…
files     3 files, 3.9k  (LICENSE, SKILL.md, stack.json)
needs     skills/leaving-pr-comments
tags      github, pull-request, writing
targets   claude-code, codex

Import, as a dry run. Nothing is written; the plan shows what would land where:

$ stack import skills/file-pr --dry-run --project ./my-app --human
import  skills/file-pr             -> .agents/skills/file-pr
import  skills/leaving-pr-comments -> .agents/skills/leaving-pr-comments (required by skills/file-pr)
ignore  would update .gitignore (managed escacs block)
agents  would update AGENTS.md (managed escacs block)
dry run: nothing written

Status of a project with nothing imported yet:

$ stack status --project ./my-app --human
nothing imported yet. try: stack list, then stack import <id>

Once something is imported, status reports each import. See CLI Importing.

Where it finds the stack

The stack is the checkout that contains the CLI file. The CLI works out its own location and reads skills/, components/, presets/ and so on from there. Nothing else selects the checkout, with one exception: ESCACS_STACK_ROOT changes which checkout the stack remote commands read. There is no ESCACS_STACK variable; the code does not read one.

Imports come from the stack's git history, not from the working files. import and update read the commit HEAD points at, or the one given by --ref. An entry must be committed to the stack before it can be imported.

The project directory

Project commands act on the current directory, or on the directory given by --project <dir>. The directory must exist:

no such directory: /nonexistent/x

--project is accepted by init, import, status, update, remove, sync, gitignore and preset apply.

See also: CLI Discover, CLI Importing, CLI Output Modes.

Clone this wiki locally