Token导航 LogoToken导航TokenDH.com
开发需要联网github未标认证来源可访问许可证需确认审计未展示

lovstudio%3atranslation-reviewlovstudio%3a 翻译审查

Agent Skill

lovstudio%3atranslation-review 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,023

周安装

41

GitHub Stars

45

下载量

331
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/lovstudio/skills --skill lovstudio:translation-review

简介

lovstudio%3atranslation-review 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。
  • 安装前需确认权限范围和维护状态,注意可能触发联网、命令执行或文件读写操作。
  • 建议结合原始 README 和仓库内容进一步核验具体功能和用法边界。

SKILL.md

translation-review — Chinese-English Translation Review

Systematically compare a Chinese source document against its English translation, identify issues across 6 dimensions, and produce a prioritized review report.

When to Use

  • User provides a Chinese original + English translation pair for review
  • User asks to check/proofread an English translation from Chinese
  • User mentions "翻译检查", "审校", "translation review"

Workflow (MANDATORY)

You MUST follow these steps in order:

Step 1: Collect Input

Use AskUserQuestion to confirm before starting:

Ask the user:

  1. Document type — academic paper (SCI/EI), technical docs, business docs, general
  2. Domain — medicine, CS, law, finance, general (affects terminology checking)
  3. Focus areas — terminology accuracy, grammar, style, references, all (multi-select)

If the user has already provided context (e.g., "SCI 4区医学论文"), skip the obvious questions.

Step 2: Read Both Documents

Read the Chinese source and English translation. For .docx files:

pandoc "<chinese_file>.docx" -t plain --wrap=none
pandoc "<english_file>.docx" -t plain --wrap=none

For .md or .txt files, read directly.

If files are large, read in sections (offset/limit) to stay within context.

Step 3: Systematic Review

Compare the two documents across 6 dimensions, in this order:

D1: Mistranslation (meaning changed)

  • Words/phrases translated to a different meaning
  • Omissions (content in Chinese missing from English)
  • Additions (content in English not in Chinese)
  • Pay special attention to domain-specific terms that have been incorrectly generalized or specialized

D2: Terminology Accuracy

  • Domain-specific terms: check against standard English terminology
  • Abbreviation consistency: first occurrence should have full form + abbreviation
  • Proper nouns: names, institutions, gene/protein names, drug names
  • Units and measurements

D3: Grammar & Syntax

  • Subject-verb agreement
  • Tense consistency (especially in Methods vs Results)
  • Article usage (a/an/the) — common error in Chinese-to-English
  • Dangling modifiers, run-on sentences
  • Passive voice overuse

D4: Consistency

  • Same Chinese term translated differently in different places
  • Formatting inconsistencies (capitalization, hyphenation, number style)
  • Heading style consistency

D5: References & Citations (academic papers only)

  • Citation numbers match between Chinese and English versions
  • Reference format consistency (author names, journal abbreviations)
  • Missing author information in reference entries
  • In-text citation correctness

D6: Style & Register

  • Academic register appropriate for target journal
  • Overly verbose or literary phrasing
  • Chinese-influenced sentence structure (e.g., "through...method" patterns)
  • Paragraph length and structure

Step 4: Source Document Issues

While reviewing, also note issues in the Chinese source that the English faithfully translates but are themselves incorrect. Flag these separately.

Step 5: Generate Report

Output a structured review report with the following format:

# 翻译审校报告 / Translation Review Report

**Document**: [title]
**Reviewer**: 手工川 (AI-assisted)
**Date**: [YYYY-MM-DD]
**Domain**: [domain]
**Document type**: [type]

---

## Summary

[2-3 sentence overall assessment]

---

## A-Level Issues (Must Fix)

### A1. [Issue title]
**Location**: [section/paragraph]
**Original (CN)**: "..."
**Translation (EN)**: "..."
**Problem**: [explanation]
**Suggested fix**: → "..."

---

## B-Level Issues (Recommended)

### B1. [Issue title]
...

---

## Source Document Issues

### C1. [Issue title]
...

---

## Priority Summary

| Priority | # | Issue | Impact |
|----------|---|-------|--------|
| Must fix | A1 | ... | ... |
| ... | | | |

---

## Conclusion

[Overall quality assessment + recommended next steps]

Step 6: Save Report

Save the report to the same directory as the input files:

Filename: 手工川-translation-review-{YYYY-MM-DD}-v0.1.md

If a file with this name exists, increment the version.

Issue Severity Classification

LevelCriteriaExamples
A (Must fix)Meaning changed, factual error, or would cause rejectionMistranslation, wrong terminology, reference number mismatch
B (Recommended)Awkward but understandable, or non-standard usageVerbose phrasing, minor grammar, style inconsistency
C (Source issue)Error in Chinese original, faithfully translatedWrong terminology in Chinese, factual inaccuracy

Domain-Specific Checklists

Academic / SCI Papers

  • Abstract: structured, matches body content
  • Keywords: standard MeSH or domain terms
  • Reference numbers: sequential, match between CN/EN versions
  • Figure/table captions: translated and consistent
  • Statistical reporting: p-values, CI format

Medical / Biomedical

  • Disease names: ICD/MeSH standard
  • Gene/protein names: HUGO/UniProt standard (italics for genes)
  • Drug names: INN (International Nonproprietary Names)
  • Anatomical terms: Terminologia Anatomica standard

Technical Documentation

  • UI strings: consistent with product localization
  • Code snippets: untranslated, syntax preserved
  • API terms: match official documentation

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.9%
按下载量换算122

Claude

31.64%
按下载量换算105

Cursor

20.01%
按下载量换算66

Gemini CLI

8.26%
按下载量换算27

安全审计

暂无安全审计结果可展示。

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills