inkos-translation

Translates long-form text across languages with glossary consistency and segmented review.

9.4k|1.8k|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Narcooo/inkos --skill inkos-translation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inkos-translation
Source: https://github.com/Narcooo/inkos/tree/main/packages/core/skills/inkos-translation
Command: npx skills add https://github.com/Narcooo/inkos --skill inkos-translation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Long-form translation often breaks down through inconsistent terminology, lost context between segments, and abandoned progress when a parser or provider fails. This Skill provides a disciplined method for translating and reviewing lengthy texts while preserving meaning, voice, and continuity.

Core Features & Use Cases

  • Terminology Consistency: Treats the project glossary as persistent authority, reusing established names and terms across the entire work.
  • Segment-Aware Translation: Keeps segment boundaries operational while reading neighboring segments and chapter context as one passage, so references and cadence survive batching.
  • Resumable Workflows: Preserves completed segments and resumes from the first unfinished segment after parser or provider failures.
  • Use Case: Translating a serialized novel chapter by chapter into another language, where character names, invented terms, and tone must stay identical across hundreds of segments, with chapter-level review for fidelity and readability.

Quick Start

Translate this novel chapter into English using the project glossary, keeping character names and tone consistent with previous chapters.

Frequently Asked Questions about inkos-translation

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

FAQPage Schema
How do I translate a long novel while keeping terminology consistent?

Maintain a project glossary as the persistent authority for names, titles, and invented terms, and reuse established renderings in every segment. When context changes the correct rendering, update the glossary with a note instead of allowing silent variation.

How to translate text in segments without losing context?

Keep segment boundaries operational but read neighboring segments and the full chapter as one passage before translating. Review at chapter scope so local fluency does not break character voice, references, or terminology across segments.

What should a translation review check for?

Review should check fidelity, missing content, added content, terminology, referents, names, numbers, and target-language readability, each backed by concrete evidence. A parser or provider failure is not a translation-quality verdict and should be handled separately.

What happens when a translation provider fails mid-chapter?

Completed segments are preserved and work resumes from the first unfinished segment rather than restarting. Provider or parser failures are treated as operational issues, not as judgments about translation quality.

Can the translation summarize or adapt the source text?

No. The method forbids summarizing, expanding, censoring, or improving the source unless the user explicitly requests adaptation. Ambiguity is resolved conservatively, with a note recorded when it materially affects meaning.