---
id: gh-vgpu
name: "vgpu"
url: https://skills.yangsir.net/skill/gh-vgpu
author: vercel-labs
domain: ai-dev-tools-workflow
tags: ["vgpu", "documentation", "cli", "versioning", "migration"]
install_count: 1600
rating: 4.30 (120 reviews)
github: https://github.com/vercel-labs/vgpu/tree/main/skills/vgpu
---

# vgpu

> 该 Skill 让 Agent 通过项目本地安装的 vgpu CLI 查询与锁定版本一致的捆绑文档，而不是凭记忆、仓库默认分支或托管站点推断 API。适用于依赖升级、迁移指南查阅以及避免版本错配写出幻觉接口的场景，确保改代码前先读到正确的指南与 API 页面。

**Stats**: 1,600 installs · 4.3/5 (120 reviews)

## Before / After 对比

### 版本对齐的文档查询

**Before**:

开发者确认某个 API 用法时，只能翻记忆、仓库默认分支或在线文档站点，拿到的往往是 latest 版本，与项目锁定版本不一致，改完代码才发现接口对不上，反复返工。

**After**:

此技能先确认本地 vgpu CLI 的解析版本，再用 docs ls / find / cat 只加载该版本捆绑的指南与 API 页面，并按顺序阅读迁移文档，让每次改动都建立在正确的接口定义上。

| Metric | Before | After | Change |
|---|---|---|---|
| 定位正确 API 文档耗时 | 25分钟 | 3分钟 | -88% |
| 版本错配返工次数 | 3次 | 0次 | -100% |

## Readme

# vgpu

Treat the documentation bundled with the target project's installed `vgpu` package as the
authority for that project. This skill is intentionally version-neutral: do not infer API shapes
from the skill's Git revision, remembered APIs, the repository default branch, hosted docs, or a
hosted MCP server when local package docs are available.

The public skill install command has no branch pin:

```sh
npx skills add vercel-labs/vgpu
```

## Select the package version

Run the project-local `vgpu` executable from the workspace that owns the dependency. First check
the relevant package manifest and lockfile, then confirm which local CLI you resolved without
allowing the package manager to download a missing command:

```sh
pnpm exec vgpu --version
npm exec --no -- vgpu --version
```

Use a local-only equivalent for other package managers, such as `yarn exec vgpu --version` or an
already resolved `node_modules/.bin/vgpu`. Commands such as bare `npx vgpu` or `bunx vgpu`
may download a missing package, so do not use them for local version discovery. npm's `--offline`
is also insufficient because it can install a missing package from cache. Do not replace an
installed version merely to read newer documentation.

If a package manifest or lockfile selects `vgpu` but the local binary is unavailable, treat the
dependency tree as incomplete rather than unversioned. Restore the project's locked dependencies
when installation is within scope. For read-only access, the exact selected version can be invoked
explicitly instead:

```sh
npx -y vgpu@<selected-version> docs cat getting-started.md
```

Do not substitute `@latest` for a selected stable, RC, or other prerelease. Only when neither the
project nor the user has selected a vgpu version, default to the explicit stable tag:

```sh
npx -y vgpu@latest docs cat getting-started.md
```

When adding a previously unselected dependency is part of the requested work, install
`vgpu@latest` with the project's package manager. Use `vgpu@next`, an RC, or any other
prerelease only when the user or the existing project explicitly selected that prerelease;
preserve an exact requested version.

## Route through the bundled docs

Ask the resolved local CLI what documentation its version supports, then load only the pages
needed for the task:

```sh
pnpm exec vgpu docs --help
pnpm exec vgpu docs ls
pnpm exec vgpu docs cat getting-started.md
pnpm exec vgpu docs find "<topic, symbol, or error code>"
pnpm exec vgpu docs grep -i "<term>"
pnpm exec vgpu docs cat "<path or symbol>"
```

Adapt `pnpm exec` to a no-install command for the project's package manager, but keep using its
local binary; with npm, retain `npm exec --no -- vgpu` for every docs command. Start with getting
started for unfamiliar projects, use `find` for task or symbol discovery, use `grep` for details
mentioned inside pages, and `cat` every relevant guide and API page before changing code. Let
`docs --help` from that installed version define the available commands.

When upgrading a project, record its previous version before changing dependencies. After selecting
the authorized target version, run `docs ls /migrations` through that version's local CLI and read
the intervening version guides in order. Each guide identifies affected usage and verification steps;
skip changes already applied, including when moving between RCs of the same release. Older packages
may not bundle migration guides: report that absence and consult the exact release's notes instead
of silently substituting the current hosted docs.

For MCP-based lookup, start `vgpu mcp` through the same project-local executable so it serves the
same bundled corpus. A hosted MCP server is a convenience for current stable documentation, not
the authority for a project pinned to another version.

If the installed docs do not contain a proposed API or workflow, do not invent it or silently
switch versions. Report the mismatch and change versions only when the user's task authorizes it.


---
*Source: https://skills.yangsir.net/skill/gh-vgpu*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-vgpu/markdown*