技能介绍
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
做什么
当用户想翻译寄存器 README,制作回波多语种,将docs本地化,添加语言切换器,将README国际化,或者在一个 GitHub 风格的寄存器中更新本地化的README 变体时使用.
何时用
用户想要翻译一个寄存器 README, 制作一个多语种的 Repo, 本地化 Docs, 添加语言切换器, 将 README 国际化, 或在 GitHub 风格的寄存器中更新本地化的 README 变体
代理如何加载
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Inputs、Defaults And Decision Rules、Workflow、1. Establish the source README and languages、2. Audit the Markdown structure before translating、3. Translate only the prose layer。 其中含规范建议的小节:分步指令。
文件分析
文件分析:除 SKILL.md 外,正文引用了 references/preservation-checklist.md、references/language-selector-reference.md,属于带资源的技能包,这些文件按需再读。
官方 description(原文)
Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.
Inputs Defaults And Decision Rules Workflow 1. Establish the source README and languages 2. Audit the Markdown structure before translating 3. Translate only the prose layer 4. Preserve structure while writing the localized README 5. Rewrite localized anchors and anchor-dependent links 6. Write sibling files using the repo's naming pattern 7. Insert or update the language selector 8. Final verification Output
来源分类:skills.sh agent-skill
来源与网址
namereadme-i18n
descriptionUse when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.
发现技能 客户端向 Agent 提供名称与描述目录。
匹配与调用 用户指定或任务匹配后,载入 SKILL.md 指令。
按需加载 按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 2 references/preservation-checklist.mdreferences/language-selector-reference.md以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。
具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。
交给 Agent 安装
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「readme-i18n」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-719aeebe268c8ffd-%E8%AF%BB%E5%8F%96-I18n.html
请存为 .cursor/skills/readme-i18n/SKILL.md 或 .claude/skills/readme-i18n/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/xixu-me/skills 取完整目录,不要只建一个 SKILL.md。
复制安装提示词 GitHub 完整包 ↗
终端安装 · Skills CLI
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/xixu-me/skills' --list
复制查看命令
目标客户端
安装时交互选择 Codex Claude Code Cursor
安装范围
当前项目 我的所有项目
npx skills add 'https://github.com/xixu-me/skills' --skill 'readme-i18n' 复制安装命令
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
SKILL.md 原文 可复制,不会改动源文件
复制 SKILL.md
恢复原文
阅读排版
---
name: readme-i18n
description: Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.
---
Localize a repository `README.md` without breaking the repo mechanics around it.
The default job is translate + wire-up:
- read the source-of-truth README
- create localized sibling files such as `README.zh.md`
- preserve GitHub-flavored Markdown structure and repo-specific tokens
- add or update a shared language selector near the top of every variant
This skill is for multilingual README workflows, not general website/app i18n.
## Inputs
Expect these inputs when available:
- source README path, default `README.md`
- source language, default inferred or English
- one or more target languages
- optional glossary or do-not-translate list
- optional filename override if the repo already uses a different multilingual naming pattern
If target languages are not named, inspect existing translated files, selectors, filenames, issues, or prior repo conventions. If that still leaves the target languages unclear, ask once. Do not invent target languages.
## Defaults And Decision Rules
- Treat the root `README.md` as the source-of-truth unless the user explicitly says otherwise.
- If the source language is ambiguous, ask once. Otherwise assume English.
- Keep section order aligned with the source README. Only make a small heading wording adjustment when needed to produce a valid localized anchor.
- Output localized siblings with `README..md` naming unless the repo already has a different established pattern that should be preserved.
- Update an existing language selector in place. Do not duplicate it.
- Translate only human-language content.
- Preserve project names, package names, commands, CLI flags, option names, environment variables, URLs, file paths, inline code, code fences, HTML attributes, and badge/image URLs.
- Badge alt text or visible labels may be translated only when the change does not require changing the badge URL, query params, or image source.
- If a glossary or do-not-translate list is provided, apply it consistently across every target language.
## Workflow
### 1. Establish the source README and languages
- Confirm the source README path. Default to `README.md`.
- Identify the source language from the file contents and repo context.
- Determine target languages from the request or existing repo pattern.
- Note any glossary terms, product names, or phrases that must stay untranslated.
### 2. Audit the Markdown structure before translating
Read the source README once as structure, not prose. Open [`references/preservation-checklist.md`](./references/preservation-checklist.md) and inventory the elements most likely to break:
- headings and heading levels
- badge rows, shields URLs, and image links
- tables and alignment rows
- raw HTML blocks and inline HTML
- GitHub alerts or admonitions such as `> [!NOTE]`
- code fences, inline code, commands, and config snippets
- intra-document anchors such as `(#installation)`
- relative links to files, docs, screenshots, or other README variants
If the README already has localized siblings, inspect them too before choosing filenames or selector style.
### 3. Translate only the prose layer
Translate:
- paragraph text
- list item prose
- table cell prose
- visible text inside HTML blocks
- image alt text when safe
- selector labels and other human-facing labels
Do not translate:
- fenced code blocks
- inline code spans
- shell commands
- flags such as `--help`
- env vars such as `OPENAI_API_KEY`
- URLs
- file paths
- repo/package/project identifiers
- badge and image URLs
When in doubt, preserve the literal token and translate the surrounding sentence instead.
### 4. Preserve structure while writing the localized README
- Keep the same heading hierarchy and section order as the source.
- Keep the same number of code fences unless the user explicitly asks to rewrite examples.
- Preserve table shape, list nesting, HTML wrappers, and Markdown comments.
- Preserve relative links unless a link intentionally needs to point at a localized sibling README.
### 5. Rewrite localized anchors and anchor-dependent links
When a translated heading changes, GitHub will generate a different heading ID. After translating headings:
- rewrite every same-file `(#...)` link so it matches the localized heading slug in that file
- preserve custom explicit anchors such as `
` unless the file already uses localized explicit IDs
- verify that every intra-document anchor target resolves to an existing heading or explicit anchor
Prefer a small heading wording adjustment over a broken anchor. The section order should still match the source README.
### 6. Write sibling files using the repo's naming pattern
Default to sibling filenames like:
- `README.zh.md`
- `README.es.md`
- `README.fr.md`
If the repo already uses a different multilingual naming pattern, keep using it consistently rather than forcing the default pattern.
### 7. Insert or update the language selector
Open [`references/language-selector-reference.md`](./references/language-selector-reference.md) before editing selectors.
Placement:
- keep the selector near the top of the file
- if the README starts with a title, badges, hero image, or short intro block, place the selector immediately after that opening cluster
Behavior:
- update an existing selector block in place if one already exists
- if you add a new selector, use the canonical marker comments from the reference file so later runs can update it deterministically
- emphasize the current language and link the other variants
- keep selector order and labels consistent across every README variant
### 8. Final verification
Before finishing, verify:
- localized filenames follow the chosen pattern
- every README variant contains exactly one selector block
- code fence counts are preserved
- badge/image URLs and relative file links still point to the original targets unless intentionally localized
- every `(#...)` link resolves inside its own file
- the localized README still feels structurally identical to the source
## Output
Produce:
- one localized sibling README per target language
- an updated selector block in every README variant
- a brief note to the user covering created or updated files, any assumptions, and any terms intentionally left untranslated
## Maintenance Note
Keep `README.md` as the canonical source unless the user says otherwise. When the source README changes later, update each localized sibling by diffing the changed prose, then re-check selectors, filenames, and anchor links instead of reformatting the whole file from scratch.
## Example Prompts
**Example 1**
`Translate this README into Chinese and add a language switcher. Keep badge URLs, code fences, and all commands exactly as they are.`
**Example 2**
`Make the repo multilingual. Add Spanish and Chinese README variants, keep the internal anchor links working, and wire the selector into every file.`
**Example 3**
`We already have README.zh.md. Add README.es.md and update the existing selector in place instead of adding a second one.`
## Common Mistakes
- Translating fenced code blocks or inline code instead of only the prose around them
- Duplicating the language selector instead of updating the existing block
- Translating a heading but forgetting to rewrite same-file `(#...)` links
- Changing badge URLs or image sources while trying to translate visible labels
- Reordering sections in the localized README even though the source README is the authority
相关技能
Agent 工作流
创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.
Agent 工作流
使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.
Agent 工作流
管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.
Agent 工作流
Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…