SkillAgentSearch skills...

vlx

vlt exec / exec-local / exec-cache commands and @vltpkg/vlx

Install / Use

npx skills add vltpkg/vltpkg

Installs into whichever agent you are using.

About this skill
📐

Cursor Rules

Cursor IDE rules (v2)

Quality Score

65/100

Supported Platforms

Cursor

Our assessment of vlx

vlx scores 65/100 on our quality scale, 3942nd of 4,606 Development & Engineering skills we index.

Its Cursor Rules is 3.0 KB long, split into 7 sections with 2 code examples: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
16/20
Description
8/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so vlx is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

vlx compared with similar skills

All 4 of these similar skills score higher than vlx; compare them before choosing.

SkillScoreStarsUpdatedFormat
vlx (this skill)by vltpkg6503d agoCursor Rules
taste-skillby Leonxlnx100102.7ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10066.0k5d agoCLAUDE.md
claude-howtoby luongnv8910045.2k6d agoCLAUDE.md
algorithmic-artby anthropics100177.9k34d agoSKILL.md

Frequently asked questions

How do I install vlx?
Run npx skills add vltpkg/vltpkg. The install tabs above show the steps for each supported agent.
Which AI agents does vlx work with?
It is written for Cursor, as a Cursor Rules file. Other agents that read the same format can often use it too.
Is vlx safe to use?
It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is vlx still maintained?
The repository was last updated 3 days ago, so vlx is actively maintained.

description: vlt exec / exec-local / exec-cache commands and @vltpkg/vlx globs: src/cli-sdk/src/commands/exec.ts,src/cli-sdk/src/commands/exec-local.ts,src/cli-sdk/src/commands/exec-cache.ts,src/vlx/src/.ts,www/docs/content/client/commands/exec.mdx alwaysApply: false

Exec Commands & vlx

vlt exec (alias: x)

Runs a command from a package, installing into XDG data dir if needed. Never modifies local node_modules.

Resolution order:

  1. If --package=<pkg> set → use that package
  2. If arg0 found in local node_modules/.bin → run it (no install)
  3. Otherwise treat arg0 as package spec → install to exec cache → run default bin

Local dir spec (arg0 or --package: ., ./x, file:x; relative to cwd) → bins shimmed into XDG cache vlt/vlx-local/<key> (keyed by dir, bins, shebangs; never rewritten), run in place, nothing installed. Path-like arg0 skips the .bin lookup.

Default bin inference: single bin entry, or bin matching package name (after / for scoped).

vlt exec eslint src/            # local or install + run
vlt exec --package=typescript@5 tsc   # explicit package
vlt exec                        # no args → interactive shell with local bins in PATH

vlt exec-local (alias: xl)

Runs command with local node_modules/.bin prepended to PATH. No remote installs. No args → spawns interactive shell.

vlt exec-cache (alias: xc)

Manage the exec cache (XDG data dir installations).

| Subcommand | Description | |------------|-------------| | ls | List cached packages (filter by name or key) | | info <key> | Extended info about a cached install | | install <spec>... | Pre-install packages into exec cache | | delete [key...] | Remove cached packages (all if no args) |

@vltpkg/vlx Module (src/vlx/src/)

Entry point re-exports:

  • vlx.resolve(positionals, options, promptFn?) → string | undefined — core resolution logic: find local bin → find local package → install to cache → infer default executable. Returns undefined for interactive shell.
  • vlx.install(spec, options, promptFn?) → VlxInfo — install to XDG exec cache
  • vlx.list() → cached package list
  • vlx.info(key) → VlxInfo for a cached install
  • vlx.delete(keys) — remove from cache

Key Types

type VlxInfo = {
  name: string, version?: string,
  path: string,      // synthetic project dir (cache), projectRoot (local), or shim dir (local dir spec)
  resolved: string,  // registry resolution or file URL for local
  arg0?: string,     // inferred default bin path
  integrity?: Integrity, signatures?: Resolution['signatures']
}

Internal Helpers

  • findExecutable(arg0, projectRoot) — searches node_modules/.bin
  • findPackage(name, projectRoot, packageJson) — checks local install satisfies
  • localDir(spec) — abs path if spec is a local dir
  • vlxLocal(dir, packageJson) — shims a local dir's bins, no install
  • inferDefaultExecutable(manifest) — picks bin from manifest
  • inferName(spec) — package name from spec
  • doPrompt(promptFn, spec, path, resolution) — confirmation before install

Related Skills

View on GitHub
GitHub Stars0
CategoryDevelopment
Updated3d ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low