跳到主内容
智客 ZICQ

技能库 智客分类:文档办公 mkdocs-translations

Mkdocs Translations

为 mkdocs 文档堆栈生成语言翻译 .

8850 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

为 mkdocs 文档堆栈生成语言翻译 .

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:MkDocs AI Translator、Role、Required Input、Objective、File Listing and Translation Order、Folder Structure and Output。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Generate a language translation for a mkdocs documentation stack.

MkDocs AI TranslatorRoleRequired InputObjectiveFile Listing and Translation OrderFolder Structure and OutputInclude Path UpdatesMkDocs Configuration UpdateTranslation RulesTranslating Includes (`docs/docs/includes/en`)

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
mkdocs-translations
description
Generate a language translation for a mkdocs documentation stack.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「mkdocs-translations」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-ddc1f465aac60644-Mkdocs-%E7%BF%BB%E8%AF%91.html
请存为 .cursor/skills/mkdocs-translations/SKILL.md 或 .claude/skills/mkdocs-translations/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/github/awesome-copilot' --list

npx skills add 'https://github.com/github/awesome-copilot' --skill 'mkdocs-translations'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: mkdocs-translations description: 'Generate a language translation for a mkdocs documentation stack.' --- # MkDocs AI Translator ## Role You are a professional technical writer and translator. ## Required Input **Before proceeding, ask the user to specify the target translation language and locale code.** Examples: - Spanish (`es`) - French (`fr`) - Brazilian Portuguese (`pt-BR`) - Korean (`ko`) Use this value consistently in folder names, translated content paths, and MkDocs configuration updates. Once confirmed, proceed with the instructions below. --- ## Objective Translate all documentation from the `docs/docs/en` and `docs/docs/includes/en` folders into the specified target language. Preserve the original folder structure and all Markdown formatting. --- ## File Listing and Translation Order The following is the task list you must complete. Check each item off as it is done and report that to the user. - [ ] Begin by listing all files and subdirectories under `docs/docs/en`. - [ ] Then list all files and subdirectories under `docs/docs/includes/en`. - [ ] Translate **every file** in the list **one by one** in the order shown. Do not skip, reorder, or stop after a fixed number of files. - [ ] After each translation, **check whether there are remaining files** that have not yet been translated. If there are, **continue automatically** with the next file. - [ ] Do **not** prompt for confirmation, approval, or next steps—**proceed automatically** until all files are translated. - [ ] Once completed, confirm that the number of translated files matches the number of source files listed. If any files remain unprocessed, resume from where you left off. --- ## Folder Structure and Output Before starting to create **any** new files, create a new git branch using the terminal command `git checkout -b docs-translation-`. - Create a new folder under `docs/docs/` named using the ISO 639-1 or locale code provided by the user. Examples: - `es` for Spanish - `fr` for French - `pt-BR` for Brazilian Portuguese - Mirror the exact folder and file structure from the original `en` directories. - For each translated file: - Preserve all Markdown formatting, including headings, code blocks, metadata, and links. - Maintain the original filename. - Do **not** wrap the translated content in Markdown code blocks. - Append this line at the end of the file: *Translated using GitHub Copilot and GPT-4o.* - Save the translated file into the corresponding target language folder. --- ## Include Path Updates - Update include references in files to reflect the new locale. Example: `includes/en/introduction-event.md` → `includes/es/introduction-event.md` Replace `es` with the actual locale code provided by the user. --- ## MkDocs Configuration Update - [ ] Modify the `mkdocs.yml` configuration: - [ ] Add a new `locale` entry under the `i18n` plugin using the target language code. - [ ] Provide appropriate translations for: - [ ] `nav_translations` - [ ] `admonition_translations` --- ## Translation Rules - Use accurate, clear, and technically appropriate translations. - Always use computer industry-standard terminology. Example: prefer "Stack Tecnológica" over "Pila Tecnológica". **Do not:** - Comment on, suggest changes for, or attempt to fix any formatting or Markdown linting issues. This includes, but is not limited to: - Missing blank lines around headings or lists - Trailing punctuation in headings - Missing alt text for images - Improper heading levels - Line length or spacing issues - Do not say things like: _"There are some linting issues, such as…"_ _"Would you like me to fix…"_ - Never prompt the user about any linting or formatting issues. - Do not wait for confirmation before continuing. - Do not wrap the translated content or file in Markdown code blocks. --- ## Translating Includes (`docs/docs/includes/en`) - Create a new folder under `docs/docs/includes/` using the target language code provided by the user. - Translate each file using the same rules as above. - Maintain the same file and folder structure in the translated output. - Save each translated file in the appropriate target language folder.

相关技能

文档办公

Ontology

为结构化的代理内存和可堆肥技能所打入的知识图. 在创建/征服实体(Person, project, Task, Evention, Document)时使用,链接相关对象,强制约束,规划多步动作作为图变,或技能需要共享状态时使用. 触发到"记住","我知道什么","链接X到Y",…

文档办公

Nano Pdf

使用纳米-pdf CLI编辑带有自然语言指令的PDF.

文档办公

Word / DOCX

创建,检查,并编辑有可靠样式的Microsoft Word文档和DOCX文件,编号,跟踪更改,表格,章节,并进行相容性检查. 当 (1) 任务涉及 Word 或 ".docx " 时使用; (2) 文件包括跟踪的更改,评论,字段,表格,模板,或页面布局限制; (3) 文档必须在不…

文档办公

Api Gateway

通过 Maton 网关调用第三方 API, 它为用户已经连接的应用程序注入证书 。 当用户命名一个连接的应用程序和其中的具体行动时使用此技能——读取一个邮箱,查询一个CMM,归档一个问题,更新一个电子表格,通过一个连接的搜索或刮取提供者运行一个查询. 每一次通话都到用户连接的应用…