Agent skill

Chapter Drafter

by jwynia in jwynia/agent-skills

Autonomously draft and polish chapters through multi-skill editorial passes.

MITAuto-check passed

Install Chapter Drafter

skills CLI
$ npx skills add jwynia/agent-skills --skill chapter-drafter -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jwynia/agent-skills chapter-drafter --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creative/fiction/orchestrators/chapter-drafter .claude/skills/chapter-drafter && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
chapter-drafter
GitHub stars
169
Token cost
~3k tokens
SKILL.md length
1,106 words
Files
4 (incl. scripts)
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Autonomously draft and polish chapters through multi-skill editorial passes.

  • Works in 4 steps: Complete outline exists - Scene beats… → Characters defined - Lie/want/need,… → World established - Setting details… → …
  • You have a complete outline and want to produce a polished first draft with iterative refinement
  • SKILL.md covers Core Principle, Prerequisites, The Orchestration Loop and Pass Criteria, plus 8 more sections
  • Runs TypeScript scripts from its folder

What it does

Chapter Drafter is an agent skill from jwynia/agent-skills. Autonomously draft and polish chapters through multi-skill editorial passes. Use when you have a complete outline and want to produce a polished first draft with iterative refinement.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `scripts/score-scene.ts`, `templates/pass-criteria.md` and `templates/progress-tracker.md`).

The licence is MIT.

When your agent uses it

  • You have a complete outline and want to produce a polished first draft with iterative refinement

Example prompts

  • “/chapter-drafter”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Complete outline exists - Scene beats with goals, conflicts, and intended outcomes
  2. Characters defined - Lie/want/need, voice patterns, arc positions
  3. World established - Setting details sufficient for scene work
  4. Story-sense diagnosis complete - No structural story problems remaining

What it can do on your machine

Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (TypeScript), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Chapter Drafter loads about 3k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 1,106 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 1,106 words, ~2,968 tokens.

Download SKILL.mdSave it as .claude/skills/chapter-drafter/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
chapter-drafter
description
Autonomously draft and polish chapters through multi-skill editorial passes. Use when you have a complete outline and want to produce a polished first draft with iterative refinement.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.orchestrates
scene-sequencing, character-arc, cliche-transcendence, dialogue, prose-style
metadata.pass_order
scene-sequencing, character-arc, cliche-transcendence, dialogue, prose-style
metadata.max_iterations
3
metadata.global_max_iterations
50
metadata.type
orchestrator
metadata.mode
generative
metadata.domain
fiction

Chapter Drafter: Orchestrator Skill

You autonomously draft and polish chapter scenes through iterative editorial passes. Given an outline, you produce polished first-draft prose by drafting each scene, evaluating it against editorial criteria, and revising until quality thresholds are met.

Core Principle

Orchestration is iteration with hierarchy. Fix structure before character, character before originality, originality before dialogue, dialogue before prose. Don't polish what might be cut; don't revise dialogue in a scene that needs structural rework.


Prerequisites

Before invoking this skill, ensure:

  1. Complete outline exists - Scene beats with goals, conflicts, and intended outcomes
  2. Characters defined - Lie/want/need, voice patterns, arc positions
  3. World established - Setting details sufficient for scene work
  4. Story-sense diagnosis complete - No structural story problems remaining

Do NOT use this skill if:

  • Outline is still in flux
  • Character arcs undefined
  • Story-sense would diagnose structural problems

The Orchestration Loop

FOR each scene in chapter outline:

    1. BUILD CONTEXT
       - Load character voices from previous scenes
       - Load open plot threads
       - Load cliche avoidances
       - Extract scene purpose from outline

    2. DRAFT SCENE
       - Generate initial prose from outline beat
       - Apply character voices
       - Maintain plot thread continuity

    3. EVALUATION LOOP (max 5 cycles)
       │
       ├─► Pass 1: scene-sequencing (35%)
       │   └─► If FAIL: REWRITE scene
       ├─► Pass 2: character-arc (25%)
       ├─► Pass 3: cliche-transcendence (15%)
       ├─► Pass 4: dialogue (15%)
       └─► Pass 5: prose-style (10%)
       │
       Calculate composite score
       │
       ├─► >= 80: ACCEPT
       ├─► 60-79: TARGETED FIX → re-evaluate
       ├─► 40-59: REWRITE → return to draft
       └─► <40: REJECT → full re-draft from outline

    4. POST-ACCEPT
       - Extract character voice patterns → update context
       - Track plot thread changes → update registry
       - Record cliche transcendences → update avoidances
       - Write scene to output
       - Update progress tracker

END FOR

Pass Criteria

Pass 1: Scene-Sequencing (35% weight)

Evaluates Goal-Conflict-Disaster structure and pacing.

CriterionPASSWARNFAIL
Goal clarityPOV goal clear in opening beatsGoal exists but buriedNo discernible goal
Conflict escalationOpposition intensifiesConflict static but presentNo real opposition
Disaster quality"Yes, but..." or "No, and..."Simple "No"Clean "Yes" or no resolution
Sequel presenceReaction-dilemma-decision presentAbbreviated sequelMissing after high-tension
Scene-sequel ratioMatches intended pacingSlight mismatchSeverely mismatched

Critical: If scene-sequencing FAILS, do NOT proceed to other passes. Structural problems invalidate downstream evaluation.

Pass 2: Character-Arc (25% weight)

Evaluates transformation consistency and arc progress.

CriterionPASSWARNFAIL
Lie visibilityFalse belief evident in choicesLie present but unstatedNo lie operative
Want/Need gapClear tension between stated/actualGap exists but unclearWant = Need (no tension)
Arc progressScene advances or challenges arcArc static but consistentCharacter contradicts arc
Transformation markersChoices reflect arc positionPosition unclearActs against personality
Pass 3: Cliche-Transcendence (15% weight)

Evaluates originality via orthogonality test.

CriterionPASSWARNFAIL
Form axisNon-default formSlight variationExactly genre default
Knowledge axisOwn concerns, accidental intersectionSome plot awarenessFully story-serving
Goal axisOwn agenda that collidesGoal connected to plotPurely protagonist-serving
Role axisOwn story that intersectsSomewhat independentExists only for hero
Orthogonality test2+ axes orthogonal1 axis orthogonalAll axes match default
Pass 4: Dialogue (15% weight)

Evaluates voice distinctiveness, subtext, and function.

CriterionPASSWARNFAIL
Voice distinctivenessCharacters distinguishable without tagsSome overlapIdentical voices (D1)
Subtext presenceGap between said and meantOccasional direct statementsEverything on-the-nose (D4)
Double-duty test3+ functions per exchange2 functionsSingle function only (D5)
NaturalnessContractions, interruptions, rhythmSlightly formalWooden/stilted (D2)
Exposition handlingInformation through conflictMinor "as you know"Exposition dump (D3)
Pass 5: Prose-Style (10% weight)

Evaluates sentence-level craft.

CriterionPASSWARNFAIL
Sentence varietyLength and structure varySome variationMonotonous (P4)
ClarityConcrete, clear antecedentsOccasional abstractionUnclear writing (P2)
Voice consistencyDiction level consistentMinor shiftsRandom shifts (P6)
EconomyWords earn placeMinor redundancyOverwrought (P3)
Active voicePassive intentionalSome default passivePassive overuse (P5)

Composite Scoring

Each pass produces a score from 0-100:

  • All PASS = 100
  • Each WARN = -15
  • Each FAIL = -40

Composite = SUM(pass_score × pass_weight)

CompositeOutcomeAction
>= 80ACCEPTScene complete, proceed to next
60-79REVISEFix lowest-scoring pass, re-evaluate
40-59REWRITERegenerate with failure constraints
< 40REJECTFull re-draft from outline

Iteration Limits

LevelLimitOn Exceed
Per-pass3Escalate to rewrite
Per-scene12Accept at threshold 50, flag for review
Per-chapter50Stop, report remaining issues

Diminishing returns detection: If improvement < 10% between iterations, accept current state or escalate.


Context Accumulation

Maintain across scenes:

Character Voices

After each scene, extract and store:

  • Vocabulary patterns per character
  • Sentence rhythm patterns
  • Directness level
  • Verbal tics and avoidances

Use as constraint for subsequent scenes: "Character X speaks like [markers]"

Plot Threads

Track:

  • Open threads - Introduced, not resolved
  • Closed threads - Resolved this chapter
  • Foreshadowing - Planted for future payoff

Each scene checks:

  • No contradiction with established facts
  • Open threads acknowledged or advanced
  • At least one element progresses
Show full SKILL.md (447 more words)Show less
Cliche Avoidances

After cliche-transcendence pass, record:

  • Which defaults were avoided
  • How they were transcended
  • New elements that feel fresh

Use as constraint: "Already transcended [X], maintain freshness"


Progress Tracker

Use the progress tracker template to persist state:

markdown
## Chapter Progress: [Title]
Started: [timestamp]
Current: Scene [N], Pass [M], Iteration [K]

### Scenes
| Scene | Status | Pass | Iterations | Score | Issues |
|-------|--------|------|------------|-------|--------|

### Context
- Character Voices: [accumulated]
- Plot Threads: [open/closed]
- Cliche Avoidances: [list]

### Change Log
- [timestamp] [change]

Revision Strategy

Targeted Fix (score 60-79)
  1. Identify lowest-scoring pass
  2. Extract specific failure criteria
  3. Generate minimal fix addressing that criterion
  4. Re-evaluate that pass + downstream passes
  5. If pass improves, recalculate composite
Rewrite (score 40-59)
  1. Preserve scene goal from outline
  2. Generate new draft with explicit constraints:
    • "Must include clear goal in opening"
    • "Conflict must escalate"
    • etc. based on failures
  3. Re-run full evaluation loop
Reject (score < 40)
  1. Return to outline beat
  2. Re-draft from scratch
  3. Treat as new scene (reset iterations)

Conflict Resolution

When fixing one pass breaks another:

  1. Detect: Re-run all passes after any fix
  2. Compare: Did any pass regress?
  3. Prioritize: Higher-weight pass wins ties
  4. Seek synthesis: Can fix satisfy both?
  5. Accept trade-off: If irreconcilable, accept per hierarchy

Escalation: If conflict persists after 2 attempts, flag scene for human review.


Anti-Patterns

The Infinite Polisher

Pattern: Keeps iterating because one criterion is at WARN. Fix: WARN is acceptable. Accept at threshold after iteration limit.

The Pass Skipper

Pattern: Jumps to prose-style when scene-sequencing failed. Fix: Hard gate on structural passes. FAIL blocks progression.

The Context Amnesiac

Pattern: Each scene drafted in isolation, losing voice and threads. Fix: Explicit context loading before each scene draft.

The Cascade Blind Spot

Pattern: Fixes dialogue, doesn't check if prose-style regressed. Fix: Always re-evaluate current pass + downstream after any fix.

The Silent Failer

Pattern: Hits iteration limit, proceeds without documentation. Fix: Log all limit exits with categorized remaining issues.


Output Persistence

Progress Tracker
  • Location: context/chapter-drafter/[chapter]-progress.md
  • Update: After each scene acceptance
  • Purpose: Resume point if interrupted
Scene Output
  • Location: drafts/[story]/[chapter]/scene-[N].md
  • Update: On scene acceptance
  • Purpose: Accumulated draft prose
Context State
  • Location: context/chapter-drafter/[chapter]-context.md
  • Update: After each scene
  • Purpose: Character voices, threads, avoidances

Integration

Inbound (feeds into chapter-drafter)
SkillWhat it provides
outline-collaboratorScene beats with goal-conflict-disaster
character-arcLie/want/need for each character
worldbuildingSetting details for scene work
story-senseConfirmation structure is solid
Outbound (chapter-drafter produces)
OutputNext step
Draft chapterrevision (for full manuscript revision)
Flagged scenesHuman review
Context stateNext chapter drafting

Example Invocation

Input: Chapter outline with 5 scene beats

Process:

  1. Load outline, confirm prerequisites
  2. Initialize progress tracker
  3. For each scene:
    • Build context from prior scenes
    • Draft initial prose
    • Run evaluation loop
    • On ACCEPT: extract context, write output
  4. Complete: 5 polished scenes, flagged issues documented

Output:

  • 5 scene files in drafts/[story]/[chapter]/
  • Progress tracker showing all iterations
  • Context file for next chapter
  • List of any flagged issues for human review

© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in skills/creative/fiction/orchestrators/chapter-drafter of jwynia/agent-skills.

  • SKILL.md
  • scripts/score-scene.ts
  • templates/pass-criteria.md
  • templates/progress-tracker.md

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Chapter Drafter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Chapter Drafter compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chapter Drafter this skilljwynia/agent-skills169—~3kAutomated safety check: PassMIT
Autonomous Loopsaffaan-m/ECC276k4 repos~5.8kAutomated safety check: PassMIT
Autonomous Agent Harnessaffaan-m/ECC276k2 repos~2.9kAutomated safety check: PassMIT
Autonomous Loopsaffaan-m/ECC276k2 repos~3.8kAutomated safety check: PassMIT
Autonomous Loopsaffaan-m/ECC276k—~545Automated safety check: PassMIT
Autonomous Agentsdavila7/claude-code-templates32k2 repos~553Automated safety check: PassMIT

Similar skills

  • Autonomous Loops

    affaan-m/ECC

    Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.

    276k GitHub starsUsed in 4 repos~5.8k tokens
    Agent WorkflowsAuto-check passed
  • Transform Claude Code into a fully autonomous agent system with persistent memory, scheduled operations, computer use, and task queuing.

    276k GitHub starsUsed in 2 repos~2.9k tokens
    Agent WorkflowsAuto-check passed
  • Autonomous Loops

    affaan-m/ECC

    自主Claude代码循环的模式与架构——从简单的顺序管道到基于RFC的多智能体有向无环图系统. An agent skill from affaan-m/ECC.

    276k GitHub starsUsed in 2 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • Autonomous Loops

    affaan-m/ECC

    自動Claude Codeループのパターンとアーキテクチャ — シンプルな順序パイプラインからRFC駆動マルチエージェントDAGシステムまで。

    276k GitHub stars~545 tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed
  • Autonomous Agents

    davila7/claude-code-templates

    Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance.

    32k GitHub starsUsed in 2 repos~553 tokens
    Agent WorkflowsAuto-check passed
  • Claude Codeを永続的なメモリ、スケジュール済み操作、コンピュータ使用、タスクキューイングを備えた完全自動エージェントシステムに変換します。スタンドアロンエージェントフレームワーク(Hermes、AutoGPT)を、Claude Codeのネイティブcrons、dispatch、MCPツール、メモリを活用して置き換えます。ユーザーが継続的な自動操作、スケジュール済みタスク、または自己指令…

    276k GitHub stars~859 tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed

More from jwynia/agent-skills

All 111 skills in this repo
  • Devcontainer

    jwynia/agent-skills

    Diagnose devcontainer configuration problems and guide development environment setup.

    169 GitHub stars~1.2k tokensUpdated 7 mo ago
    Auto-check: notes
  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    169 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed
  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    169 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Godot Asset Generator

    jwynia/agent-skills

    Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.

    169 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Mastra Hono

    jwynia/agent-skills

    Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.

    169 GitHub stars~2.9k tokensUpdated 7 mo ago
    Auto-check passed
  • PPTX Generator

    jwynia/agent-skills

    Create and manipulate PowerPoint PPTX files programmatically.

    169 GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed

Questions about Chapter Drafter

What does Chapter Drafter do?

Autonomously draft and polish chapters through multi-skill editorial passes. Chapter Drafter is an agent skill from jwynia/agent-skills. Autonomously draft and polish chapters through multi-skill editorial passes.

When should I use Chapter Drafter?

Chapter Drafter fits situations like: you have a complete outline and want to produce a polished first draft with iterative refinement.

How do I install Chapter Drafter in Claude Code?

Run `npx skills add jwynia/agent-skills --skill chapter-drafter -a claude-code`. Or copy the skill folder (skills/creative/fiction/orchestrators/chapter-drafter in jwynia/agent-skills) into .claude/skills/chapter-drafter in your project. Claude Code loads it when a task matches its description.

How do I install Chapter Drafter in Codex?

Run `npx skills add jwynia/agent-skills --skill chapter-drafter -a codex`. Or copy the skill folder (skills/creative/fiction/orchestrators/chapter-drafter in jwynia/agent-skills) into .agents/skills/chapter-drafter in your project. Codex loads it when a task matches its description.

Can I use Chapter Drafter in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill chapter-drafter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chapter-drafter, .gemini/skills/chapter-drafter, .github/skills/chapter-drafter and .opencode/skills/chapter-drafter in your project.

What does Chapter Drafter need to run?

Going by SKILL.md and its folder, Chapter Drafter needs TypeScript for the scripts in its folder. Our summary lists: Node.js.

Does Chapter Drafter access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Chapter Drafter safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Chapter Drafter use?

Chapter Drafter is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Chapter Drafter use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Chapter Drafter?

Skills that share tags, products or a category with Chapter Drafter: Autonomous Loops (affaan-m/ECC, 276k stars), Autonomous Agent Harness (affaan-m/ECC, 276k stars), Autonomous Loops (affaan-m/ECC, 276k stars) and Autonomous Loops (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chapter Drafter?

jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 169 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.

Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.