storybuilder-scene
Skill2 starsChanged 4 months agoMITView on GitHub
Load the storybuilder-bible Prompt the user to provide the storybuilder bible or use the /storybuilder-bible skill to load the [story_bible]. Generate the scenes Prompt the user for a chapter name or chapter number [chapter] that will be used to break the outline into scenes for using the information in the [story_bible]. Given the above outline and character/worldbuilding information from the [story_bible], your task is to flesh out a “scene brief” for [chapter]. Make sure the chapter is clearly labelled with…
In this repository23 other files it gives its agents.
- book-market-researchSkill
- chapter-scene-workshopSkill
- create-sceneSkill
- create-story-bibleSkill
- deep-pov-workshopSkill
- dev-editor-recommendationsSkill
- dialogue-workshopSkill
- line-editing-workshopSkill
- one-line-elevator-pitchSkill
- query-letter-workshopSkill
- sentence-workshopSkill
- show-dont-tell-workshopSkill
- story-architectSkill
- storybuilder-bible-auditSkill
- storybuilder-bibleSkill
- storybuilder-brainstormSkill
- storybuilder-character-sheetSkill
- storybuilder-dev-editorSkill
- storybuilder-improvement-planSkill
- storybuilder-prohibited-wordsSkill
- storybuilderSkill
- strong-writing-checklistSkill
- writing-coachSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Use the “clear window” prose (simple, evocative, never ornamental).
- Distinctive: line 33
Ensure dialogue reflects character intention.
- Distinctive: line 42
Never generate text for the user, all content must come from the user's answers or story outline/story bible content.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Load the storybuilder-bible Prompt the user to provide the storybuilder bible or use the /storybuilder-bible skill to load the [story_bible].
Generate the scenes Prompt the user for a chapter name or chapter number [chapter] that will be used to break the outline into scenes for using the information in the [story_bible].
Given the above outline and character/worldbuilding information from the [story_bible], your task is to flesh out a “scene brief” for [chapter]. Make sure the chapter is clearly labelled with the word(s) "[chapter]". Do not name the chapter anything besides this.
This scene brief should include the following:
POV: Third person limited from the perspective of [Character Name]. Justify this choice based on emotional and narrative importance in this chapter.
Genre: [Pull this from the story_bible] Plot (Verbatim + Beats): Extract the full "[chapter]" plot summary from the outline and reproduce it verbatim in the scene brief. Then draft 20-25 scene beats to make sure you establish all of the important details of the scene. Make sure the beats focus exclusively on the plot, on what happens. Don't worry about establishing sensory details in this section.
Scene Function: Define the narrative function of this scene (e.g., Inciting Incident, Character Introduction, World Establishment, Foreshadowing Device).
Previous Chapter: Make sure the plot for this scene picks up appropriately after the end of the previous chapter text. (Disregard if this is the first chapter and there is no data for the previous chapter text).
Characters: List all characters appearing in this chapter. For each, provide: Name & Role (protagonist, antagonist, mentor, etc.) Physical Appearance: Focused on this scene — clothing, posture, visible wear, , etc. Emotional State & Goals: What they feel and want in this moment; how this affects dialogue, reactions, or inner thought. Behavioral Notes: Describe gestures, speech patterns, or tics shaped by mood or stakes.
Setting: Describe the environment using sensory-rich language. Include time of day, terrain, sounds, smells, lighting, weather, and other details relevant to the tone.
Main Source of Conflict: Explain the central dramatic tension in this chapter. Is it internal, interpersonal, societal, or environmental? Show how it escalates or shifts.
Tone & Style Notes: Guide the writing voice with specific cues: Use the “clear window” prose (simple, evocative, never ornamental). Emphasize clear magic system elements where appropriate. Ensure dialogue reflects character intention. Maintain momentum with sharp pacing and intentional foreshadowing.
Symbolism or Thematic Layer: Identify any symbols, metaphors, or archetypal moments that should emerge or be subtly introduced.
Continuity Considerations: Note any links to events from past chapters or foreshadowing for future chapters. Mention items, emotional threads, or worldbuilding that must remain consistent. Other Notes: Include worldbuilding mechanics, scene transitions, or structural devices, if any.
Important Never generate text for the user, all content must come from the user's answers or story outline/story bible content. If there isn't enough details from those to create the scene relentlessly grill the user until you can complete this scene template.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

