issue-identification

Identify and classify translation issues in ULT/Hebrew/Greek texts into 94 types.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/unfoldingWord/bp-assistant-skills --skill issue-identification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-identification
Source: https://github.com/unfoldingWord/bp-assistant-skills/tree/main/.claude/skills/issue-identification
Command: npx skills add https://github.com/unfoldingWord/bp-assistant-skills --skill issue-identification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify translation issues in ULT/Hebrew/Greek texts, enabling systematic discovery and QA across a broad catalog of translation concerns.

Core Features & Use Cases

  • Automated identification and classification of translation issues across ULT, UST, and source languages.
  • Coverage of 94 issue types distributed across 7 categories to support consistent notes and translation decisions.
  • Workflow guidance with references to authoritative decisions, TN indices, and translation templates for reliable notes.

Quick Start

Ask Claude to run the issue-identification skill on a passage to identify translation issues and categorize them by type

Frequently Asked Questions about issue-identification

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

FAQPage Schema
How do I identify translation issues in biblical texts automatically?

To identify translation issues in biblical texts, this Skill analyzes ULT, UST, Hebrew, and Greek source texts, classifying discovered concerns into 94 specific issue types across 7 categories to produce structured, machine-readable metadata for translation QA.

What categories of translation issues can text-analysis tools detect in source languages?

Text-analysis tools for biblical translation detect 94 distinct issue types distributed across 7 categories. This systematic classification covers linguistic concerns found in ULT, UST, Hebrew, and Greek texts to support consistent translation notes and decision-making.

How do I generate structured translation notes from Hebrew and Greek texts?

Generating structured translation notes from Hebrew and Greek texts involves fetching source passages, comparing variants, and classifying linguistic issues. This Skill outputs machine-readable metadata referencing authoritative decisions and TN indices to enable reliable, indexable translation notes.

Can I use issue-identification for automated translation QA workflows?

Yes, issue-identification supports automated translation QA workflows by integrating with workspace tools to fetch text and compare variants. It delivers structured, machine-readable outputs suitable for indexing, discovery, and downstream translation QA pipelines without manual intervention.

What is the best way to classify linguistics problems in ULT and UST texts?

The best way to classify linguistics problems in ULT and UST texts is to run an automated issue-identification process that categorizes translation concerns into 94 types across 7 categories. This ensures consistent notes and references authoritative translation templates.

Do I need source language texts to perform biblical translation issue classification?

Yes, performing biblical translation issue classification requires ULT, UST, Hebrew, or Greek texts as input. The Skill compares these source texts and variants to accurately identify and categorize issues into its 94 predefined types for translation QA.