Token导航 LogoToken导航

Agent Skill · 开发

xdoc-translation(xdoc 翻译)

xdoc-translation 用于整理文档、README、Markdown 和说明材料,适合在 OpenClaw 中需要把零散信息整理成结构清晰的文档时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

xdoc-translation 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 6,039。

总安装 5,232周安装 218GitHub Stars 1下载 1,744核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.2

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:xdoc-translation(xdoc 翻译)
来源仓库:https://github.com/yangsongbai1/xdoc-translation
安装命令:
openclaw skills install xdoc-translation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install xdoc-translation

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

用于整理文档、README、Markdown 和说明材料,适合在 OpenClaw 中结构化零散信息。支持多种文件格式的文档整理与文本翻译服务。可通过 openclaw skills install xdoc-translation 安装使用。建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

可结合来源仓库和原始 README 进一步核验具体用法。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install xdoc-translation;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

xdoc-translation 怎么安装?

在终端执行 openclaw skills install xdoc-translation。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

xdoc-translation 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

xdoc-translation 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

xdoc-translation 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

xdoc-translation 用的人多吗?

公开数据是累计安装 5,232 次,近一周安装 218 次,下载 1,744 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

xdoc-translation 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
xdoc-translation

xdoc 翻译 · 本页

5,2321接触敏感数据MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Xdoc Translation API Skill

You are a document translation assistant powered by the Xdoc Translation API. This skill enables you to translate documents and text between multiple languages.


Authentication & API Key

How to Get an API Key

  1. Visit https://translation.x-doc.ai/
  2. Sign up or log in to your account
  3. Navigate to User → API Management → My API
  4. Click Create API Key and copy your key
  5. Store the API key securely (it will only be shown once)

Required Credential

VariableDescriptionRequired
XDOC_API_KEYYour Xdoc API keyYes

The API key must be provided as an environment variable XDOC_API_KEY or passed via the x-api-key HTTP header.

Security Notes

  • Never share your API key in public repositories or logs
  • API keys are tied to your account and usage quota
  • You can revoke and regenerate keys at any time from the dashboard
  • All API requests are encrypted via HTTPS

Service Information

PropertyValue
ProviderXdoc (https://x-doc.ai)
API Base URLhttps://translation.x-doc.ai/api/open_api/v1
Supportsupport@x-doc.ai

Core Workflow

Document Translation Flow

1. Create Upload URL → 2. Upload File → 3. Submit Translation → 4. Poll Status → 5. Download Result

Step-by-Step:

  1. Create Upload URL
   POST /files/create_upload_url
   Headers: x-api-key: <your_api_key>
   Body: {"filename": "report.docx", "is_can_edit": true}
   Returns: file_id, upload_url, content_type
  1. Upload File

- Option A: User uploads via upload_page_url in browser (drag-and-drop) - Option B: PUT request to upload_url with file content

  1. Submit Translation
   POST /translate/document
   Headers: x-api-key: <your_api_key>
   Body: {
     "file_id": 123456789,
     "source_language": "en",
     "target_language": "zh-cn",
     "trans_mode": "master"
   }
  1. Poll Status (every 3-5 seconds)
   POST /translate/status
   Headers: x-api-key: <your_api_key>
   Body: {"file_id": "123456789"}
   Returns: status_name (parsing/translating/compositing/completed)
  1. Download Translation

- When status_name == "completed", response includes download_url


API Capabilities

Document Translation

FunctionEndpointMethod
Create Upload URL/files/create_upload_urlPOST
Submit Translation/translate/documentPOST
Check Status/translate/statusPOST
Delete File/files/deletePOST

Text Translation

FunctionEndpointMethod
Instant Translate/text/translatePOST

Glossary (Term Library)

FunctionEndpointMethod
Create Glossary/term-libs/createPOST
List Glossaries/term-libs/listPOST
Edit Glossary/term-libs/editPOST
Delete Glossary/term-libs/deletePOST
Add Terms/term-entries/addPOST
List Terms/term-entries/listPOST
Edit Term/term-entries/editPOST
Delete Terms/term-entries/deletePOST

Translation Memory

FunctionEndpointMethod
Create Memory/memory-libs/createPOST
List Memories/memory-libs/listPOST
Edit Memory/memory-libs/editPOST
Delete Memory/memory-libs/deletePOST
Add Entries/memory-entries/addPOST
List Entries/memory-entries/listPOST
Edit Entry/memory-entries/editPOST
Delete Entries/memory-entries/deletePOST

Utility

FunctionEndpointMethod
Get Supported Languages/languagesGET

Usage Guide

Translation Modes

  • deep: Standard quality, faster processing
  • master: Premium quality, recommended for professional use

Supported File Formats

docx, doc, pdf, pptx, ppt, xlsx, xls, txt, xml

PDF Handling

  • Editable PDF (with selectable text): is_can_edit: true
  • Scanned/Image PDF: is_can_edit: false (enables OCR)

Using Glossaries

Ensure consistent terminology by specifying glossary IDs:

{
  "file_id": 123456789,
  "source_language": "en",
  "target_language": "zh-cn",
  "term_lib_ids": [1, 2]
}

Using Translation Memory

Reuse previous translations with memory libraries:

{
  "file_id": 123456789,
  "source_language": "en",
  "target_language": "zh-cn",
  "memory_libs": [
    {"memory_lib_id": 1, "threshold": 0.8}
  ]
}
  • threshold: Match threshold, 0-1, default 0.8

Status Reference

Translation Status Flow

parsing → pending → translating → compositing → completed
    ↓         ↓           ↓
parse_failed  ...   translation_failed

Status Definitions

StatusMeaningAction
parsingParsing documentContinue polling
pendingWaiting for translationContinue polling
translatingTranslation in progressContinue polling
compositingGenerating output fileContinue polling
completedDoneGet download_url
parse_failedParse errorCheck file format
translation_failedTranslation errorRetry or contact support

Language Codes

CodeLanguageCodeLanguage
enEnglishzh-cnChinese (Simplified)
jaJapanesekoKorean
deGermanfrFrench
esSpanishptPortuguese
ruRussianarArabic
thThaiviVietnamese
zh-twChinese (Traditional)itItalian

Use /languages endpoint for the complete list.


Example Scenarios

Scenario 1: Translate a Word Document

User: Translate report.docx from English to Chinese

Steps:
1. Call create_upload_url to get upload info
2. Provide upload_page_url to user for upload, or upload directly
3. Call translate_document to submit translation
4. Poll translate/status until completed
5. Return download_url to user

Scenario 2: Instant Text Translation

User: Translate "Hello World" to Japanese

Call:
POST /text/translate
{"text": "Hello World", "source_language": "en", "target_language": "ja"}

Returns: "こんにちは世界"

Scenario 3: Translate with Glossary

1. Create glossary and add terms
2. Specify term_lib_ids when translating
3. Ensures consistent translation of technical terms

Error Handling

All API responses follow this format:

{
  "code": 0,
  "message": "success",
  "data": { ... }
}

Success

CodeMessageDescription
0successRequest completed successfully

Authentication Errors (910xx)

CodeMessageResolution
91000API Key is requiredAdd x-api-key header
91001Invalid API KeyCheck your API key is correct
91002API Key has expiredRenew your API key
91003API Key is disabledContact support or create new key
91004API Key is not yet effectiveWait until the key activation date
91005Customer not foundVerify your account status
91006Rate limit exceededReduce request frequency, retry later

File Translation Errors (911xx)

CodeMessageResolution
91100File size exceeds the limitReduce file size (max 50MB)
91101File type not supportedUse supported formats: docx, pdf, pptx, xlsx, txt, xml
91102File upload failedRetry upload
91103File not foundVerify file_id is correct
91104File status does not allow this operationCheck current file status
91105Insufficient account balanceTop up your account
91107Task not foundVerify task_id is correct
91108Task not completed, cannot downloadWait for translation to complete
91109Translated file not foundRetry translation
91110Failed to get download URLRetry later
91111File is being translated, cannot operateWait for current translation to finish
91112File has not been uploaded yetUpload file before submitting translation

Glossary Errors (912xx)

CodeMessageResolution
91200Term library name already existsUse a different name
91201Term library not foundVerify term_lib_id is correct
91202Source term already existsUpdate existing term instead
91203Term entry not foundVerify entry_id is correct
91204Entry list cannot be emptyProvide at least one entry

Translation Memory Errors (913xx)

CodeMessageResolution
91300Memory library name already existsUse a different name
91301Memory library not foundVerify memory_lib_id is correct
91302Memory entry not foundVerify entry_id is correct
91303Entry list cannot be emptyProvide at least one entry

Text Translation Errors (915xx)

CodeMessageResolution
91500Text exceeds model token limitReduce text length (max 5000 chars)
91501Translation service errorRetry later
91502Translation returned empty resultCheck source text is valid

Best Practices

  1. Polling Interval: Wait 3-5 seconds between status checks
  2. File Size: Recommended max 50MB per file
  3. Concurrency: Max 10 simultaneous translation tasks
  4. Glossaries: Use same glossary for documents in the same domain
  5. Memory Maintenance: Regularly clean outdated translation memories

Privacy & Data Handling

  • Data Encryption: All data transmitted via HTTPS/TLS
  • Data Retention: Uploaded files are automatically deleted after 7 days
  • No Third-Party Sharing: Your documents are not shared with third parties
  • Compliance: Service complies with GDPR and data protection regulations
  • Data Location: Files are processed and stored in secure cloud infrastructure

For privacy policy details, visit: https://x-doc.ai/privacy

平台分布

OpenClaw

70.43%
按下载量换算1,228

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills