JimLiu/baoyu-skills / skills/baoyu-translate
baoyu-translate
FlaggedThis skill should be used when the user asks to "translate", "翻译", "精翻", "translate article", "translate to Chinese", "translate to English", "改成中文", "改成英文", "convert to Chinese", "localize", "本地化", "refined translation", "精细翻译", "proofread translation", "快速翻译", "快翻", "这篇文章翻译一下", or provides a URL/file with translation intent. Supports three modes (quick/normal/refined) with custom glossary support.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.7 KB |
| references/config/extend-schema.md | markdown | 3.3 KB |
| references/config/first-time-setup.md | markdown | 3.9 KB |
| references/glossary-en-zh.md | markdown | 842 B |
| references/refined-workflow.md | markdown | 4.6 KB |
| references/subagent-prompt-template.md | markdown | 3.2 KB |
| references/workflow-mechanics.md | markdown | 625 B |
| scripts/bun.lock | other | 1.4 KB |
| scripts/chunk.ts | script | 8.2 KB |
| scripts/main.ts | script | 1.4 KB |
| scripts/package.json | manifest | 110 B |
references/refined-workflow.md
View on GitHub# Translation Workflow Details
Per-step guidelines. All intermediate results are saved in the output directory.
## Step 1: Content Analysis
Save to `01-analysis.md`.
### 1.1 Content Summary
- What is this content about? What is the core argument?
- Author background, stance, and writing context
- Purpose and intended audience of the original
### 1.2 Terminology
- List technical terms, proper nouns, brand names, acronyms
- Cross-reference with loaded glossaries
- For terms not in glossary, determine standard translations
- Record in a terminology table
### 1.3 Tone & Style
- Formal or conversational? Humor, metaphor, cultural references?
- What register is appropriate for the translation given the target audience?
### 1.4 Translation Challenges
- **Comprehension gaps**: Terms or references that target readers may not understand — note what explanation is needed
- **Figurative language**: Metaphors, idioms, expressions that don't translate literally — note intended meaning and target-language approach (interpret / substitute / retain)
- **Structural challenges**: Long complex sentences, wordplay, puns, or humor that needs creative adaptation
**Save `01-analysis.md`** with:
```
## Content Summary
[Core argument, author, context, purpose]
## Terminology
[term → translation, ...]
## Tone & Style
[assessment]
## Translation Challenges
- [term/passage] → [challenge type] → [suggested approach]
- ...
```
## Step 2: Assemble Translation Prompt
Main agent builds the prompt from `01-analysis.md` using [references/subagent-prompt-template.md](subagent-prompt-template.md), inlining:
- **Target style**: Resolved style preset + source voice assessment from §1.3
- **Content background**: Summary from §1.1
- **Glossary**: Merged glossary with analysis-extracted terms from §1.2
- **Translation challenges**: All challenges from §1.4
Save to `02-prompt.md`; used by subagents (chunked) or the main agent (non-chunked).
## Step 3: Initial Draft
Save to `03-draft.md`. Chunked: merged from subagent chunk translations; non-chunked: the main agent translates directly. Follow `02-prompt.md` and the **Translation principles** in SKILL.md.
## Step 4: Critical Review
Main agent reviews the draft against the source → `04-critique.md`. **Diagnosis only** — no rewriting yet.
### 4.1 Accuracy
- Compare each paragraph against the original
- Verify facts, numbers, dates, proper nouns
- Flag content accidentally added, removed, or altered
- Check terminology consistency with glossary
### 4.2 Native Voice
- Flag sentences that read as "translated" rather than "written" — unnatural word order, calques, stiff phrasing
- For CJK targets: check for unnecessary connectives (因此/然而/此外), passive voice abuse (被/由/受到), noun pile-ups, over-nominalization
- Flag metaphors translated literally that sound unnatural in the target language
- Check emotional connotations are preserved, not flattened
- Note where sentence restructuring would improve readability
### 4.3 Notes & Adaptation
- Are translator's notes accurate, concise, and genuinely helpful?
- Flag missed comprehension challenges that need notes, and over-annotations on obvious terms
- Were translation strategies from `02-prompt.md` followed?
- Do cultural references work in the target language?
**Save `04-critique.md`** with:
```
## Accuracy
- [issue]: [location] — [description]
## Native Voice
- [issue]: [example] → [suggested fix]
## Notes & Adaptation
- [add/remove/revise]: [term/passage] — [reason]
## Summary
[Overall assessment: X critical issues, Y improvements]
```
## Step 5: Revision
Read `03-draft.md` and `04-critique.md`; apply all findings (fix accuracy issues, rewrite unnatural expressions, adjust notes, improve flow) → `05-revision.md`.
## Step 6: Polish
Final publication-quality pass on `05-revision.md` → `translation.md`:
- Read it as a standalone piece — does it flow as native content?
- Smooth remaining rough transitions
- Ensure consistent narrative voice and style throughout
- Final terminology consistency check
- Verify formatting is preserved correctly
## Chunked Refined Translation
Subagents (one per chunk, in parallel) only produce the Step 3 draft; the main agent does everything else:
1. Analysis (Step 1) on the **entire** document first → `01-analysis.md`
2. Assemble prompt → `02-prompt.md`
3. Split into chunks → `chunks/`
4. Subagents translate chunks (each reads `02-prompt.md`) → merge into `03-draft.md`
5. Review → `04-critique.md`; revise → `05-revision.md`; polish → `translation.md`
6. Final cross-chunk consistency check: terminology, narrative flow, transitions at chunk boundaries
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |