book-writer_skill

This skill guides theological book chapter writing in CJ's voice, grounding analysis in Scripture and providing clear, evidence-based structure for readers.

Python

2

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill williacj/claude-skills --skill book-writer

SKILL.md13.3 KB

Overview

This skill guides writing theological book chapters in CJ's voice and method. It is intended strictly for book chapters—not for sermon writing, sermonettes, or weekly teaching material. Use the detailed book plans for specific content while using this skill for how to shape, voice, and test each chapter.

How this skill works

The skill codifies voice characteristics, anti-AI rules, and a step-by-step chapter workflow so every chapter is built from Scripture and presented plainly. It inspects structure, scripture handling, framework development, language use, and integration with the larger book plan. Follow the pre-write, drafting, and post-write checklists to ensure biblical faithfulness and voice authenticity.

When to use it

Drafting or revising a chapter for a theological book
Translating a book plan's outline into a full chapter
Developing theological frameworks grounded in Scripture
Deciding when to use original-language notes or extended exegesis
Ensuring chapter integration with the book’s overall argument

Best practices

Start by consulting the detailed book plan for WHAT to write, then use this skill for HOW to write
Build arguments piece by piece from multiple biblical passages; avoid proof-texting
Write in CJ’s natural voice: plain language, varied rhythm, inclusive 'we', and honest questions
Use original languages only when they genuinely illuminate meaning, and keep explanations accessible
Limit subheadings and lists to places that genuinely aid clarity; prefer prose by default
After drafting, read aloud, verify Scripture context, and remove any hype or AI-like phrasing

Example use cases

Converting a chapter outline into a 3,500–5,000 word chapter that develops a theological framework
Reworking exegesis so it shows connections across Old and New Testaments without overstatement
Adding illustrative examples and metaphors that clarify rather than distract
Testing a proposed theological framework against hard or tension-creating texts
Preparing chapter transitions that integrate with preceding and following chapters

FAQ

No. This skill is explicitly for book chapters only; sermons, sermonettes, and weekly teaching material require a different approach.

When should I consult the detailed book plan?

Always before writing a chapter. The book plan provides the theological frameworks, passages, and structure; this skill provides the method and voice.