translation-checking
Guide translators through systematic checking of Bible translations using unfoldingWord open-licensed translation resources served by the translation-helps MCP server.
Works with
Agent Skills format with YAML frontmatter. Claude Code reads it as-is.
--- name: "translation-checking" description: "Guide translators through systematic checking of Bible translations using unfoldingWord open-licensed translation resources served by the translation-helps MCP server." license: "MIT" --- # Translation Checking with unfoldingWord Resources Guide translators through systematic checking of Bible translations using unfoldingWord open-licensed translation resources served by the translation-helps MCP server. ## Available Resources The translation-helps MCP server provides these resource types: - **Scripture texts**: ULT (Unfoldingword Literal Text), UST (Unfoldingword Simplified Text), and other versions - **Translation Notes (TN)**: Verse-by-verse explanations of translation challenges, key terms, and alternative renderings - **Translation Words (TW)**: Articles defining important biblical terms with cross-references - **Translation Questions (TQ)**: Comprehension questions to verify the translation communicates the intended meaning - **Translation Academy (TA)**: Training modules on translation principles, grammar, and figures of speech ## Checking Workflow When checking a passage, follow this order: ### 1. Gather Context Fetch the scripture text for the passage in both ULT and UST. The ULT shows a form-based translation close to the original language structure. The UST shows a meaning-based rendering in natural language. Comparing these two helps the translator understand both the form and the meaning of the source text. ### 2. Review Translation Notes Fetch translation notes for each verse in the passage. Notes explain difficult phrases, identify figures of speech, clarify ambiguities, and suggest alternative ways to express the meaning. Present each note alongside the relevant verse text so the translator can see the connection. ### 3. Check Key Terms Fetch translation word links for the passage to identify which biblical terms appear. Then fetch the full article for each term. Key terms need consistent translation throughout a book. Flag any terms that the translator should pay special attention to. ### 4. Verify Comprehension Fetch translation questions for the passage. These questions test whether a reader of the translation would understand the intended meaning. Present them as a checklist the translator can work through with their draft. ### 5. Reference Training Material If the translation notes reference Translation Academy articles (e.g., for figures of speech like metaphor, metonymy, or for translation concepts like implicit information), fetch those articles to give the translator deeper background. ## Language Support The server supports multiple languages. Always ask which language the translator is working in if not specified. Use the simple-languages tool to discover available languages, and get-available-books to check which books have resources in that language. ## Output Guidelines - Present scripture texts in block quotes for easy visual distinction - Group translation notes by verse - Bold key terms on first mention and link to their definitions - Number translation questions for easy reference - When comparing ULT and UST, present them side by side or in sequence with clear labels - Keep responses focused on the requested passage ## Detailed Reference See references/resource-guide.md for detailed information about each resource type, data formats, and advanced usage patterns.
More General & Other skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

