安装指南

1. ClawHub CLI 从源直接安装技能的最快方式。
   npx clawhub@latest install translate-to-zh-hans
2. 手动安装 将技能文件夹复制到以下位置之一
   全局模式
   ~/.openclaw/skills/
   工作区
   /skills/
   优先级：工作区 > 本地 > 内置
3. 提示词安装 将此提示词复制到 OpenClaw 即可自动安装。
   请帮我使用 Clawhub 安装 translate-to-zh-hans。如果尚未安装 Clawhub，请先安装（npm i -g clawhub）。
   更倾向于下载？
   获取包含原生技能文件的ZIP压缩包。
   下载技能 (.zip)

什么是

此 Openclaw Skills 工作流会将 ai-thoughts/docs/ 中用户明确选定的一篇文章翻译成简体中文，并保存为对应的 -zh-hans.md 文件。它会保留源文件的 Markdown 结构、链接、代码、技术名称和其他指定内容，同时为技术词汇添加英文释义，并清晰解释不熟悉的概念。
此技能以用户控制权和准确性为核心：它不会自动选择文章或写入文件。执行前会确认源文件和目标文件，检查是否已有译文；遇到内容不明确时会提问，而不是猜测。

应用场景

根据文件名、slug 或日期，为指定文章创建简体中文版。
用户要求翻译文章或制作中文版本时，生成 -zh-hans.md 版本。
翻译技术文章，同时保留命令、代码、产品名称、链接、表格和图片引用。
检查是否已有中文译文，再决定覆盖、比较还是跳过。
遵循一致的双语释义风格，帮助中文读者学习技术文档中使用的英文术语。

工作原理

等待用户准确指定一篇文章；如果未指定，则询问要翻译哪篇文章。
如果用户提供的是 slug 或日期而非路径，则在 ai-thoughts/docs/ 中定位源文件。
确认源文件、准确的输出路径，以及是否允许覆盖现有译文。获得用户批准之前不要写入文件。
检查是否存在现有的 -zh-hans.md 或旧版 -chn.md 译文。如果存在，则暂停并询问用户是覆盖、比较还是跳过。
阅读完整源文件，忠实地将内容翻译成简体中文，并为技术术语及相关标题添加英文释义。
保留 Markdown 结构和指定的原文内容，包括代码、命令、URL、链接、表格、图片路径和产品名称。在 H1 标题后添加所需的 GitHub 绝对源链接。
将译文写入对应的 -zh-hans.md 路径，不更改源文件或范围外文件。
检查文件名、源链接、保留的内容及任何所需的 Arch 签名，然后报告输出路径。

配置指南

未指定单独的安装命令或配置格式。请在包含 ai-thoughts/docs/ 的仓库中使用此技能，并提供要翻译的确切文章。创建或更改输出文件前，工作流要求获得明确批准。
通过文件名、slug 或日期指定一篇源文章。
查看并批准建议的源文件和目标路径；如果已有译文，也要确认覆盖决定。
确认计划后，再要求代理进行翻译。
示例请求：

此技能未定义 CLI 命令。

指示代理翻译一篇指定文章，例如：

"将 260803-ollama-to-llamacpp 翻译为简体中文。"

数据架构

此技能读取一篇 Markdown 文章，并创建一个译文 Markdown 文件。它不定义单独的元数据 schema，也不会生成辅助文件。
项目 约定
源文件 ai-thoughts/docs/ 下的文章，例如 260803-ollama-to-llamacpp.md
新输出文件 文件名和 slug 保持不变，将 .md 改为 -zh-hans.md
输出示例 260803-ollama-to-llamacpp-zh-hans.md
旧版译文 现有 -chn.md 文件保留原名，除非用户明确要求迁移
源文件署名 指向原文章的 GitHub 绝对链接，紧接在 H1 标题之后
保留内容 Markdown 结构、frontmatter、链接、HTML、表格、图片路径、代码、命令及指定专有名词
范围之外 修改源文件、articles.yaml 和 README 文件
默认使用简体中文翻译。技术术语在首次有意义地出现时添加英文释义，包括相关标题和表格单元格；代码块及其他逐字保留的例外内容不作更改。

高级特性

明确审批关卡：
写入前必须指定文章，并由用户确认源文件、目标文件和覆盖计划。
冲突处理：
检测现有的 -zh-hans.md 和旧版 -chn.md 文件，并询问是覆盖、比较还是跳过。
双语技术释义：
为专业术语和标题添加英文对应词，并以通俗语言解释不熟悉的概念。
结构和内容保留：
按要求完整保留 Markdown 组织结构、代码、命令、链接、表格、HTML、frontmatter 和图片引用。
源文件署名：
在翻译后的 H1 标题之后立即插入指向原文章的 GitHub 绝对链接。
Arch 签名处理：
如果源文件末尾出现
btw, i use arch
，则原样保留该行。
准确性保障：
遇到含糊或无法翻译的内容时先请求澄清，不虚构内容；并验证输出路径和受保护内容。

name: translate-to-zh-hans description: > Translate a specific article from ai-thoughts/docs/ into Simplified Chinese,
writing the output to an exactly-same-filename "-zh-hans.md" file. Use when the
user names a specific article and asks to translate it (e.g. "translate 260803-ollama-to-llamacpp", "翻译 xxx", "make a -zh-hans.md version" — or the legacy "make a -chn.md version"). Never
runs automatically; only acts on an explicitly chosen article.

Translate to Chinese (-zh-hans.md)

Translate one article from ai-thoughts/docs/ into Simplified Chinese and write it to a new file with the same filename plus a -zh-hans.md suffix.

Approval gate — read before anything else
Never translate, write, or create anything without explicit user approval. This skill converts on demand only; it does not run automatically and it does not pick candidate articles on its own.
No action if no article is specifically chosen. The user must point out exactly one article (by filename, slug, or date). If they don't, do nothing except ask which one.
Legacy naming: files translated before this rule was standardized are named -chn.md and keep that name until the user explicitly migrates them; every new translation uses -zh-hans.md.
Before writing the output, confirm the plan with the user: the source file, the exact output path, and whether an existing -zh-hans.md should be overwritten.

Inputs

source — Path to the source article, e.g. ai-thoughts/docs/260803-ollama-to-llamacpp.md. Required. If the user only names an article by slug or date, locate it in ai-thoughts/docs/.

Outputs

outputPath — Path to the translated article: docs/-zh-hans.md (replace the .md suffix with -zh-hans.md, keeping the YYMMDD-slug prefix and all characters exactly). Example: 260803-ollama-to-llamacpp.md → 260803-ollama-to-llamacpp-zh-hans.md.

Procedure

Wait for the user to point out the article to translate. Do not start until they name it explicitly.
Confirm the plan with the user: the source file and the output path. Get their go-ahead before writing anything.
Check for an existing translation. If docs/-zh-hans.md — or the legacy docs/-chn.md — already exists, stop and ask whether to overwrite, diff against it, or skip. Never overwrite silently.
Read the source article from source. Understand the full content before translating.
Translate the body into Simplified Chinese:
Keep the title as an H1 with the key term followed by a Chinese translation (match the style of existing Chinese pairs — most are still legacy -chn.md).
Right after the H1, add the source link line, using the absolute GitHub URL (the j3ffyang repo), not a relative link: 原文：
Translate the running text, headings, and bullets faithfully and naturally. Do not add, remove, or reorder content.
Write Simplified Chinese by default; Traditional Chinese only when the source was originally written that way.
Apply the bilingual-gloss style below: gloss technical terms and section titles, and add plain-language explanations for unfamiliar concepts.
Do not translate specific terms — leave them verbatim:
Product, tool, and agent names: Hermes Agent, OpenCode, OpenClaw, Astro, etc.
Technical terms, commands, flags, config and file names (AGENTS.md, SOUL.md, .cursorrules, hermes -c), environment variables, URLs.
Code blocks, inline code, CLI keystrokes (Ctrl+C, Alt+Enter).
Existing proper nouns already in Latin script. Only translate the surrounding prose; never translate inside code.
Preserve everything else exactly: ../imgs/ image references (keep the path verbatim — Chinese files mirror English per AGENTS.md), links, HTML, tables, frontmatter (if any), and Markdown structure.
Write the output to docs/-zh-hans.md with the source link line followed by the translated body.
Arch sign-off: if the source ends with btw, i use arch, append the identical line at the bottom of the -zh-hans.md. Keep it verbatim English — do not translate.
Report outputPath to the user. Do not modify the source file, and do not touch articles.yaml or the READMEs (out of scope for this skill).
Bilingual-gloss style (default)

Every -zh-hans.md uses this style: Simplified Chinese is the primary text, and English is added as glosses so a Chinese-only reader still gets the technical vocabulary. The source article stays as-is; the glosses and explanations live only in the -zh-hans.md.

Gloss technical terms inline. The first meaningful time a technical term appears, follow it with the English in parentheses: 技能 (skill), 无头 (headless), 密钥链 (keychain), 接口额度 (API quota). Don't gloss every repetition or everyday words — only technical or specialized vocabulary.
Gloss section titles. Add the gloss to headings that contain technical terms: ## 技能 (skill) 是什么, ## 无头 (headless) 环境下的认证.
Add plain-language explanations. For concepts a general reader won't know (e.g. what 无头 (headless) 环境 means), add a short, simple explanation in plain Chinese at the first use. Understanding beats literal fidelity here — the explanation may be a small addition to the source, since the goal is a standalone readable article for a Chinese audience.
Gloss inside tables too. The same rules apply to table cells — gloss technical terms on first appearance: | 我——思维流 (thought-flow) | OpenCode + git——工作流 (workflow) |.

The verbatim exceptions from Procedure step 6 still apply: code, commands, product names, and URLs stay untouched, and glosses never go inside code blocks.

Quality rules

Avoid hallucination. If a word, reference, or term is unclear, do not guess — ask the user or flag it in the report. Never invent translations, names, dates, or content that is not in the source.
Ask if anything is unclear — about the article, an ambiguous phrase, an unknown acronym, or the intended output. Clarify rather than assume.
Translate meaning faithfully and naturally in Simplified Chinese; do not perform a word-for-word substitution.

Verification

Output is at docs/-zh-hans.md; the prefix and slug match the source filename exactly (only the .md → -zh-hans.md suffix changed).
The source link line is present right after the H1 and uses the absolute GitHub URL: 原文： .
Every ../imgs/ reference in the output matches one in the source (verify with a glob/ls against ai-thoughts/imgs/).
Code blocks, inline code, commands, and specific terms (e.g. Hermes Agent, OpenCode) are preserved verbatim.
The bilingual-gloss style is applied: technical terms and headings carry English glosses, table cells are glossed on first appearance, and unfamiliar concepts get a plain-language explanation at first use.

If the source ends with the arch sign-off (btw, i use arch), the -zh-hans.md carries the identical verbatim line.

The source file is unmodified (confirm via git status/diff).

Error Handling

No article chosen: do nothing; ask the user which article to translate.
Source not found: list candidate files in ai-thoughts/docs/ and ask which to use.
Output already exists: stop and ask whether to overwrite, diff against it, or skip.
Ambiguous or untranslatable content: ask the user instead of guessing.

Arch Sign-off

圣维拉诺