mirror of
https://git.openapi.site/https://github.com/desirecore/market.git
synced 2026-06-06 05:30:39 +08:00
xyx
a582f0f4f9
## 背景 / Background #16 (4f7037a) 将 16 个 SKILL.md 的 `~/.desirecore` 路径批量替换为 `${DESIRECORE_ROOT}`，但只升了 `manifest.json`，**未升任何 per-skill version**。 客户端按 SKILL.md frontmatter 的 per-skill `version` 做 semver 同步：version 不变即判定「无更新」而永久跳过，导致已升级用户的全局技能正文停留在替换前的旧内容（与线上不同步）。 #16 (4f7037a) bulk-replaced `~/.desirecore` with `${DESIRECORE_ROOT}` in 16 SKILL.md files but only bumped `manifest.json`, leaving every per-skill `version` untouched. Clients sync by per-skill semver, so an unchanged version is treated as "no update" and skipped forever — upgraded users' global skills stay frozen on pre-replacement content. ## 改动 / Changes - 对 #16 触及且至今仍未升号的 **14 个在册技能** 各 patch +1 - `manifest.json` 1.2.2 → 1.2.3（沿用 #16「内容改动同步升 manifest」的约定） - 退役技能 `minimax-image-gen` / `minimax-tts`（不在 builtin-skills.json，不下发）跳过 - diff 为纯 version 行，未触动正文 Bumps the 14 in-manifest skills changed by #16 that were never version-bumped; manifest 1.2.2 → 1.2.3; retired skills skipped. Version-line-only diff.
9.5 KiB
9.5 KiB
name, description, version, type, risk_level, status, disable-model-invocation, tags, metadata, market
| name | description | version | type | risk_level | status | disable-model-invocation | tags | metadata | market | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| nodejs-runtime | Use this skill when the user needs to install, upgrade, or troubleshoot Node.js, npm, pnpm, yarn, and JavaScript/TypeScript runtime environments. Covers four-tier fallback strategy: (1) DesireCore HTTP API for in-app installation, (2) DesireCore built-in Volta CLI for Node.js + package manager version management, (3) system package managers (brew/apt/dnf/winget/NodeSource), (4) community nvm/fnm as last resort. Also covers global package management, npm registry/proxy configuration, EACCES permission errors, and PATH troubleshooting. Triggers include: "install node", "node not found", "npm not found", "npm EACCES", "pnpm", "yarn", "volta", "nvm", "fnm", "nodejs version", "package-lock", or any Node.js / npm runtime error. 使用场景：用户需要 安装 Node.js、安装 npm、 pnpm、yarn、配置全局包、解决 EACCES、PATH 问题、镜像/代理配置。 | 1.0.2 | procedural | low | enabled | true |
|
|
|
nodejs-runtime Skill
L0: One-line Summary
When to use: the user needs to install Node.js / upgrade Node / switch Node multi-version / install or configure
npm / pnpm / yarn / troubleshoot node: command not found, npm: command not found,
EACCES global install permission errors, node-gyp build failures, registry mirror / proxy issues, or other
Node.js runtime problems, or when other skills (pptx using pptxgenjs, etc.) report "Node.js unavailable".
How: prefer the DesireCore built-in Volta and follow a four-tier fallback (HTTP API → Volta CLI → system package manager brew/apt/NodeSource/winget → community options nvm/fnm).
L1: Overview and Use Cases
Capability Description
Procedural skill. Before each Node.js environment operation, run scripts/probe-node.sh to obtain a JSON snapshot, then choose a path according to the four-tier fallback in ../dev-environment-setup/references/decision-tree.md.
Use Cases
- "node not found" / "npm not found"
- The user requests to install/upgrade Node.js
- Multi-version switching (based on
package.json#voltaor.nvmrc) - Install/manage pnpm / yarn / npm
- "EACCES: permission denied" (npm global install permission error)
- Configure registry / proxy
- Other skills (pptx, etc.) report Node.js unavailable
Core Value
- DesireCore first: Volta + HTTP API as L1/L2, avoiding pollution of the system Node
- JSON-driven decisions: the probe script outputs structured data that Claude can parse directly
- package.json#volta compatible: Volta automatically switches versions per project
L2: Detailed Specification
Step 1: Environment Probe (mandatory)
bash skills/nodejs-runtime/scripts/probe-node.sh > /tmp/node-probe.json
cat /tmp/node-probe.json | jq .
See ../dev-environment-setup/references/probe-snapshot.md for field definitions.
Step 2: Choose an Execution Path
| Condition | Path |
|---|---|
desirecore_api non-empty |
L1 HTTP API |
desirecore_api empty, volta_path non-empty |
L2 Volta CLI |
| Neither of the above | L3 System package manager (brew / apt / NodeSource / winget) |
| L1–L3 all fail or user explicitly requests | L4 Community options (nvm / fnm) |
Step 3: Execute (only the main path is shown; see each reference for details)
L1: HTTP API (→ references/volta-desirecore.md)
PORT=$(cat ${DESIRECORE_ROOT}/agent-service.port)
BASE="https://127.0.0.1:${PORT}/api/runtime"
# 列出可装版本
curl -sk "${BASE}/node/available"
# 触发安装（异步）
curl -sk -X POST "${BASE}/node/install" \
-H "Content-Type: application/json" \
-d '{"version":"22"}'
# 安装包管理器
curl -sk -X POST "${BASE}/pkg/pnpm/install" \
-H "Content-Type: application/json" \
-d '{"version":"latest"}'
# 完成后刷新缓存
curl -sk -X POST "${BASE}/environment/refresh"
L2: Volta CLI Absolute Path (→ references/volta-desirecore.md)
VOLTA=${DESIRECORE_ROOT}/runtime/volta/volta
export VOLTA_HOME=${DESIRECORE_ROOT}/runtime/volta
export VOLTA_FEATURE_PNPM=1
"$VOLTA" install node@22
"$VOLTA" install pnpm@latest
"$VOLTA" install yarn@latest
"$VOLTA" list all
# 项目级固定（修改 package.json#volta）
"$VOLTA" pin node@22 pnpm@9
Windows: %USERPROFILE%\.desirecore\runtime\volta\volta.exe.
L3: System Package Manager
| Platform | Command |
|---|---|
| macOS | brew install node |
| Debian/Ubuntu | NodeSource: curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash - && sudo apt install nodejs |
| Fedora/RHEL | curl -fsSL https://rpm.nodesource.com/setup_22.x | sudo bash - && sudo dnf install nodejs |
| Arch | sudo pacman -S nodejs npm |
| Windows | winget install OpenJS.NodeJS.LTS |
L4: nvm / fnm (→ references/nvm-fallback.md)
Only enable when explicitly requested by the user or when the above fail.
Step 4: Package Manager Strategy
See references/package-managers.md for details:
- pnpm (recommended, disk-efficient, strict dependencies)
- yarn (Berry / Classic)
- npm (default, ships with Node.js)
- Project-level
package.json#voltaautomatic switching
Step 5: Troubleshooting
See references/troubleshooting.md for details:
- npm EACCES permission errors (do not use sudo npm)
- registry / proxy configuration
- node-gyp build failures
- "node: command not found" when nvm is installed
Important Constraints
- Never
sudo npm install -g: use a user-level prefix or Volta/nvm. - Refresh after modifying the environment: for L1, call
POST /api/runtime/environment/refresh; for other paths, re-run the probe. - Cross-skill collaboration: when
pptxand others need Node.js, install via this skill's main path; for npm package quick reference, see../dev-environment-setup/references/office-deps.md. - Respect package.json#volta: when this field is detected, prefer Volta — do not switch to nvm.
References
- Decision tree:
../dev-environment-setup/references/decision-tree.md - DesireCore foundation:
../dev-environment-setup/references/desirecore-runtime.md - Probe protocol:
../dev-environment-setup/references/probe-snapshot.md - Office dependencies (npm packages):
../dev-environment-setup/references/office-deps.md