* feat: skills i18n 改造 — schemaVersion 1.1,零向后兼容
把 21 个 skills + 1 个 agent + manifest/categories 全量迁移到 schemaVersion 1.1
的 i18n 结构,配套 CI AI 翻译流水线(GitHub Models)与本地工具链。
## 关键变更
### 数据结构(破坏性,schemaVersion 1.0 → 1.1)
- SKILL.md: 顶层 name 改为 ASCII slug(== 目录名,符合 agentskills.io 规范);
中文显示名/short_desc/description 全部迁入 metadata.i18n.<locale>
- agents/<id>/agent.json: shortDesc/fullDesc/tags/persona.{role,traits} 迁入
i18n.<locale>;changelog[].changes 改为 { <locale>: string[] } 对象
- categories.json: 每个分类的 label/description 迁入 i18n.<locale>,顶层只剩
color/icon
- manifest.json: 加 supportedLocales / defaultLocale;顶层 description 迁入
i18n.<locale>
### Body 文件结构
- 根 SKILL.md = frontmatter + default_locale (en-US) body
- SKILL.<locale>.md = 各 locale 的 markdown body(首行 <!-- locale: xx --> 自校验)
### 工具链(scripts/i18n/)
- glossary.json: zh→en 术语表 + do_not_translate 白名单
- schema/skill-frontmatter.schema.json: i18n frontmatter JSON Schema
- validate-i18n.py: 8 条校验规则(name 合规 / locale 完整性 / hash 一致性等)
- translate.py: GitHub Models / Anthropic 双 backend,sha256 增量翻译
- migrate.py: 一次性迁移脚本(旧格式 → i18n 结构)
### CI(.github/workflows/)
- i18n-validate.yml: PR 触发跑 validate + translate --check
- i18n-translate.yml: PR 触发用 GitHub Models(默认 openai/gpt-5-mini)翻译缺失
locale,自动追加 commit;可切到 ANTHROPIC_API_KEY 走 Claude
### 文档
- docs/I18N.md: 作者贡献指南(schema 说明 / 提交流程 / 常见问题)
- README.md: 加多语言段落
## 验证
- uv run scripts/i18n/validate-i18n.py: OK,49 文件 0 错误
- uv run scripts/i18n/translate.py --check: 0 stale locale
- 21 skills 标题数 zh-CN == en-US 严格对齐(最大 66=66)
- skills-ref 规范校验:全部通过(顶层 name ASCII slug + description 单字段)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(i18n): 修复 PR #1 review 反馈的 6 项问题
- schema: translated_by 正则放宽为 ^(human|ai:[A-Za-z0-9._:/-]+)$,接受
'ai:github:openai/gpt-5-mini' 这类 backend:model 形式(CI 翻译输出格式)
- README + docs/I18N.md: 修正"CI 用 Claude API"误导描述,正确说明默认是
GitHub Models(openai/gpt-5-mini)+ GITHUB_TOKEN,可选切到 Anthropic
- skills/minimax-tts/SKILL.md & SKILL.zh-CN.md: 删除多余的 ``` 闭合,避免
Markdown 后续渲染错乱
- skills/docx/SKILL.md: 翻译时丢失的 • Unicode escape 示例已恢复,
与 zh-CN 版本对齐
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.1 | 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/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/runtime/volta/volta
export VOLTA_HOME=~/.desirecore/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