Skip to content

CLI Maintainer Commands

Mel edited this page Nov 10, 2026 · 1 revision

These are for people working on the stack itself. Projects do not need them.

Command What it does Notes
stack serve [--port <n>] read-only web browser for the stack on 127.0.0.1 (default port 4321; 0 picks a free port) prints escacs stack: http://127.0.0.1:<port>/; refreshes remote caches in the background and has a sync button. npm run web runs it
stack catalog regenerate catalog.json and llms.txt from the manifests writes those two files. Offline and deterministic; remote members are never indexed. Exits 1 and writes nothing when a manifest is invalid
stack check validate manifests and library.json files, and fail if the generated index is stale prints ok: N entries on success; catalog.json is stale; run npm run catalog otherwise. Never touches the network. npm run check also runs the test suite
stack link-skills <names...> symlink skills into ~/.claude/skills and ~/.codex/skills meant for the always-on helpers escacs-stack and create-agents-md; the command accepts any skill name. An existing entry that is not the same link is left alone (skip ... (exists, not touching it))
$ stack check
ok: 93 entries
$ stack link-skills escacs-stack create-agents-md
linked  ~/.claude/skills/escacs-stack
linked  ~/.claude/skills/create-agents-md
linked  ~/.codex/skills/escacs-stack
linked  ~/.codex/skills/create-agents-md

The paths are shown with ~; the command prints the full home path. Setting HOME to another folder before the command redirects both links, which is how to try it without touching a real home directory.

After adding, renaming or editing a manifest or summary: npm run catalog regenerates catalog.json and llms.txt (never edit them by hand; commit them with the change), and npm run check validates and runs the tool tests. CI runs the same command.

See also: CLI Environment and Flags, CLI Remote Libraries, CLI Known Issues.

Clone this wiki locally