@enteros/skill-cli — enterskill

The official EnterOS Skill Framework CLI, published as an npm bin so a skill repo can scaffold, hard-gate, build, verify, and manage its .enterskill composition tree without an SDK checkout on disk:

npx enterskill --help
npx enterskill init my-skill          # scaffold the ability AT THE REPO ROOT (the repo IS the ability)
npx enterskill init my-skill --dir skills   # …or the <dir>/<id>/ multi-skill-monorepo layout
npx enterskill check .
npx enterskill verify .
npx enterskill tree .

init carries no org defaults: the npm scope is --scope → the scope of the repo's own root package.json name → (on a TTY) a prompt → else it exits 2 (unscoped repo: pass --scope). At the repo root, package.json is merged (name set to <scope>/skill-<id>, module fields added; existing devDependencies/scripts preserved) and pre-existing anatomy files are never clobbered. npm children compose from ANY scope by default (open framework); --scopes on check/verify is OPT-IN restriction — pass it only to lock a deployment down to specific scopes.

Stdlib-only, zero runtime dependencies. The package carries its own copy of the normative contracts/skill-framework/*.schema.json family, so one published version governs the contracts AND the checker — every pattern/const/enum the CLI enforces is read from those bundled schemas at runtime, never restated.

init --with-ci

When run from this published package, enterskill init --with-ci scaffolds a registry-neutral CI workflow that installs @enteros/skill-cli at this version and runs enterskill check — no vendored contracts, no SDK git pin (the CLI is authoritative). When run from an SDK checkout it keeps the legacy pinned-clone wiring (vendored contracts-upstream/ + sdk-hardgate.mjs).

gen

enterskill gen composes config/config.schema.json, config/ENV.md, config/WORK.md, and the SKILL.md routing block. It shells out to the target repo's Node and resolves @enteros/skill-core from the target repo's node_modules (install it there first: npm i @enteros/skill-core).

Build

tools/ and contracts/ are build artifacts materialized from the SDK's repo-root source of truth by scripts/bundle.mjs (run automatically on prepack). They are gitignored; the tarball always ships fresh copies.