vlt-cli
/vlt-cli
Mapa narzędzia vlt CLI dla agentów: instalacja, dodawanie i aktualizacja zależności, skrypty, rejestry, pliki vlt.json i zapytania DSS.
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 13
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
BSD-2-Clause, otwarta.
Co robi i kiedy
Mapa narzędzia vlt CLI dla agentów: instalacja, dodawanie i aktualizacja zależności, skrypty, rejestry, pliki vlt.json i zapytania DSS.
Wyzwalacze z opisu
Oryginalny opis (EN)
Map of the vlt CLI for coding agents. Covers how to install, add, remove and update dependencies, run scripts and package bins, configure registries (installs work with no config through vlt's public npm mirror, publishing needs a configured registry), work with vlt.json and vlt-lock.json, and pass Dependency Selector Syntax (DSS) queries to commands. Use when the user wants to use vlt in a project, add or update a dependency with vlt, fix "Missing registry configuration" (ECONFIG), set up registries or tokens for vlt, work with vlt workspaces, ship an agent skill from a package, install vlt's
Jak działa
- Help ladder
- Install management
- Project files
- Registry setup
- vlt's agent skills
- DSS queries
Podgląd SKILL.md
--- name: vlt-cli description: Map of the vlt CLI for coding agents. Covers how to install, add, remove and update dependencies, run scripts and package bins, configure registries (installs work with no config through vlt's public npm mirror, publishing needs a configured registry), work with vlt.json and vlt-lock.json, and pass Dependency Selector Syntax (DSS) queries to commands. Use when the user wants to use vlt in a project, add or update a dependency with vlt, fix "Missing registry configuration" (ECONFIG), set up registries or tokens for vlt, work with vlt workspaces, ship an agent skill from a package, install vlt's agent skills in a project, or asks which vlt command or flag does something or what `vlr` and `vlx` are. --- # Using the vlt CLI A map of the CLI, one line per command. For anything deeper, defer to `vlt help <cmd>` and the docs instead of guessing options. ## Help ladder - `vlt -h` lists the common commands; `vlt -a` every command and bin plus the common flags; `vlt help <cmd>` (or `vlt <cmd> -h`) one command's usage, options and examples. - Every docs page is Markdown at its URL plus `.md`; the index is <https://docs.vlt.io/llms.txt>. Commands: <https://docs.vlt.io/client/commands.md>. Config keys: <https://docs.vlt.io/client/configuring.md>. - When stdout is not a TTY and `CI` is unset, the default `--view` is `json`, so in a sandbox `vlt help <cmd>` prints a JSON-encoded string: add `--view=human` (`vlt <cmd> -h` is unaffected). `--view=json` works on every command. - Confirm with the user before publishing, unpublishing, deprecating, changing access, or creating or revoking tokens. ## Install management - `vlt install [pkgs]` (`i`, `add`): install everything, or add packages to package.json and vlt-lock.json. `-D`/`--save-dev`, `-E`/`--save-exact`, `-w <path>` adds to that workspace, `--frozen-lockfile` fails if the lockfile is out of date. - `vlt uninstall <pkgs>` (`rm`): remove dependencies, update both files. - `vlt update` (`u`): raise dependencies to the latest in-range versions by resolving from scratch; `-w <path>` limits it. - `vlt ci`: delete node_modules and install exactly from vlt-lock.json. - `vlt build [query]` (`b`): run lifecycle scripts and link bins for installed packages. `install`, `ci`, `update` and `uninstall` run no dependency scripts unless `--allow-scripts=<query>` allows them. - `vlt outdated [pkgs]`: dependencies with newer versions, and the command that upgrades each. - `vlt pkg get|set|delete <key>` (`p`): read and edit package.json. - `vlt run <script>` (`r`, bin `vlr`) runs package.json scripts; `vlt exec <bin>` (`x`, bin `vlx`) runs a package bin, installing it when needed. - `vlt skills list|link [query]`: show or link the agent skills shipped by installed packages; `--allow-skills=<query>` on install links them automatically. `vlt skills init [<name>]` scaffolds a skill for the project to ship: `skills/<name>/SKILL.md`, or a root `SKILL.md` named after the package, added to package.json `files` when needed. It never overwrites and needs no registry. - Everything else (`init`, `create`, publishing, account and token commands, `cache`, `bugs|docs|repo` openers): `vlt -a`. ## Project files - `package.json`: dependencies and scripts, as with npm. - `vlt.json` at the project root (commit it): `workspaces` and a `config` object (registries, allow-scripts, allow-skills, ...). Workspaces found in package.json or pnpm-workspace.yaml are saved here on install. A user-level vlt.json (`vlt config location --config=user`) applies to every project; the project file layers on top. - `vlt-lock.json`: the lockfile; commit it. `vlt ci` and `--frozen-lockfile` install exactly what it records. - `node_modules` is laid out by vlt: `vlt query` and `vlt ls` need a project installed by vlt (run `vlt install` first in a project installed by another client). Docs: <https://docs.vlt.io/client/configuring.md>, <https://docs.vlt.io/client/workspaces.md>. ## Registry setup With no config, installs and other reads work out of the box: the built-in `npm` alias is vlt's public npm mirror (`https://registry.vlt.io/upstream/npm/`), read-only and with usage limits, so bare specs fetch from `registry.vlt.io`. Publish and account commands (`publish`, `login`, `whoami`, `token`, ...) never use it and fail with `Missing registry configuration` (`ECONFIG`) until a registry is configured. - `vlt setup [<account>]`: vlt.io accounts, recommended (account npm mirror with no usage limits, private packages, tokens). Authenticates and writes the account's `npm` (mirror) and `main` (private) aliases to the user vlt.json (`--config=project`: the project one, then it offers vlt's agent skills, see below). - `vlt config set registries.npm=https://registry.npmjs.org/`: plain npm instead of the public mirror, no login. Writes the project vlt.json; add `--config=user` for every project. Any `registries.<alias>=<url>` works the same, and `<alias>:pkg@range` specs fetch from that alias; `scoped-registries` maps an `@scope` to a URL instead. - `vlt login --registry=<url>`: authenticate against a registry and save it as the `registry` scalar (project vlt.json, or `--config=user`). Publish, auth and account commands then use it, and so do bare-spec installs (`npm:` alias specs keep using `registries.npm`). Without a login, publish with `publishConfig.registry` in package.json, `--registry`, or `vlt setup`. - One run only: `vlt install --registries npm=<url>`; add `--save-config` (`install`, `update`) to persist it to vlt.json. - Env and CI: every option is `VLT_<OPTION>`, lists newline-delimited (`VLT_REGISTRIES='npm=https://registry.npmjs.org/'`); tokens via `VLT_TOKEN` (the default registry) or per registry URL, trailing `/` dropped and non-alphanumerics replaced by `_` (`VLT_TOKEN_https_registry_npmjs_org`). `.npmrc` is not read. Never commit or print a token. - Docs: <https://docs.vlt.io/client/registries.md>, <https://docs.vlt.io/client/auth.md>. Moving a repo and its CI onto vlt.io: the `vlt-registry-migration` skill. ## vlt's agent skills `@vltpkg/skills` packages this skill, `dss-query` and `vlt-registry-migration`. To give a project's agents these skills: - `vlt setup --skills`: the command to run in an existing project. No prompt (safe for agents), no account, registry or token changes, only acts on the current project. It needs a root `package.json` (else run `vlt init`) and a configured `registries.npm`, like any install. Running it again changes nothing. - It changes: `@vltpkg/skills` in the root `devDependencies` (a root dependency keeps its type and spec); `allow-skills` in the project vlt.json, a `#@vltpkg/skills` selector added to the stored query (nothing stored: `:not(:malware), #@vltpkg/skills`, which links the skills of every non-malware package on each install and needs Socket data, fail closed); links in the agent skill dirs (`.agents/skills`, `.claude/skills`, ..., or `skills-dir`) with their `.gitignore` blocks. Commit package.json, vlt-lock.json and vlt.json: `vlt ci` in a fresh clone links them again. - `vlt setup <account> --config=project` asks `Do you want to install vlt skills? (Y/n)` at its end, in a project with a `package.json` (interactive, and it rewrites the registries: not for agents). `--yes` accepts; without a terminal and without `--yes` it is skipped. A failed install there is only a warning. - Plain `vlt setup` (user config) never offers them; in a project without them, it ends with a hint to run `vlt setup --skills`. `--config=user` is not supported by `--skills` yet. - Narrower by hand: `vlt install -D @vltpkg/skills --allow-skills="#@vltpkg/skills"` saves only `#@vltpkg/skills`, and keeps an already stored `allow-skills`, so the next clone may not link them. Docs: <https://docs.vlt.io/client/commands/setup.md>. ## DSS queries Dependency Selector Syntax is CSS selectors over the dependency graph. Single-quote selectors in the shell. | Selector | Matches | | ------------------------------------ | ----------------------------------- | | `:root` `:workspace` `:project` | project root / a workspace / both | | `#name` `[name^="@scope"]` | by name / by package.json field | | `:root > *` / `:root *` / `a, b` | direct deps / transitive / OR | | `:dev` `:prod` `:optional` `:peer` | dependency type | | `:not(...)` `:has(> #x)` | negate / packages that depend on x | | `:outdated(major)` `:semver(^1.0.0)` | version checks | | `:skills` | packages that ship agent skills | | `:malware` `:cve` `:vuln(high)` | Socket security data (network call) | Where queries go: - `--target=<query>` (which packages): `vlt query`, `vlt ls`, `vlt build`, `vlt outdated`, `vlt skills`, `vlt bugs|docs|repo`. Only `vlt query`, `vlt build` and `vlt skills list|link` also take the query positionally; `ls` and `outdated` positionals are package names, `bugs|docs|repo` take a spec. - `--scope=<query>` (what counts as top level, or which workspaces run): `vlt query`, `vlt ls`, `vlt run`, `vlt exec`, `vlt run-exec`, `vlt pkg`, `vlt version`, `vlt pack`, `vlt publish`. `-w <path|glob>` picks workspaces by path instead. - `--allow-scripts=<query>`, `--allow-skills=<query>`: `vlt install`, `vlt update`, `vlt uninstall`, `vlt ci`. - `vlt query '<selector>' --expect-results='>=1'` exits non-zero when the count does not match: a CI gate. `--view=count|json|mermaid`. - Deeper: the `dss-query` skill (`vlx skills add vltpkg/vltpkg -- --skill dss-query`), <https://docs.vlt.io/client/selectors.md> and <https://docs.vlt.io/client/security.md>.
Wersje
W bazie nie ma innych skilli o nazwie vlt-cli.
Migawka bazy z 13.11.2026 · wersja paczki 59848cc51142 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100vlt-registry-migration
Przenosi repozytorium JavaScript na rejestr vlt.io, konfiguruje tokeny, lockfile i uwierzytelnianie w npm, pnpm, yarn i bun. - 100dss-query
Wyjaśnia i składa zapytania vlt Dependency Selector Syntax (DSS), czyli selektory podobne do CSS do filtrowania pakietów w grafie zależności, także z audytem bezpieczeństwa przez Socket. - 100npm
Pomaga zarządzać zależnościami JavaScript i Node.js: package.json, pliki lock, workspaces w monorepo, skrypty, audyty bezpieczeństwa i publikowanie pakietów. - 95package-management
Pomaga wybierać i konfigurować menedżery pakietów JavaScript i TypeScript npm, yarn, pnpm i bun, zarządzać zależnościami, workspace'ami monorepo, plikami lock oraz publikować pakiety. - 100bun-package-manager
Obsługuje polecenia menedżera pakietów Bun (install, add, remove, update), przestrzenie robocze, lockfile'e i migrację z npm, yarn i pnpm. - 100python-dependency-management
Dodaje, aktualizuje i usuwa zależności Python w projektach uv, w tym grupy zależności i extras.