Update to Sermon Scribe

{
  "description": "Translate a completed Christian sermon, sermon record, or sermon excerpt into another language while preserving theology, Scripture handling, pastoral tone, and speaker intent. Use for monolingual or parallel sermon translations; do not freely localize, rewrite doctrine, or translate from missing source text.",
  "included_files": [],
  "name": "sermon-translate",
  "skill_md_contents": "---\nname: sermon-translate\ndescription: Translate a completed Christian sermon, sermon record, or sermon excerpt into another language while preserving theology, Scripture handling, pastoral tone, and speaker intent. Use for monolingual or parallel sermon translations; do not freely localize, rewrite doctrine, or translate from missing source text.\n---\n\n# Sermon Translate\n\nProduce a faithful target-language sermon that reads naturally to its intended church audience without becoming a theological rewrite.\n\nBefore translating, read [the shared fidelity and style standard](../../references/fidelity-and-style.md). Apply it to both the source interpretation and target text.\n\n## Establish the translation brief\n\nUse the target language, script, locale, audience, Bible version, and parallel-text format given by the user. If only the language is specified, use its broadly understood contemporary written form and preserve the source structure. Ask a narrow question only when an unresolved choice would materially change meaning—for example, Traditional versus Simplified Chinese or a required Bible translation for newly quoted verse text.\n\nTranslate the approved or most complete sermon record when one exists. If the only available source is a raw transcript, translate it faithfully as-is unless the user also asks for reconstruction; do not silently perform a major editorial rewrite.\n\n## Translation priorities\n\n1. Preserve theological meaning, logical relationships, qualifications, and degree of certainty.\n2. Preserve pastoral warmth, humility, reverence, and the preacher's emotional register.\n3. Use natural target-language syntax rather than word-for-word calques.\n4. Keep names, events, testimonies, and applications aligned with the source.\n5. Preserve headings, paragraph relationships, and Scripture references unless the user requests another layout.\n\nUse established target-language Christian terminology when it conveys the same meaning. When a doctrinal term has several plausible renderings and context does not settle it, choose the least interpretive standard term and briefly note the ambiguity only if it matters.\n\n## Scripture and quotations\n\nTranslate sermon prose and source quotations faithfully. For quoted Scripture, retain the source wording when it is already in the target language. Use a named target-language Bible version only when the user specifies it or provides its text. Otherwise translate the supplied wording without falsely labeling it as an official version, or preserve the reference without adding missing verse text.\n\nPreserve exact quotation status: do not turn paraphrase into a direct quote. If a memorable phrase cannot retain both literal wording and rhetorical force, prioritize theological meaning and pastoral intent.\n\n## Quality check and delivery\n\nCheck terminology consistency, pronoun and speaker references, negation, modality, Scripture citations, numbers, names, and paragraph omissions. Ensure the translation does not add explanation or remove a difficult claim.\n\nReturn the translated sermon directly in the requested format. Include translator notes only for material ambiguities, not routine choices. Do not append a command menu or mandatory follow-up prompt.\n"
}