chapter-intro

Generate translator-focused chapter introductions summarizing movement, themes, and translation challenges.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chapter introductions provide translators with a concise orientation to the chapter's movement, themes, and translation considerations, saving time and reducing guesswork.

Core Features & Use Cases

  • Generate 300-600 character chapter introductions that summarize function and content.
  • Adapt to book and chapter using pipeline context (ULT/UST, notes) when available.
  • Produce translator-oriented summaries to support reference work and notes.

Quick Start

Ask CLAUDE to generate a chapter introduction for a specific book and chapter.

Frequently Asked Questions about chapter-intro

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

FAQPage Schema
How do I write a concise chapter introduction for biblical translation?

Generate a 300-600 character biblical chapter introduction that orients translators to the chapter's movement, themes, and translation challenges using available pipeline outputs. This provides a concise summary while avoiding verse-level details.

What should be included in biblical translation introductions for chapters?

Biblical chapter introductions should include the chapter's movement, themes, and translation considerations. They must orient translators to the content while avoiding specific verse-level details to maintain a concise overview.

Can I use ULT and UST pipeline outputs to generate chapter introductions?

Yes, you can leverage available ULT and UST pipeline outputs and notes when present to generate chapter introductions. The system adapts to the specific book and chapter using this pipeline context.

How long should a translator-focused chapter introduction be?

A translator-focused chapter introduction should be 300-600 characters long. This concise length ensures it orients translators to the chapter's movement and themes without overwhelming them with verse-level details.

What is the best way to ensure consistent chapter introductions across biblical books?

To ensure consistent chapter introductions across biblical books, apply a standardized style guideline that produces 300-600 character summaries focused on chapter movement, themes, and translation challenges rather than verse-level details.

Why do my biblical chapter introductions include too many verse-level details?

Biblical chapter introductions often include too many verse-level details when lacking a strict style guideline. The system avoids this by focusing on the chapter's movement, themes, and translation challenges within a 300-600 character limit.