classical-history-zh-Hans

Control ancient-history EPUB translation with named-entity locking and chapter audits.

248|23|Updated May 10, 2026
One-click install
npx skills add https://github.com/SaberOnGo/public-domain-books-translation --skill classical-history-zh-hans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: classical-history-zh-Hans
Source: https://github.com/SaberOnGo/public-domain-books-translation/tree/main/template/epub_pipeline/profiles/classical-history-zh-Hans
Command: npx skills add https://github.com/SaberOnGo/public-domain-books-translation --skill classical-history-zh-hans

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill keeps ancient-history EPUB translation accurate by controlling identities, chronology, institutions, and annotation depth so the final book stays readable and factually consistent.

Core Features & Use Cases

  • Adds a historical-control overlay for name-heavy works such as chronicles, biographies, diplomacy, warfare, ritual, and political history.
  • Maintains people, places, state relations, and event timelines so chapter translation does not drift on names, dates, or political context.
  • Supports chapter historical audits, random spot-checks, and book-wide defect-family closure when recurring history errors appear.

Quick Start

Use this skill to add the classical-history-zh-Hans overlay to an ancient historical translation project and then build the people, timeline, and chapter audit records before batch translating.

Frequently Asked Questions about classical-history-zh-Hans

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

FAQPage Schema
How do I keep ancient-history EPUB translation accurate when names and chronology drift across chapters?

Ancient-history EPUB translation accuracy is maintained by applying a historical-control overlay that locks named entities, tracks timelines, and performs chapter audits to prevent identity, chronology, and annotation drift.

What is named-entity locking for literary Chinese translation into Simplified Chinese?

Named-entity locking for literary Chinese translation prevents misidentified people, states, and places by maintaining a strict reference profile, ensuring historical context remains factually consistent throughout chronicles and biographies.

How do I stop recurring translation errors in history-dense source texts like chronicles and diplomacy works?

Recurring translation errors in history-dense source texts are resolved through random spot-checks and book-wide defect-family closure, identifying and eliminating systematic mistakes across the entire translated EPUB.

Does this historical translation control work for ritual and political history texts with complex institutions?

Historical translation control works for ritual, political, and diplomacy texts by maintaining state relations and institutional context, adding a historical-control overlay specifically designed for history-dense source texts.

How to start an ancient-history book translation project using layered profile integration?

Start an ancient-history translation project by adding the historical-control overlay, then build people, timeline, and chapter audit records before beginning the batch translation of the EPUB.

When do I need chapter historical audits for Simplified Chinese EPUB translation?

Chapter historical audits are needed when translating history-dense source texts into Simplified Chinese to verify that political context, dates, and named entities have not drifted during the chapter translation process.