* 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>
10 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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| python-runtime | Use this skill when the user needs to install, upgrade, or troubleshoot Python and pip environments. Covers four-tier fallback strategy: (1) DesireCore HTTP API for in-app installation, (2) DesireCore built-in Hatch CLI for Python version management, (3) system package managers (brew/apt/dnf/winget), (4) community pyenv as last resort. Also covers virtual environments (venv/pipx/conda), PEP 668 externally-managed errors, and import / PATH troubleshooting. Triggers include: "install python", "pip not found", "python not found", "PEP 668", "externally-managed", "venv", "virtualenv", "pipx", "conda", "miniconda", "pyenv", "hatch", "python version", "pip command not found", or any Python-related runtime error. 使用场景:用户需要 安装 Python、安装 pip、配置虚拟环境、管理多版本、 解决 PEP 668、import 失败、PATH 问题、SSL 证书错误等。 | 1.0.1 | procedural | low | enabled | true |
|
|
|
python-runtime Skill
L0: One-line Summary
When to use: The user needs to install Python / upgrade Python / switch
between multiple Python versions / configure pip / create virtual environments
(venv / pipx / conda) / troubleshoot python: command not found,
pip: command not found, PEP 668 "externally-managed", SSL certificates,
import failures, PATH anomalies, and other Python runtime issues; or when
another skill (docx / pdf / xlsx / pptx) reports "Python unavailable".
How to do it: Prefer DesireCore's built-in Hatch, executing through the four-tier fallback (HTTP API → Hatch CLI → system package manager brew/apt/dnf/winget → community solution pyenv).
L1: Overview and Use Cases
Capability Description
Procedural skill. Before each Python environment operation, first run scripts/probe-python.sh to obtain a JSON snapshot, then follow references/decision-tree (→ ../dev-environment-setup/references/decision-tree.md) to choose a path through the four-tier fallback.
Use Cases
- "python not found" / "pip not found"
- The user requests to install/upgrade Python
- The user requests multi-version management (3.10/3.11/3.12 switching)
- Create/activate/debug virtual environments (venv/pipx/conda)
- "externally-managed-environment" (PEP 668) error
- import failures, PATH issues, SSL certificate errors
- Other skills (docx/pdf/xlsx/pptx) report Python unavailable
Core Value
- DesireCore first: Hatch + HTTP API as mandatory L1/L2, avoiding pollution of system Python
- JSON-driven decisions: the probe script outputs structured data that Claude can parse directly
- Cross-platform consistency: macOS / Linux / Windows share a unified 4-tier fallback
L2: Detailed Specification
Step 1: Environment Probe (mandatory)
bash skills/python-runtime/scripts/probe-python.sh > /tmp/py-probe.json
cat /tmp/py-probe.json | jq .
For the meaning of output fields, see ../dev-environment-setup/references/probe-snapshot.md.
Step 2: Choose an Execution Path
Decide using ../dev-environment-setup/references/decision-tree.md:
| Condition | Path |
|---|---|
desirecore_api is non-empty |
L1 HTTP API |
desirecore_api empty, hatch_path non-empty |
L2 Hatch CLI |
| Neither of the above | L3 system package manager (brew/apt/dnf/winget) |
| L1–L3 all fail or user explicitly requests | L4 community solution (pyenv) |
Step 3: Execute (only the main path is shown; see references for details)
L1: HTTP API (→ references/hatch-desirecore.md)
PORT=$(cat ~/.desirecore/agent-service.port)
BASE="https://127.0.0.1:${PORT}/api/runtime"
# List installable versions
curl -sk "${BASE}/python/available"
# Trigger install (asynchronous; subscribe to runtime:terminal for progress)
curl -sk -X POST "${BASE}/python/install" \
-H "Content-Type: application/json" \
-d '{"version":"3.12"}'
# Force-refresh the cache after install completes
curl -sk -X POST "${BASE}/environment/refresh"
L2: Hatch CLI absolute path (→ references/hatch-desirecore.md)
HATCH=~/.desirecore/runtime/hatch/hatch
export HATCH_HOME=~/.desirecore/runtime/hatch
"$HATCH" python install 3.12
"$HATCH" python show # List installed/installable versions
# Use the Hatch-installed Python directly
~/.desirecore/runtime/hatch/local/3.12/python/bin/python3 -m venv .venv
Windows: %USERPROFILE%\.desirecore\runtime\hatch\hatch.exe.
L3: System Package Manager
| Platform | Command |
|---|---|
| macOS | brew install python3 |
| Debian/Ubuntu | sudo apt install python3 python3-pip python3-venv |
| Fedora/RHEL | sudo dnf install python3 python3-pip |
| Arch | sudo pacman -S python python-pip |
| Windows | winget install Python.Python.3 |
L4: pyenv (→ references/pyenv-fallback.md)
Only enable when the user explicitly requests it or the above paths fail.
Step 4: Virtual Environments
For virtual environment strategy, see references/virtualenv.md:
- venv (recommended, standard library)
- pipx (global CLI tools such as black/ruff/markitdown)
- conda / miniconda (data-science scenarios)
Step 5: Troubleshooting
When errors occur, look up references/troubleshooting.md:
- "python: command not found" / "pip: command not found"
- PEP 668 "externally-managed-environment"
- SSL/TLS certificate errors
- import failures (package name vs. import name differences)
- macOS xcrun / Xcode CLI missing
- Windows PowerShell execution policy blocking scripts
- Proxy environment configuration
Important Constraints
- Never
sudo pip install: always use a virtual environment orpipx. - Refresh after modifying the environment: for L1 call
POST /api/runtime/environment/refresh; for L2/L3/L4 re-run probe. - Cross-skill collaboration: when
docx/pdf/xlsx/pptxreport "Python unavailable", fall into L1/L2 install; for office dependency lookup see../dev-environment-setup/references/office-deps.md. - Do not pollute system Python: at the project level always use venv; for global CLI use pipx.
References
- Decision tree:
../dev-environment-setup/references/decision-tree.md - DesireCore base:
../dev-environment-setup/references/desirecore-runtime.md - Probe protocol:
../dev-environment-setup/references/probe-snapshot.md - Office dependencies:
../dev-environment-setup/references/office-deps.md - System tools:
../dev-environment-setup/references/system-tools.md