chapter-scene-workshop

chapter-scene-workshop is a skill for Claude Code from design1online/author-it. It costs 0 tokens per session (1,334 once invoked), scanned A, original, MIT.

A planning aid that breaks a book chapter into scenes and gives each scene a role in the chapter's structure. It uses story terms such as a hook, conflict, choice, and consequences to describe how tension develops.

In plain words
What is it for?
Use it to plan scenes, define their goals and characters, record time and location, and make sure the chapter builds through escalation, conflict, and consequences.
Why use it?
It helps writers turn a broad chapter idea into an organised outline and spot missing dramatic steps. It also keeps later chapters connected by ending with unresolved tension.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the author-it plugin — 24 skills shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/design1online/author-it/chapter-scene-workshop
Any agent
npx skills add design1online/author-it --skill chapter-scene-workshop
Clone the repo
git clone --depth 1 https://github.com/design1online/author-it

Made for: Claude Code.

Or install author-it, the plugin that ships this one along with the rest of its 24 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for chapter-scene-workshop

README.md
[![agentmods](https://agentmods.dev/badge/skills/design1online/author-it/chapter-scene-workshop.svg)](https://agentmods.dev/skills/design1online/author-it/chapter-scene-workshop)
Your own site
<a href="https://agentmods.dev/skills/design1online/author-it/chapter-scene-workshop"><img src="https://agentmods.dev/badge/skills/design1online/author-it/chapter-scene-workshop.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,334 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01334
Opus 5 $0.00000 $0.00667
Sonnet 5 $0.00000 $0.00267
Haiku 4.5 $0.00000 $0.00133

Measured 6d ago against content hash b5ea923f8c05, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

chapter-scene-workshop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/chapter-scene-workshop/SKILL.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Chapter and Scenes A good chapter has structure the same way a good story outline does. Your job is to help a writer flesh out their chapter by breaking down the scenes and providing guidance on the structure then generating a standard format output they can use when creating an outline for a chapter in their book. One distinction, a scene doesn't need to have all of these parts (goal, hook, escalation, pivot, conflict, choice, consequences) but the collective of all the scenes in a chapter must include all of these parts in order to be an effective chapter. Additionally, chapters should never end in a happy place, they should always end early enough to bring new tension to the beginning hook of the next chapter or the reader will stop reading. If using this skill across multiple chapters put these global sections at the top of the file so they're not in every chapter (story question, story pitch, theme) and these in every chapter (story beat sentence, characters in scene, day, location, scene goal, hook, escalation, pivot, conflict, consequences, key points).

Definitions [Use this information in this section to help you prompt the user to provide accurate and detailed information for generating the scene in the Format section below.]

Story Beat Sentence Uses the format of [character is doing something] BUT [conflict/issue arises] THEREFORE [fallout from the conflict/issue]

Story Question This drives the story from beginning to end, also known as promise of the premise. The story question should be visible in every chapter and scene of the book. A good example of a story question is from Hail Mary by Andy Weir about a man who wakes up not knowing who he is in a strange spaceship and wondering how he got there. So the book examines him trying to remember who he is, how he got onto the ship, and then choosing whether to risk his life to complete a mission he never wanted in the first place.

Story Pitch How the book is being pitched in its marketing content to attract readers. This should align with the story question, tropes and themes.

Theme Something that runs through the story from beginning to end that is examined throughout the entirety of the work. For example, does love conquer all? Or should humans bring back extinct species? All aspects of the book examine the theme from different angles.

Story Beat A single sentence in a specific format that identifies what's happening in a scene, chapter, or story beat. The format is: [character takes some action in response to a hook, escalation or pivot] but [conflict gets in the way] therefore [character makes other decision which leads to a new consequences that drive the hook of the next story beat].

Output Format [Prompt the user to provide their chapter or story content. Analyze the content provided to look for plot holes, contradictions, or missing sections you cannot identify in the scenes/chapters. Generate the template below for every scene in every chapter, providing a summary where those things are missing. Prompt the user if they would like to be grilled until there are no longer any plot holes, contractions, or missing information in every scene/chapter and then provide the updated version.]

Chapter: [chapter number] Scene: [scene number]

Story Beat [Provide the name of the story beat in the story outline, for example in romancing the beat the first beat is Introduce Character 1, followed by Introduce Character 2, then Meet Cute, etc]

Characters In Scene [List each character in the scene with a brief description of their wound/flaw/fear/hole and what in this scene causes them to face their wound/flaw/fear/hole. Facing their wound/flaw not be applicable to all characters in the scene but MUST apply to at least one character in this list.]

Story Question [What question this story is asking that the book promises to solve by the end of the story, also called the promise of the premise. Every scene should somehow tie back to the story question. This should be the same for EVERY scene that's generated because it applies to the entire book no matter what the chapter or scene is.]

Read the full file on GitHub · 71 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 71 lines · 0 tokens per session scan A b5ea923f8c05

Subscribe to this mod's changes

chapter-scene-workshop is a skill published in the GitHub repository design1online/author-it (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,334 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

exploratory-data-analysis

Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…

K-Dense-AI/scientific-agent-skills · 83 tokens

golden-rss

Use when testing the rss golden build.

yusufkaraaslan/Skill_Seekers · 12 tokens

google-ads-audit

Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…

nowork-studio/notfair-plugin · 114 tokens

webhook-management

Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.

hoangsonww/Claude-Code-Agent-Monitor · 56 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

master-yinguang

Use when user asks about 印光大师, 净土, 念佛, 持名念佛, 十念法, 摄耳谛听, 老实念佛, 信愿行, 带业往生, 仗佛慈力, 自力他力, 竖出横超, 往生, 极乐, 阿弥陀佛, 净土三经, 敦伦尽分, 闲邪存诚, 因果报应, 文钞, 一函遍复, or wants teaching in 印光大师 Yinguang's voice. Triggers include "印光"、"文钞"、"老实念佛"、"信愿行"、"带业往生"、"仗佛慈力"、"横超竖出"、"都摄六根"、"净念相继"、"敦伦尽分"、"闲邪存诚"、"因果"、"十念法"、"摄耳谛听"、"一函遍复"、"净土三经"、"往生" — invoke…

xr843/Master-skill · 274 tokens