editorial-translation

Translate nonfiction documents between languages while preserving authorial intent and formatting.

1|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/brycehamrick/editorial-skills --skill editorial-translation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editorial-translation
Source: https://github.com/brycehamrick/editorial-skills/tree/main/skills/editorial-translation
Command: npx skills add https://github.com/brycehamrick/editorial-skills --skill editorial-translation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires markdown-it, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates the translation of long-form nonfiction documents while maintaining professional editorial standards, ensuring that intent, tone, and formatting are preserved across languages.

Core Features & Use Cases

  • Context-Aware Translation: Integrates with existing editorial workflows to respect established voice, tone, and style guides.
  • Chunked Processing: Handles large manuscripts by intelligently splitting content into manageable segments while maintaining terminology consistency.
  • Customizable Glossaries: Supports project-specific terminology to ensure technical or brand-specific terms are translated accurately every time.

Quick Start

Use the editorial-translation skill to translate the manuscript file into Spanish using the elegant style preset.

Frequently Asked Questions about editorial-translation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate a long-form markdown manuscript while preserving formatting?

To translate a long-form markdown manuscript while preserving formatting, use automated chunking to split the content into manageable segments. This maintains structural formatting and terminology consistency across large-scale manuscripts.

What is the best way to maintain authorial intent and tone during nonfiction translation?

Context-aware translation is the best way to maintain authorial intent and tone during nonfiction translation. It integrates with existing editorial workflows to respect established voice, style guides, and register across different languages.

Do I need Bun runtime to process large-scale document translation?

Yes, you need the Bun runtime to process large-scale document translation with this approach. Script execution requires Bun to handle automated manuscript chunking and terminology management tasks efficiently.

Can I use custom glossaries for project-specific terminology during localization?

Yes, you can use customizable glossaries for project-specific terminology during localization. This ensures technical or brand-specific terms are translated accurately and consistently every time they appear in the manuscript.

Does editorial translation work with Codex CLI for advanced tasks?

Yes, editorial translation provides optional integration with Codex CLI for advanced tasks. This allows you to handle complex nonfiction translation workflows while preserving structural formatting and editorial context.

Why does my nonfiction translation lose structural formatting across large documents?

Nonfiction translation loses structural formatting across large documents when content is not properly chunked. Automated chunking splits manuscripts into manageable segments while maintaining markdown formatting and terminology consistency.